News:

 

Topic: Making NVil run on Linux...  (Read 4669 times)

0 Members and 1 Guest are viewing this topic.

  • No avatar
  • Posts: 948
  • Polygon
October 01, 2019, 04:42:22 pm
It doesn't disable anti-aliasing. It enables it for the whole WINEPREFIX, so it should affect all programs that you have installed in it.

  • No avatar
  • Posts: 948
  • Polygon
April 22, 2020, 08:19:23 am
I tried to create a new 32-bit wineprefix for NVil by following the list of winetricks verbs that I once posted, but starting NVil always ends up with:
Code: [Select]
002d:err:ole:CoGetContextToken apartment not initialised
and the interface looking like in this post.
I tried many combinations of various dotnetxx verbs to no avail.
Dotnet40 by itself isn't sufficient, because SlimDX installation will fail with the following error message:
Code: [Select]
DXSETUP.EXE - .NET Framework Initialization
Unable to find a version of the runtime to run this application.
Installing dotnet3x seems to solve this.

If anyone is able to run NVil on a 32-bit wineprefix, and can reproduce a working installation every time, please post your Wine version and the list of winetricks verbs that you use. Thanks.

  • Posts: 497
  • Triangle
July 26, 2020, 12:50:15 am
Nvil (32 bit) is now working Ok for me with Play on Linux and wine 5.13. Must have been some recent updates to wine which has made it go from not being able to generate the interface to working Ok.

It does have black bars top and bottom of the splash screen and ampersands after all the menu items but apart from that seems to run Ok on my initial tests of running a few commands on a cube.

Nvil (64 bit) still crashes though
« Last Edit: July 26, 2020, 05:30:31 am by kevjon »

  • No avatar
  • Posts: 948
  • Polygon
July 29, 2020, 08:56:25 am
Kevjon, did you have to install any additional components (like dotnet46, d3dx9, etc.), or does it work with Mono now?
Last time I tried to run NVil on Wine 5.5 (development) I couldn't get it to work at all.

  • Posts: 497
  • Triangle
July 30, 2020, 09:53:29 am
RD

I just did a clean 32bit install in play on linux with a new virtual drive and it works without any additional components installed or fonts. I did install slimdx x86 of course into the virtual drive.

I am using Solus Budgie with kernel 4.9.227-160.lts
I also am using AMD RX580 graphic card which uses the kernel drivers rather than AMD's proprietary drivers.
« Last Edit: July 31, 2020, 06:55:24 am by kevjon »

  • No avatar
  • Posts: 948
  • Polygon
August 05, 2020, 07:06:06 pm
I just did a clean 32bit install in play on linux with a new virtual drive and it works without any additional components installed or fonts. I did install slimdx x86 of course into the virtual drive.

I am using Solus Budgie with kernel 4.9.227-160.lts
I also am using AMD RX580 graphic card which uses the kernel drivers rather than AMD's proprietary drivers.
Thanks. So it works with just Mono now, that's good news.
I just launched NVil on Wine 5.13/PoL and indeed it runs smoothly, though I need to test it more.
I'll give 64-bit version a try once Wine 5.13 amd64 shows up in PoL downloads.

  • Posts: 497
  • Triangle
August 06, 2020, 02:21:10 am
I have found that radial menus cause objects to disappear momentarily and after using a radial menu short cut keys get stuck till you hit them again.

You can probably work around this issue with hot windows rather than radial menus. I need to test further.

  • No avatar
  • Posts: 948
  • Polygon
August 06, 2020, 12:28:45 pm
Yeah, the problem with brief disappearance of the scene caused by radial menus is something that I've been seeing since Wine 3.20. It's very annoying, so I had to completely rebuild my config by moving stuff from radial menus to User Tool Windows.

I don't use hot windows anymore because they cause the viewport to blink. Also, on several occasions I saw hot windows breaking and not being rendered again until I restart NVil.

Does NVil crash your PoL wineprefix when you try to exit the program? NVil saves config changes on exit, so the crash (which happens every time), makes it impossible to save user preferences.
« Last Edit: August 06, 2020, 12:35:29 pm by rubberDuck »

  • No avatar
  • Posts: 948
  • Polygon
