11-17-2018, 03:37 PM
(This post was last modified: 11-17-2018, 04:42 PM by Extrudeface.)
It happens with "A", too (aim). (edit: and reset view)
Oki. I'm preparing a very complete post in the other report (the one about OBJ import) . Is very related with this one, as is same type of blender scene. The other case (the actual import stage) I have it more ironed, but with this one is less than I can do, as it seems that my total crash was... probably graphic card memory that gets totally stuck (or whatever in the card or something OS-graphic related, card involved or not). It can't redraw. Whole Wings3D window can't paint any change, the thumbing rotation wont rotate the axes in the corner, and cannot even open the log window, neither any window, and nothing in menus highlights on mouse over. Luckily, the rest of the system (my Windows) responds, this time. But instead of killing erl, this time waited quite, and it finally reacts, I see the actions I did taking place (a RMB over the 3D space, etc) Then I could open the log window, this was all the content :
wings-2.1.7
Reading preferences from: c:/Users/.../AppData/Roaming/Wings3D/Preferences.txt
wings_wm:837: Dropped Event autosaver: redraw
There is no crash dump generated with this.
Doing the unitize thing does not solve the problem (practically unresponsive, but with patience I can -this time- quit the app, etc).
Consider all this is with an extreme case of a really crazy scene with a 3.5 millions as dimension in the object, related to Blender unit, exported as OBJ and imported into Wings. I had happened to be just randomly in such a scene while making a project's concept freely, but I thought could be a good case to check if is there something going on.
EDIT :Actually, not sure if it just fills up card memory or whatever-the card thing, in another instance it really leaves the system unresponsive, checked the task manager, and the erl.exe process was taking almost 6GB (5.76, and I believe, growing) of my poor 8GB RAM (this tends to kill the machine). So, it can't redraw the windows app window, but it also takes huge system resources. Again, I guess is such a crazy scene scale. I believe maybe is when there you tell it to frame an object. To do the operation in such scene. It happens with AIM, FRAME, and reset view.
Oki. I'm preparing a very complete post in the other report (the one about OBJ import) . Is very related with this one, as is same type of blender scene. The other case (the actual import stage) I have it more ironed, but with this one is less than I can do, as it seems that my total crash was... probably graphic card memory that gets totally stuck (or whatever in the card or something OS-graphic related, card involved or not). It can't redraw. Whole Wings3D window can't paint any change, the thumbing rotation wont rotate the axes in the corner, and cannot even open the log window, neither any window, and nothing in menus highlights on mouse over. Luckily, the rest of the system (my Windows) responds, this time. But instead of killing erl, this time waited quite, and it finally reacts, I see the actions I did taking place (a RMB over the 3D space, etc) Then I could open the log window, this was all the content :
wings-2.1.7
Reading preferences from: c:/Users/.../AppData/Roaming/Wings3D/Preferences.txt
wings_wm:837: Dropped Event autosaver: redraw
There is no crash dump generated with this.
Doing the unitize thing does not solve the problem (practically unresponsive, but with patience I can -this time- quit the app, etc).
Consider all this is with an extreme case of a really crazy scene with a 3.5 millions as dimension in the object, related to Blender unit, exported as OBJ and imported into Wings. I had happened to be just randomly in such a scene while making a project's concept freely, but I thought could be a good case to check if is there something going on.
EDIT :Actually, not sure if it just fills up card memory or whatever-the card thing, in another instance it really leaves the system unresponsive, checked the task manager, and the erl.exe process was taking almost 6GB (5.76, and I believe, growing) of my poor 8GB RAM (this tends to kill the machine). So, it can't redraw the windows app window, but it also takes huge system resources. Again, I guess is such a crazy scene scale. I believe maybe is when there you tell it to frame an object. To do the operation in such scene. It happens with AIM, FRAME, and reset view.