By JesperW
#230631
The 1.5.1 plugin (from 070531) has fixed the crash-on-window-open problem.

However it still crashes for me when exporting a large complex assembly, still with the "Virtual Function Call" message.

Some observations:

After "Render Scene" the status bar flickers rapidly with the "exporting scene... x%" working its way up to 20% after about 2 minutes.

After 20% the flickering stops and the number no longer increases. The process is still consuming 100% CPU. The OS still has plenty of RAM free, so it's not out of memory.

After a few minutes of going nowhere and consuming 100% CPU the application crashes with "R6025 - Pure Virtual Function Call".

(The assembly is large but not extreme, less than 1000 parts and less than 1M polys at current resolution).

/j
User avatar
By juan
#230950
Hi Jesper,

- does it crash with any large assembly?
- does it have lightwave components?

The behavior of the status bar is not accurate when the CPU is 100% busy so I am afraid this is not a clue in this case.. does the memory consumption grows until the app crashes or the system is frozen for some minutes without allocating more memory?

Many thanks,

Juan
By JesperW
#231025
- Any assembly... Well I am only working on one project so I couldn't tell (It's still the same yacht but nearing completion now...) But I can do other types of "whole assembly" operations, such as running 3rd party export plugins etc.

- SWX resolves all components when you do render so it shouldn't have any lightweight components (I am assuming you saying "lightwave" was a mistake)

The CPU is not 100% busy, only one core is 100%, but anyway...

It does not allocate more memory once the status bar has stopped counting up.
Help with swimming pool water

Hi Andreas " I would say the above "fake[…]

render engines and Maxwell

Other rendering engines are evolving day by day, m[…]