August 06, 2020, 12:37:53 pm
Here's the output of PoL debugger:
Code: [Select]
=================================================================
    Native Crash Reporting
=================================================================
Got a UNKNOWN while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

=================================================================
    Managed Stacktrace:
=================================================================
      at <unknown> <0xffffffff>
      at NtDll:NtQueryDirectoryFile <0x00012>
      at System.IO.Enumeration.FileSystemEnumerator`1:FindNextEntry <0x000b7>
      at System.IO.Enumeration.FileSystemEnumerator`1:MoveNext <0x001a7>
      at System.Collections.Generic.LargeArrayBuilder`1:AddRange <0x00115>
      at System.Collections.Generic.EnumerableHelpers:ToArray <0x00167>
      at System.IO.MonoLinqHelper:ToArray <0x00037>
      at System.IO.DirectoryInfo:GetFiles <0x00067>
      at System.IO.DirectoryInfo:GetFiles <0x00037>
      at System.IO.DirectoryInfo:GetFiles <0x00063>
      at DigitalFossil.AnimationDesign.AnimationDesignGraphicWindow:OnClosing <0x003e3>
      at System.Windows.Forms.Form:OnClosing <0x0007a>
      at System.Windows.Forms.Form:WmClose <0x00351>
      at System.Windows.Forms.Form:WndProc <0x00257>
      at DigitalFossil.AnimationDesign.AnimationDesignForm:WndProc <0x0006f>
      at ControlNativeWindow:OnMessage <0x0002f>
      at ControlNativeWindow:WndProc <0x00136>
      at System.Windows.Forms.NativeWindow:Callback <0x000cc>
      at System.Windows.Forms.NativeWindow:Callback <0x00067>
      at <unknown> <0xffffffff>
      at DevExpress.Utils.Win.Hook.ControlWndHook:CallWindowProc <0x00012>
      at DevExpress.Utils.Win.Hook.ControlWndHook:WindowProc <0x000df>
      at DevExpress.Utils.Win.Hook.ControlWndHook:WindowProc <0x00067>
      at <unknown> <0xffffffff>
      at System.Windows.Forms.UnsafeNativeMethods:CallWindowProc <0x00012>
      at System.Windows.Forms.NativeWindow:DefWndProc <0x000af>
      at System.Windows.Forms.NativeWindow:DefWndProc <0x00073>
      at System.Windows.Forms.Control:DefWndProc <0x0002f>
      at System.Windows.Forms.Form:DefWndProc <0x0013f>
      at System.Windows.Forms.Control:WndProc <0x004f6>
      at System.Windows.Forms.ScrollableControl:WndProc <0x0007b>
      at System.Windows.Forms.ContainerControl:WndProc <0x0004b>
      at System.Windows.Forms.Form:WmSysCommand <0x001e7>
      at System.Windows.Forms.Form:WndProc <0x00383>
      at DigitalFossil.AnimationDesign.AnimationDesignForm:WndProc <0x0006f>
      at ControlNativeWindow:OnMessage <0x0002f>
      at ControlNativeWindow:WndProc <0x00136>
      at System.Windows.Forms.NativeWindow:Callback <0x000cc>
      at System.Windows.Forms.NativeWindow:Callback <0x00067>
      at <unknown> <0xffffffff>
      at DevExpress.Utils.Win.Hook.ControlWndHook:CallWindowProc <0x00012>
      at DevExpress.Utils.Win.Hook.ControlWndHook:WindowProc <0x000df>
      at DevExpress.Utils.Win.Hook.ControlWndHook:WindowProc <0x00067>
      at <unknown> <0xffffffff>
      at System.Windows.Forms.UnsafeNativeMethods:DispatchMessageW <0x00012>
      at ComponentManager:System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop <0x006ab>
      at ThreadContext:RunMessageLoopInner <0x00749>
      at ThreadContext:RunMessageLoop <0x0005b>
      at ThreadContext:RunMessageLoop <0x00087>
      at System.Windows.Forms.Application:DoEvents <0x0003b>
      at DigitalFossil.AnimationDesign.StartForm:Run_InMainThread <0x000f7>
      at DigitalFossil.AnimationDesign.StartForm:Run_InMainThread <0x00063>
      at DigitalFossil.AnimationDesign.StartForm:Main <0x02453>
      at <Module>:runtime_invoke_void_object <0x0006c>
=================================================================
wine: Unhandled page fault on read access to 00000000 at address 00000000 (thread 0024), starting debugger...
winedbg: Internal crash at 0x7bc25319

  • Posts: 497
  • Triangle
August 08, 2020, 11:03:56 pm
I customised the interface by adding a button with the command "open box tool" to usertools1 window. Checked that it worked then closed Nvil.

When I restarted Nvil the button and window was still there.

When I started Nvil in PoL with the Debug Option it did not show any errors on closing it down.

Quote
I'll give 64-bit version a try once Wine 5.13 amd64 shows up in PoL downloads.
I know at the moment I cannot get the 64 bit version of Nvil working as Slimdx64 is looking for dotnet4.0 and I cannot install that with PoL in a 64 bit virtual drive. Presumably someone needs to write a 64 bit version of dotnet4.0. Will amd64 solve that ?

  • No avatar
  • Posts: 948
  • Polygon
August 09, 2020, 11:37:20 am
I see. Hmm, perhaps it's the proprietary nvidia-driver that crashes wineprefix on my end. Everything is possible with closed source software.

Regarding 64-bit, what I meant is running NVil with Mono 64-bit instead of dotnet4x. 64-bit version of Wine 5.13 is still unavailable in PoL, so I guess we can't try this path yet.

  • No avatar
  • Posts: 948
  • Polygon
August 09, 2020, 04:27:31 pm
So, IStonia implemented a command for saving user settings on demand, which will be handy regardless of whether one runs NVil on Windows or Wine:
http://digitalfossils.com/nvil-forum//index.php?topic=4977.msg18439#new

I tested this command on dotnet4x and Mono PoL wineprefixes, and it crashes big time on the latter. Might be something with how Mono handles serialization functions used by dotnet to dump program's configuration to XML files. I only wonder why it doesn't crash on your machine. Maybe your wineprefix uses a different Mono version?

Could you please run find -iname "wine-mono*" in your wineprefix path and post the output of this command? It should be something like:
Code: [Select]
/home/***/.PlayOnLinux/wineprefix/nvil32_mono/drive_c/users/***/Local Settings/Temporary Internet Files/Content.IE5/9G05QPLX/wine-mono-5.1.0-x86
« Last Edit: August 09, 2020, 04:29:28 pm by rubberDuck »

  • Posts: 497
  • Triangle
Yesterday at 12:16:12 am
Hi RD

When I search using this command
find /home/****/.PlayOnLinux/wineprefix/Nvilx32 -iname "wine-mono*"
Note: I used my username rather than asterisks in the path.

"wine-mono*" is not coming up with anything

I checked I was using the find command correctly by searching for other files in the Wineprefix and it found those files Ok.

BTW On the same computer I have Nvil 32 bit running in PopOS 2004. I did however have to install Dotnet40 with PoL to install slimdx. I was able to save customise changes Ok in this one also. I ran find on its wineprefix for "wine-mono*" and it also came up with nothing.

  • No avatar
  • Posts: 948
  • Polygon
Yesterday at 12:10:43 pm
Okay, thanks.
I have just created a Wine 5.13 Staging wineprefix and saving preferences doesn't crash NVil anymore.  8)
Must have been something with vanilla 5.13 which my system didn't like.

  • Posts: 497
  • Triangle
Yesterday at 01:36:02 pm
Good news RD

In PopOS 2004 I now have Nvil working in a 64bit wine prefix using system wine which is 5.0

I grabbed the DirectX9.0c installer from an old game (IL2) and installed that with PoL. (I couldn't get the web installer to work when downloaded from microsoft as it looks for the required Microsoft OS)
I downloaded DotNet4.0 x64 package from Microsoft and installed that with PoL
I then installed slimdx64 with PoL
Installed Corefonts & Tahoma from PoL

It has the same issues as the 32 bit versions, black bars on splash, menu ampersands, radial menu temporarily causes objects to disappear etc
It is also saving my config changes without issues.