Netherlands
Joined: Apr 8, 2022
Post Count: 1615
Status:
Offline
Re: Areal View Problem
I'm sorry, but then I am out of ideas what could cause this problem. You could check that all preference settings are same on both machines but I assume you already did that.
Still, you should check with another project if the same problem occurs. If it does than the only thing left is the different machines/installed distributions.
---------------------------------------- Dodecagon.nl 1300+ 3D models, manuals, and projects
Italy
Joined: Nov 17, 2021
Post Count: 493
Status:
Offline
Re: Areal View Problem
Are you able to zoom in/out using W/S keys or Up/Down arrow keys?
Some mouse have an high frequency scroll wheel which may affect the scroll speed, so trying with a different mouse could help.
Another option is, with Pan3dView plugin installed, go to View 3D -> Pan 3D view settings..., then uncheck the "Exponential scroll" option. This should enable the default zoom speed.
If nothing works, run the program from the command line, copy the output and paste it here (if there are java exception we may find the root cause).
Austria
Joined: Oct 16, 2025
Post Count: 19
Status:
Offline
Re: Areal View Problem
I have Pan3dView.sh3p in the plugins Folder. I din't find any option to change any pan3d setting. Running from command line is not an option since this is a flatpak installation, as it is the same like on the Desktop PC
Netherlands
Joined: Apr 8, 2022
Post Count: 1615
Status:
Offline
Re: Areal View Problem
Running from command line is not an option since this is a flatpak installation
And there might be the cause of your problem. Don't use a flatpak installation. The creators of flatpaks seem to think they know better what to pack and most likely have stripped the java runtime. That it works at all on your desktop is plain luck. Download the 7.5 .tgz and extract it in a directory of your choice. Start Sweet Home 3D with the SweetHome3D_Java3D-1_5_2 script. The .tgz comes with the correct Java runtime included and using that avoids all kinds of problems. It doesn't interfere with an existing Java install.
---------------------------------------- Dodecagon.nl 1300+ 3D models, manuals, and projects
Austria
Joined: Oct 16, 2025
Post Count: 19
Status:
Offline
Re: Areal View Problem
For sure that is not the problem.
I installed the stand-alone version on my Laptop first. As I recognized the problem, I looked on my desktop and found that the installation there was flatpak. So I did the exact configuration with flatpak on the laptop and the problem persists.
Netherlands
Joined: Apr 8, 2022
Post Count: 1615
Status:
Offline
Re: Areal View Problem
Check the menu > Help > About. The dialog will show the Java version that is used. Compare them between the desktop and laptop. Your best bet is using the Java version provided with Sweet Home 3D, both for the 3D display and photo rendering. (Use the SweetHome3D_Java3D-1_5_2 script from the .tgz download for an example.)
ETA: I tried Sweet Home 3D with the latest Java (1.8.0_471/jre8U471) and everything seems to work fine. I needed that to fix an issue with the pluginmanager that now works as it should. Also no problems with zooming in 3D view. You can try that too.
---------------------------------------- Dodecagon.nl 1300+ 3D models, manuals, and projects
----------------------------------------
[Edit 1 times,
last edit by Keet at Dec 3, 2025, 12:48:40 PM]
Joined: May 18, 2021
Post Count: 277
Status:
Offline
Re: Areal View Problem
A few random thoughts:
Are you using a fancy mouse with custom settings i.e. I have an MX Master 2S, and it has a whole special app (Solaar) for controlling advanced features. Check if any settings are the same/different between the two systems.
Did you try a completely different model of mouse? Preferably a really basic one with no "smarts".
Maybe the laptop touchpad and the mouse are conflicting with each other. Does the problem occur with no mouse, just using the touchpad? Have you tried disabling the touchpad? This will be system/desktop dependent, so you would have to figure this out yourself. Possibilities are a) an app to disable it for typing, b) disable it in X - see below, c) blacklist the driver, d) a bios option.
