Joined: Nov 19, 2013
Post Count: 2
Status:
Offline
3D view disappears in my saved model.
Hi, I'm using the online version (with the latest Java version) and suddenly the 3D view disappeared. I don't mean the enlarged drawing view, the space for the 3D view is still there, but it's completely gray and empty. The view is only gone in my saved model, with a new model it is still there and works fine.
France
Joined: Nov 7, 2005
Post Count: 9426
Status:
Offline
Re: 3D view disappears in my saved model.
I noticed this issue on some computers too, and it's the reason why the installer is still bundled with Java 6 and not yet with Java 7. Sometimes, when you resize the 3D view under Java 7, the 3D view becomes grey one time out of two. To display the 3D view again, simply resize it one step more.
----------------------------------------
Emmanuel Puybaret, Sweet Home 3D creator
Joined: Nov 19, 2013
Post Count: 2
Status:
Offline
Re: 3D view disappears in my saved model.
No, that doesn't help. Starting the browser again and reload the website doesn't help. Starting a new model, the 3D view is there, loading any saved model, it isn't. I could only bring it back by reloading the website.
i got the same problem. Using different versions doesn't solve the problem (windows 8, archlinux (AUR or bundled version of sh3D)) i can post my saved file to test. BTW thx for the great work
Think i found the solution ... i had a 0 thickness shower tray. removed it and now it's almost ok. I can't get the 3d view back to main window but the 3d view is working ok in a seperate window i will post an abstract of log, if it helps ...
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at com.eteks.sweethome3d.swing.HomeComponent3D$1.ancestorAdded(Unknown Source) at com.eteks.sweethome3d.swing.HomeComponent3D$1$1.componentResized(Unknown Source) at java.awt.AWTEventMulticaster.componentResized(AWTEventMulticaster.java:160) at java.awt.Component.processComponentEvent(Component.java:6331) at java.awt.Component.processEvent(Component.java:6285) at java.awt.Container.processEvent(Container.java:2229) at java.awt.Component.dispatchEventImpl(Component.java:4861) at java.awt.Container.dispatchEventImpl(Container.java:2287) at java.awt.Component.dispatchEvent(Component.java:4687) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:735) at java.awt.EventQueue.access$200(EventQueue.java:103) at java.awt.EventQueue$3.run(EventQueue.java:694) at java.awt.EventQueue$3.run(EventQueue.java:692) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:87) at java.awt.EventQueue$4.run(EventQueue.java:708) at java.awt.EventQueue$4.run(EventQueue.java:706) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) at java.awt.EventQueue.dispatchEvent(EventQueue.java:705) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138) at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)
Further testing ... It's a tedious process to track bug as there might be multiple factors that might be contibuting. I have multiple screens. Opening the example room i downloaded (http://www.sweethome3d.com/examples/userGuideExample.sh3d) works fine but some drawings i've been doing don't . Usually the main problem is i can't dock the 3d view anymore. Anyway i'll open a new thread as i've been hijacking this one enough now.
France
Joined: Nov 7, 2005
Post Count: 9426
Status:
Offline
Re: 3D view disappears in my saved model.
Thanks for the stack trace / log, it helps me to figure out where it comes from. But I couldn't reproduce your issue under Windows or Ubuntu yet. From your description, I tried this scenario: - create a new home - move the splitter above the 3D view to make it disappear - display the 3D view in a separate window - save home - close home - open it again - display the 3D view in the main window - move the splitter above the 3D view to make it appear. In your case, there could a possibility that it produces the stack trace you posted depending on the order of the events emitted by Java. As you're using multiple screens, it could come from this point too. Is the previous scenario produces the error you reported?
----------------------------------------
Emmanuel Puybaret, Sweet Home 3D creator