https://bugs.winehq.org/show_bug.cgi?id=43517
Bug ID: 43517 Summary: MadTBG.exe unable to create instance Product: Wine Version: 2.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: haakobja@gmail.com Distribution: ---
Hi,
I tried to open madTBG.exe, which is a free application bundled with madVr from http://madvr.com. When I tried to open it I get an error with the following message: "Creating madVR instance failed."
It would be nice to get this application to run, as it plays perfectly with DisplayCAL and argyll-cms.
https://bugs.winehq.org/show_bug.cgi?id=43517
Håkon haakobja@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Fedora
https://bugs.winehq.org/show_bug.cgi?id=43517
Håkon haakobja@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|2.14 |2.13
https://bugs.winehq.org/show_bug.cgi?id=43517
--- Comment #1 from Austin English austinenglish@gmail.com --- Please attach terminal output.
https://bugs.winehq.org/show_bug.cgi?id=43517
--- Comment #2 from Håkon haakobja@gmail.com --- Created attachment 58918 --> https://bugs.winehq.org/attachment.cgi?id=58918 Terminal output for madVR
https://bugs.winehq.org/show_bug.cgi?id=43517
--- Comment #3 from Håkon haakobja@gmail.com --- Created attachment 58938 --> https://bugs.winehq.org/attachment.cgi?id=58938 Terminal output for madVR using Wine-staging 2.14
https://bugs.winehq.org/show_bug.cgi?id=43517
Håkon haakobja@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|2.13 |2.14
https://bugs.winehq.org/show_bug.cgi?id=43517
Louis Lenders xerox_xerox2000@yahoo.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Ever confirmed|0 |1 CC| |xerox_xerox2000@yahoo.co.uk Status|UNCONFIRMED |NEW URL| |http://madvr.com/
--- Comment #4 from Louis Lenders xerox_xerox2000@yahoo.co.uk --- I can confirm the bug.
Looks like it`s related to:
fixme:ntdll:NtQueryTimerResolution (0x32f778,0x32f770,0x32f774), stub!
With the hack below I was able to start the program. Though I had to run with LIBGL_ALWAYS_SOFTWARE=1 wine madTPG.exe (probably because of crappy IntelGPU on my side)
I don`t know how to use the program, so I don`t know if it really works with the hack. @Hakan,maybe you could try if the hack works around the crash for you too, the at least we know where the problem is.
diff --git a/dlls/ntdll/sync.c b/dlls/ntdll/sync.c index cfb5cbc..e3e772f 100644 --- a/dlls/ntdll/sync.c +++ b/dlls/ntdll/sync.c @@ -996,7 +996,7 @@ NTSTATUS WINAPI NtQueryTimerResolution(OUT ULONG* min_resolution, FIXME("(%p,%p,%p), stub!\n", min_resolution, max_resolution, current_resolution);
- return STATUS_NOT_IMPLEMENTED; + return 0;//STATUS_NOT_IMPLEMENTED; }
https://bugs.winehq.org/show_bug.cgi?id=43517
--- Comment #5 from Louis Lenders xerox_xerox2000@yahoo.co.uk --- Last remark, maybe we can get away with setting some fixed values for the resolutions. I will write a test to see what values are given on Windows. to be continued
https://bugs.winehq.org/show_bug.cgi?id=43517
--- Comment #6 from Håkon haakobja@gmail.com --- I can verify that the program is now launching without any problems, but I have not been able to verify that it works as expected.
As far as I know, the only way to test the application is to calibrate your screen with DisplayCAL and argyll-cms, choose madVR as screen and do the calibration. When the calibration is running, the MadTBG (test pattern generator) should show alternating colors for calibration purposes.
I've currently only tried it at my Macbook pro, and there I'm unable to contact the MadTBG-application, so I'll try to compile wine on my Fedora-box, to see if I get it to work there.
https://bugs.winehq.org/show_bug.cgi?id=43517
--- Comment #7 from Louis Lenders xerox_xerox2000@yahoo.co.uk --- Created attachment 59041 --> https://bugs.winehq.org/attachment.cgi?id=59041 improve stub a bit+little test
I made kind of semi-stub by filling in the values that are returned on a win7 machine. Not sure if this is ok for wine (side-effects?), maybe it`s ok enough to send to staging?
https://bugs.winehq.org/show_bug.cgi?id=43517
--- Comment #8 from Håkon haakobja@gmail.com --- Created attachment 59048 --> https://bugs.winehq.org/attachment.cgi?id=59048 Debug log Wine32 on Fedora 26
After applying the patch and building wine on my Fedora-machine, the error box is still appearing.
I've attached the log, but I wonder if the reason is because I'm testing on a machine where Wine is installed from before and available in my PATH?
The way I ran my custom wine, was to execute wine from the build directory
https://bugs.winehq.org/show_bug.cgi?id=43517
--- Comment #9 from Louis Lenders xerox_xerox2000@yahoo.co.uk --- (In reply to Håkon from comment #8)
Created attachment 59048 [details] Debug log Wine32 on Fedora 26
After applying the patch and building wine on my Fedora-machine, the error box is still appearing.
Might be due to lacking d3d capabalities, I had run like
LIBGL_ALWAYS_SOFTWARE=1 wine madTPG.exe
Coulf you try if that works?
https://bugs.winehq.org/show_bug.cgi?id=43517
--- Comment #10 from Louis Lenders xerox_xerox2000@yahoo.co.uk --- Hi, I think the problem is not related to the NtQueryTimerResolution stub after all. Even if I comment it out in ntdll.spec I get the same error.
I think it looked like it worked because the errorwindow is behind the main window, so not visible unless you drag the main window away. Despite the error window one can click the buttons, so it looked as if it worked I guess.
For the moment I have no clue where the error comes from...
https://bugs.winehq.org/show_bug.cgi?id=43517
--- Comment #11 from Håkon haakobja@gmail.com --- Created attachment 59086 --> https://bugs.winehq.org/attachment.cgi?id=59086 Terminal output using updated Wine-main
Added a log after updating Wine to the latest source code and applying the patch. The exception still occurs...
https://bugs.winehq.org/show_bug.cgi?id=43517
--- Comment #12 from Håkon haakobja@gmail.com --- Created attachment 59087 --> https://bugs.winehq.org/attachment.cgi?id=59087 Output of run with latest wine-main
Attached a log using the latest wine source + patch and running with LIBGL_ALWAYS_SOFTWARE=1. It does not seem to make any difference. I also disabled DRI_PRIME for the latest tests, as I've had it enabled earlier. But no.. The error message is still present..
https://bugs.winehq.org/show_bug.cgi?id=43517
--- Comment #13 from Håkon haakobja@gmail.com --- Created attachment 59088 --> https://bugs.winehq.org/attachment.cgi?id=59088 Terminal output for madVR using latest wine-main on macOS
I've just tried with a new build on macOS, and it seems that the error message does not appear there.
Could it be that proprietary graphics drivers on macOS implements some functionality that's not present in the Mesa OpenSource stack?
https://bugs.winehq.org/show_bug.cgi?id=43517
Håkon haakobja@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|2.14 |2.16
https://bugs.winehq.org/show_bug.cgi?id=43517
--- Comment #14 from Håkon haakobja@gmail.com --- Created attachment 60563 --> https://bugs.winehq.org/attachment.cgi?id=60563 Terminal output for madTPG using wine-devel-3.2 WINEDEBUG=+d3d
The vanilla version of wine-devel still does not work. I've added a new debug log, but this time setting debug flag +d3d, as I was not able to find a debug flag/channel for directshow filters.
According to the madVR web-site: "MadVR is a DirectShow Filter and there are lots of other filters out there, so keep that in mind when you start changing a bunch of settings." [https://wiki.mikejung.biz/MadVR]
I'm unable to find any info about madTPG, and I do not know if it uses DirectShow functionality or not.
Also, does wine support ParticeShader 3.0? (I guess it does)
From madvr.com: "Requirements: GPU with full D3D9 / PS3.0 hardware support"
https://bugs.winehq.org/show_bug.cgi?id=43517
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #15 from Zebediah Figura z.figura12@gmail.com --- (In reply to Håkon from comment #14)
Created attachment 60563 [details] Terminal output for madTPG using wine-devel-3.2 WINEDEBUG=+d3d
The vanilla version of wine-devel still does not work. I've added a new debug log, but this time setting debug flag +d3d, as I was not able to find a debug flag/channel for directshow filters.
According to the madVR web-site: "MadVR is a DirectShow Filter and there are lots of other filters out there, so keep that in mind when you start changing a bunch of settings." [https://wiki.mikejung.biz/MadVR]
I'm unable to find any info about madTPG, and I do not know if it uses DirectShow functionality or not.
Also, does wine support ParticeShader 3.0? (I guess it does)
From madvr.com: "Requirements: GPU with full D3D9 / PS3.0 hardware support"
You want +quartz. Keep in mind, though, that it might not be a dshow-related problem.
https://bugs.winehq.org/show_bug.cgi?id=43517
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #16 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with wine-5.10?
-
wine-bugs＠winehq.org -
WineHQ Bugzilla