Search the Community
Showing results for tags 'crash'.
Found 4 results
Some of Valentin's PVSOL Premium potential customers might have, as I did, decided to buy the software based on 3D modeling and shading simulation capabilities. Several anecdotal evidences of this capability can be found on this forum, and on promotion materials spread across several media by Valentin Software sales team. Let me give some examples below... Above - PVSOL Online Shop suggests drone usage for photogrammetry Above - Youtube tutorial suggesting the use of photogrammetry software for 3D import (Pix4D) Above: Feature advertised online since 2017, note the mention to "3D objects created with photos taken from a drone" I guess these examples should be enough to prove the spin over 3D photogrammetry and real life 3D models import into PVSOL. Most people most probably will do the same as we did, download the software and try it out with simple small examples, and it does work, how nice... we then decide to buy the software. Unfortunately it's only when starting to use it for real, with real projects, real data, real photogrammetry, that the trouble starts... errr... ok... let's go smaller then... decimate 3D model and retry... oops... there is a limit of ONLY 500.000 vertices! Anyone with the thinnest experience in photogrammetry knows 500k vertices is nothing, any model with such a low count of vertices is either a single building alone with very little detail and very decimated, or the scene is in terribly low quality with lots of 3D defects. This 500k vertices limit renders the 3D photogrammetry almost useless. In order to work with photogrammetry 3D models one has to decimate the model to a number of vertices really below the 500k vertices limit, because as reported in this other thread (without answer for weeks now) the vertices count is wrong and includes some own PVSOL vertices as overhead, limiting even further the model quality. We have no choice but to comply with the previously unmentioned limits, and we decimate the model further, making the 3D almost unrecognizable, and voila it finally loads and we can start designing the PV system believing all is well now, apart from the 3D miserable quality: This illusion ends as soon as we press the "Start shading frequency" button with the option to show shading percentages on the modules. With the example above, with only 320 modules, the application crashes with an "out-of-memory error": Now this is very strange because this is a 16GB machine and memory usage by PVSOL process never went above 1.4GB on all of the tests we did, so there is a nasty bug here. Valentin official answer is to just say we ran out of memory (despite proof we did not), and telling me "We would use the planning mode with map section.", yes really! So we are working with a 3D model decimated already to just a few hundred vertices, and still PVSOL can't cope with it. Astonishing! We did not give up, and went to the extent of DELETING part of the 3D model objects, parts that would not interfere with shading on the modules, and decimated even further. The result was an .obj file with just 82.034 vertices, that’s 16% of what PVSOL claims to be able to handle, and guess what... it still crashes and can't simulate shading. Conclusion: Don't be fooled by Valentin Software claims over the use of 3D import of photogrammetry models, it's nothing but a toy for micro systems, it's not for professional use. Hope this narrative is useful to anyone considering buying PVSOL Premium based on 3D photogrammetry imports. PS: I have found PVSOL capabilities in regards to computation to be flawless thus far, if you don't mind a miserable 3D component, it's worth it. The 3D module however is just lame. PPS: The worst part on this is that Valentin Software refuses to admit it has a memory management bug, and provides no real assistance nor solution apart from dropping 3D import.
Hi, Whenever I try to use the 3D scene in PVsol 2018 (R4) it begins to load the scene with a progress bar, but upon completion the program freezes. I have tried uninstalling the GPU and installing newest drivers, uninstalling and re-installing PVsol, opening files in previous versions of PVsol, aso. Nothing seems to work. Do you know what might be causing this or any suitable solutions?
I'm running PV Sol premium 2017.9 and yesterday it crashed when I used it. Now, everytime when I try to start it I get appcrash and the following message; Problem name: CLR20r3 Problem signature 01: pvsolpremium.exe Problem signature 02: 2017.9.0.0 Problem signature 03: 58f75470 Problem signature 04: PVSOLpremium Problem signature 05: 2017.9.0.0 Problem signature 06: 58f75470 Problem signature 07: f51 Problem signature 08: 106 Problem signature 09: System.IndexOutOfRangeException OS-version: 6.1.7601.2.1.0.256.4 Language variant-ID: 1053 More information 1: 0a9e More information 2: 0a9e372d3b4ad19135b953a78882e789 More information 3: 0a9e More information 4: 0a9e372d3b4ad19135b953a78882e789 I think it has something to do with my .NET installation but I've reinstalled it and still get the same error on start. Have anyone seen this before? I'm running Windows 7 64bit.