Wings 2.2.6

[micheus]

Stephan Vogt, thanks for the comments.

About the improvement you noticed, the Wings3D team has been working a lot since v2.0 in order to achieve that. In this post I did a summary of changes since v2.0 - check for "What was changed/improved" - a lot of code was rewritten.

About the .rwx no one has complained about that, so I think I can take a look on it and upgrade the exporter to be v2 compatible.
EDIT: I download the RWPaint.exe which requires the RWL21.DLL (RenderWare 2.1) and I was able to import an exported file from Wings3D which contains a hole.
Do you have a broken file so I can check what is going wrong?

For the selection issue, follow the oort's tip.
The current default way (just highlight an element) can be convenient when someone uses hotkeys because we don't need in fact select anything to apply a command and after that deselect to change the selection mode. It's a personal taste, of course.

[Stephan Vogt]

Unchecking the box works ok. It still has a mind of its own, once I press the space bar. I think that is the problem.
Example: I select two edges and connect. The connection is still highlighted. To go to two other edges to cut them I have to deselect the still highlighted edge. I guess I could click to deselect, but suppose I subdivide a loop and hundreds of verts are lit. Naturally you would use the space bar to deselect and then we go back to the problem I mentioned. Do you have another workflow?

On the rwx exporter, the problem depends on the model and comes at inopportune moments. So I just avoid using it. I found a file I just created a month ago using2.2.6.1. It has a lot of custom textures, so I will simplify it before I make a copy available for troubleshooting.

[oort]

Stephan,
It has been so long since I have used a version that used the old method I am not sure I understand exactly what you want.

If you turn Conditional Deselection back on (option checked), you can deselect the newly created edge/edges with space bar (after you have used connect to connect the edges) and the current mode (edge) remains active. If you hit space bar a second time you can choose another selection mode. You can always use the shortcut keys (e,v,f) to select another mode whenever you want. You probably already know all this...

Did the older versions of Wings3D allow you to set the selection mode permanently until another mode was set? Sorry I cannot remember... Is there something else you are expecting to happen/see???

oort

[micheus]

Example: I select two edges and connect. The connection is still highlighted. To go to two other edges to cut them I have to deselect the still highlighted edge. I guess I could click to deselect, but suppose I subdivide a loop and hundreds of verts are lit. Naturally you would use the space bar to deselect and then we go back to the problem I mentioned. Do you have another workflow?

I think you are talking about other thing than the "Conditional Deselection" here.

It looks like you would like to execute these commands without leaving any new resultant element selected. In this case, that is not possible.

It works that way for speed up the process. In general we cut to edges to create new connections. So get the vertices selected will help in the next step to connect them.there are other situations that will happen.

So, in this case, if you are not interested to do nothing with the resulting element you just deselect them (hitting one key).

With that settings port told you, the selection mode will stay the same until you chose another one (v, e,f,b) or hit the space bar twice ("double click").

[BazC]

Anyone using Wings on OSX Big Sur? I've downloaded 2.2.6.1 and performance is choppy on a late 2015 iMac. Rotating viewport or moving vertices is not smooth and freezes for a split second every now and then. I've used Wings on much lower spec machines in the past with no issues going back as far as a G3 iMac. I tried downloading 2.2.7 but that crashes on start up.

---

BTW I know Wings is only meant to run on Mojave or Catalina. Any idea if there are plans to run on Big Sur and/or Monterey?

[dgud]

As far as I know they should work fine, with some fixes that should be good in 2.2.7.
But I don't own a Mac anymore (won't boot) so can't test it.

I can ask Björn to test again, but I know he runs Big Sur so it (2.2.7) was tested there when it was released.

[bjorng]

Wings 2.2.6.1 did not start on my Mac (iMac from 2017 with Big Sur).

Wings 2.2.7 started, though, and I did not experiment any choppiness.

I think that you should try 2.2.7 again. Can you get it to it work if you delete the preferences file for Wings (Library/Preferences/Wings3D/Prefererences.txt in your home directory, but my sure to make a copy of it before you delete it)? When it crashes, does it leave any wings_crash.dump file?

[BazC]

Thanks for your help. I've deleted the pref and reinstalled 2.2.7 and it seems to be running fine. No choppiness in navigation either. Thanks again.

The only crash dump was from version 2.1.5

[micheus]

Nice to know about that BazC and thanks for your feedback.

Also, thanks to dgud and bjorng for help me with this subject.

[BazC]

No problem, thanks Micheus.