DisplayThreadLimit didn't change anything. However, I used Moi3D's internal mechanism which spawned Wine's version of Notepad. It might be good idea to check still that the .ini file is written in right directory. Wine can't always guess where Windows would like to save things. What would be correct (Windows) directory for the .ini? I can edit it manually, if necessary (with DOS/Windows format, of course).

Also, I tried with several ways in several viewports -- no change.

I will investigate a bit more later, now I got to go.

> What would be correct (Windows) directory for the .ini? I can edit it manually, if
> necessary (with DOS/Windows format, of course).

Under Windows it will put it under %AppData%\moi\moi.ini

When it's running under Wine it's supposed to put it instead under ~/.moi/moi.ini

You can also put it in the same directory as where moi.exe is at, it will look for it there first and use it if it finds it there.

- Michael

.ini changes were visible in Moi3D, checking .ini change status between successive Moi3D starts shows that changes were read, but problem persists.

http://koti.mbnet.fi/mmyllyma/moi3d.mp4

This is (bad) video demo of the problem.

With path extrude works; without - not.

Some betas ago it worked, so I'm wondering if it's Wine bug or some other change?

I have not had much time to use Moi3D lately, but now I'd need it in one project.

Or am I doing something completely wrong? (Wouldn't be the first...)

Any ideas?

Hi MarkkuM, thanks for making the video.

One of the things that you're doing in the video is that yes you're going to a different view but you seem to be moving your mouse frequently to the exact same elevation level as the curve. That won't really work because that's trying to make a zero height extrusion basically.

Maybe it's being somewhat sluggish to respond - what happens if you move your mouse in a side view some a ways above the curve and then just take your hand off the mouse and let it sit there for a couple of seconds, does it finish then?

Are you possibly doing a right-click as your final click instead of left click?

What happens if in the last stage of Extrude you type in a distance value like type in 5 and push Enter, does that produce a result or not?

It sort of looks there like things are running well in general, but maybe there is some kind of performance problem with inter-process communication, do you have any kind of system level stuff running like virus checking systems that might be slowing things down?

- Michael

New video:

http://koti.mbnet.fi/mmyllyma/moi2.mp4

About inter-process communication, it's a bit trick question, because this is Linux and Wine. Impossible to say if the things you suspect are even implemented. No virus scanners, though.

But if anyone has any idea, I'll test...

Hi MarkkuM, well it definitely appears that your extrude is not working there... It's fairly weird that so much other stuff is doing ok though.

Tomorrow I will give it a try on Linux myself over here and see if I can repeat that or not.

- Michael

Pretty complicated stuff (like Booleans) work, which makes this even more curious. Also, earlier this also worked. Of course, the bug might be in Wine, if so, it needs to be reported; however, that needs some background, which I'm not competent to give. You, on the other hand, are more than competent... :D

But, very much thank you for your effort! There are not many devs who support Linux at all.

Hi MarkkuM, after a few false starts with driver problems, I was able to get a current Linux setup over here. But on my system everything is working fine, I can't reproduce the extrude and revolve problems that you are seeing.

Could you tell me some specs on what you are running?

I tested here with:

LinuxMint 16 (32 bit)
Video driver: Nouveau version 1:1.0.9-2ubuntu1
Wine: wine-1.4.1
MoI: v3 beta Mar-24-2014

I tested for about 15 minutes or so constructing various things and I did not run across anything that did not work...


What version of Wine are you using?

If you're on a 64-bit OS you might try setting your Wine prefix to be 32-bit that may help to avoid some bug in 64-bit Wine which might be what you're running by default and is still rather buggy-ish apparently.

See here for how to set up your wine to be 32-bit:
http://askubuntu.com/questions/74690/how-to-install-32-bit-wine-on-64-bit-ubuntu

Basically the steps for that are to either copy elsewhere or delete your current ~/.wine directory (so that a new one will be created - note all your current installed stuff is inside of there though), and then do:
WINEARCH=32 winecfg

That should then generate a new ~/.wine directory which is set up as a 32-bit wine only, it may avoid some problems.

- Michael

Hi Michael,

this Linux box is specifically left to run at 32-bit, because I run a lot of Wine (i.e. Windows) stuff in this PC. But I have also 64-bit boxes, I just didn't want to install to several machines, because I have bought only one license from you. :D

Intel i5-750, 4GB memory
Ubuntu 12.04 LTS (32 bit)
NVIDIA Driver Version: 304.116
Wine 1.7.16
Moi 3.0 beta Mar-24-2014

Photoshop, Carrara, SketchUp and Vue work in this machine, so Wine setup is working. Also huge set of VST synthesizers work (with complex UIs).

Best,
Markku

Hi Markku, Wine 1.7.16 seems to be the current "development" version of Wine, which has stuff in it that's possibly unfinished or in progress... My best guess is that maybe you're running into some bug in Wine from running the non stable version.

According to WineHQ, the current stable release is 1.6.2, possibly that would work better for you. Over here I'm not seeing problems using Wine 1.4.1 which is just what the package manager sent down when I told it to install Wine.

Probably your best bet would be to set up a separate wine version for 1.4.1, it's possible to do that but it looks like you have to build it yourself, not get it from a pre built package (since those want to go into one central location). See here for some instructions:

http://wiki.winehq.org/FAQ#head-5d2fd5010318b5facd3ebf67930d1259e67c465f
http://forum.winehq.org/viewtopic.php?t=9630
http://forum.winehq.org/viewtopic.php?t=10041

I would think that it's likely that if you set up a build of Wine 1.4.1 and make it go into its own separate prefix like ~/.wine-1.4.1 that might work.


> Also huge set of VST synthesizers work (with complex UIs).

Yeah but it seems that something probably having to do with inter-process communication is not working... Your other programs just don't happen to use the particular thing that MoI is having problems with. Hopefully it will get fixed during their process of tuning up the 1.7 branch.

- Michael

I'll make some experiments, but I know for sure I need some features which are new in 1.7 series, so I don't want to downgrade...

However, I think I can report this as regression bug. Probably this will benefit others who use Wine and Moi.

Is it OK license-wise, if I try this on my other Linux box? I think I can install Wine 1.6 there.

Thanks anyway, I appreciate your efforts!

Hi Markku

> I'll make some experiments, but I know for sure I need some features
> which are new in 1.7 series, so I don't want to downgrade...

Yeah I don't recommend that you downgrade everything since you already have stuff working.

The links that I posted above are not for downgrading your existing wine but rather for how to set up multiple versions of Wine side by side, so that you could have a separate wine version 1.4.1 set up and be able to run MoI inside of that one, while not interfering with your existing set up.


> Is it OK license-wise, if I try this on my other Linux box? I think I can install Wine 1.6 there.

Yup, you can install the same license on any number of machines that you own, just as long as it's only actively launched and running on one at a time.

- Michael

Can I suggest from a development standpoint that you target a certain version of WINE at certain settings and list them. That way the user can manage WINE versions and include that one for MOI3d. Play On Linux allows not only multiple versions of WINE per application but also has a way to do all that automatically.

> Can I suggest from a development standpoint that you target a certain
> version of WINE at certain settings and list them.

So I guess right now that version would be Wine 1.4.1 since that's the latest one that I know for sure that works.

There are no settings that need to be adjusted, MoI v3 automatically sets up the specific settings that it needs itself (and only sets them for moi.exe specifically, it does not change any global settings for wine).

- Michael