https://bugs.winehq.org/show_bug.cgi?id=37180
Bug ID: 37180 Summary: UnrealEd 3: mouse clicks mishandled Product: Wine Version: 1.7.25 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: pastas4@gmail.com
Clicking inside the viewports in UnrealEd 3.0 (Unreal Tournament 2004, Unreal II: The Awakening) results in nothing happening. Surfaces are not selected, and the context menu on right-click is not brought up. That prevents the user from changing level geometry in any way and adding new actors to the level. However, dragging the mouse correctly moves the camera, so the issue is only with single clicks.
In addition, selecting textures in the texture browser results in only the last texture (the one closest to the lower right corner of the browser) to be selected, instead of the one that was clicked on. These two issues are probably related to each other. Neither of these issues appear in UnrealEd 2, which is otherwise pretty similar to UnrealEd 3.
https://bugs.winehq.org/show_bug.cgi?id=37180
AntiSol antisol+winehq@antisol.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |antisol+winehq@antisol.org
--- Comment #1 from AntiSol antisol+winehq@antisol.org --- I can confirm this bug and also see the same problem in the Postal 2 editor (PostEd, based on unrealed) using wine wine-1.7.46 on xubuntu 14.04.
https://bugs.winehq.org/show_bug.cgi?id=37180
Julian Rüger jr98@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jr98@gmx.net
--- Comment #2 from Julian Rüger jr98@gmx.net --- You can help the wine devs by attaching (as text file) the terminal output (if any) that appears when clicking the viewport. You could also take a look at http://wiki.winehq.org/DebugChannels that might be helpful. (Especially when there is no output as a result of clicks inside the viewport)
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #3 from AntiSol antisol+winehq@antisol.org --- Created attachment 52105 --> https://bugs.winehq.org/attachment.cgi?id=52105 output from unrealed and posted
There is no output when I click and right click.
Nevertheless, I've attached output from both UnrealEd and PostEd.
when I click in a new viewport, I get: fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1.
but that's about it, nothing in response to selection clicks or right clicks.
I checked out the debug logging page you linked to. Thanks.
But using WINEDEBUG=warn+all gave me a bunch more messages, but nothing in response to clicking.
Using WINEDEBUG=+all gave me more than 7Gb of output before PostEd had finished starting up. At that point (10mins or so) I killed, assuming you don't want to see a 7Gb log file.
I tried WINEDEBUG=+all,-relay. This gave me a similar size output.
Care to nominate which channels I should enable debug messages for?
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #4 from Julian Rüger jr98@gmx.net --- Sorry, that was about all I know. ;)
https://bugs.winehq.org/show_bug.cgi?id=37180
tblodt@icloud.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |tblodt@icloud.com
--- Comment #5 from tblodt@icloud.com --- I can suggest +message, which displays a log for every message sent to a window procedure, to see if the editor is actually recieving the clicks.
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #6 from AntiSol antisol+winehq@antisol.org --- Created attachment 52136 --> https://bugs.winehq.org/attachment.cgi?id=52136 output from +message
Thanks, relevant output from +message attached. It prints a bunch of stuff when I click, lines ~305 - 841 (WM_LBUTTONDOWN to WM_LBUTTONUP). There's also a right-click in there starting at line 893. Hope this helps.
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #7 from AntiSol antisol+winehq@antisol.org --- FYI, I am the Linux beta tester working with Running With Scissors to try to get this working for Postal 2's editor. See: https://www.winehq.org/pipermail/wine-devel/2015-August/108758.html
If you have the skills and you would like to dig into this for us, we're happy to give you access to a copy of the editor for free to help you debug the problem. Just reply here with your email address and I'll hook you up.
Thanks!
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #8 from tblodt@icloud.com ---
From the log you attached, there's a lot of WM_MOUSEMOVE and WM_SETCURSOR
events that I ignored. Then there's a WM_LBUTTONDOWN, meaning the mouse click was recieved. Immediately after that, the editor creates a child window. I'm not sure why.
I would love to investigate further. My email address is above this comment. I can't guarantee anything, but I will work on it and report back as soon as I can.
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #9 from tblodt@icloud.com --- After reading the log file more, it looks like the bug has something to do with the fact that when you click or right click in the viewport, it creates a new child window and sets the mouse capture to that window. It then removes the window when the mouse button goes up. I will investigate further.
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #10 from AntiSol antisol+winehq@antisol.org --- Awesome, thanks! Email(s) sent with link for getting the editor and some more info.
https://bugs.winehq.org/show_bug.cgi?id=37180
gdm413229 raemochrie@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |raemochrie@gmail.com
--- Comment #11 from gdm413229 raemochrie@gmail.com --- When I click a Direct3D-powered context [viewports and the texture browser], those actions you expected didn't happen in reality and I strongly demand that a patch should exist for fixing this issue somewhere in Wine's DirectX wrapper covering DirectX 8. Unreal Engine 3 works fine, including the editor ... assuming that UE3 is DX9c, not DX8 so if someone produces an unofficial patch for the UE2 games with either DX9 renderers or native Linux editing tools, then the time that expectation and reality eclipses has come ... and the time still hasn't come. The "native Linux editing tools" idea requires a HUGE forum of people talented in reverse engineering from the potential superpowers including the most populous nation on Earth, China. Reverse engineering a project with a phenomenal scope requires a coalition of top Russian and Chinese universities to complete with necessary manpower from the reverse engineering student to the professor. The unofficial patch for the OpenGL or a DX9 rendere that's not-so experimental also has similar requirements - not so much a manpower demand as reverse engineering the ENTIRE Unreal Engine 2 to build unofficial patches with improved OpenGL renderers and editing tools that natively run outside Microsoft Windows ... but to reverse engineer the engine's rendering and input interface allowing you to still run the editor AND not suffer from "DirectInput Frustration Syndrome" or "DIFS". The situation regarding the state of the mouse handlers of the DirectInput wrapper for pre-DX9 versions should be prioritised like bringing space junk back into Earth ... due to my hope that I would be able to run the UT2004 editor flawlessly - without the dire need of installing Windows 7 and relocating my machine into North Korea so that Comrade Kim protects my machine from American eavesdropping ... preferably next to a well-maintained power station if in the Democratic People's Republic of Korea. Another catalyst to this factor is the engine uses DirectX 8 instead of DirectX 9, which didn't get as much attention and I am writing this report to attract attention to fixing the pre-DX9 wrapper libraries. My research of the UE3 version of UEd 3.0 is based on several YouTube videos ... considering that Unreal Engine 3 uses DirectX 9. I filed this comment due to a number of catalytic issues and the "Viewports don't move" catalyst is removed and there are many catalysts to remove, all to do with how Wine implements DirectInput 8. I will be glad if I can use a crystal ball with REAL and SUPER POTENT magical powers to deliver me out of this black hole of turmoil. Moving cameras, scrolling the scopes and texture browser all work fine, the issue is with the lack of proper single click handling in the Wine wrappers for versions of DirectInput prior to DirectX 9. To receive the latest bug fixes and stay up to date, use the latest development version using the Git repository. If you find this issue hard to read due to untidy structure, try studying every nook and cranny of this big long text.
Tested with Ubuntu 12.04 [Linux kernel 3.2, AMD Phenom II 955, 3.2 GHz quad core, 8 gigabytes DDR3-1333, AMD Raddeon HD 6790 1GB GDDR5 graphics memory and the ST500DM002-1BD142 hard disk] and Unreal Tournament 2004 build 3369 [DirectX 8 renderer] running on Wine 1.8-rc2-64-g71bbd8d.
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #12 from Austin English austinenglish@gmail.com --- (In reply to gdm413229 from comment #11)
When I click a Direct3D-powered context [viewports and the texture browser], those actions you expected didn't happen in reality and I strongly demand that a patch should exist for fixing this issue somewhere in Wine's DirectX wrapper covering DirectX 8.
Making demands of an open source project usually doesn't go well. Perhaps we should demand that you provide a fix.
I would be able to run the UT2004 editor flawlessly - without the dire need of installing Windows 7 and relocating my machine into North Korea so that Comrade Kim protects my machine from American eavesdropping ... preferably next to a well-maintained power station if in the Democratic People's Republic of Korea.
Good luck with that. The only well-maintained power stations are near Kim's villas and KPA military bases, which don't take kindly to foreigners of any nationality, or unauthorized domestic persons getting near them (shoot on sight).
If you find this issue hard to read due to untidy structure, try studying every nook and cranny of this big long text.
Again, not the way to get people to help you. That's a surefire way to get most people to ignore you.
Best of luck fixing your problem.
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #13 from gdm413229 raemochrie@gmail.com --- (In reply to Austin English from comment #12)
(In reply to gdm413229 from comment #11)
When I click a Direct3D-powered context [viewports and the texture browser], those actions you expected didn't happen in reality and I strongly demand that a patch should exist for fixing this issue somewhere in Wine's DirectX wrapper covering DirectX 8.
Making demands of an open source project usually doesn't go well. Perhaps we should demand that you provide a fix.
I would be able to run the UT2004 editor flawlessly - without the dire need of installing Windows 7 and relocating my machine into North Korea so that Comrade Kim protects my machine from American eavesdropping ... preferably next to a well-maintained power station if in the Democratic People's Republic of Korea.
Good luck with that. The only well-maintained power stations are near Kim's villas and KPA military bases, which don't take kindly to foreigners of any nationality, or unauthorized domestic persons getting near them (shoot on sight).
If you find this issue hard to read due to untidy structure, try studying every nook and cranny of this big long text.
Again, not the way to get people to help you. That's a surefire way to get most people to ignore you.
Best of luck fixing your problem.
A native Linux version of UnrealEd would require a new subsystem to be designed that doesn't use Windows-specific protocols and the source code behind the UT2004 3369 patch is required to make this event happen without the necessity of quantum computation ... for the quest to find the source behind the Direct3D 9 renderer found in the 64-bit version of the 3369 patch for Windows - or the full 3369 patch including the editor and it's like the holy grail of native Linux UT2004 modding without VMWare.
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #14 from gdm413229 raemochrie@gmail.com --- (In reply to gdm413229 from comment #13)
(In reply to Austin English from comment #12)
(In reply to gdm413229 from comment #11)
When I click a Direct3D-powered context [viewports and the texture browser], those actions you expected didn't happen in reality and I strongly demand that a patch should exist for fixing this issue somewhere in Wine's DirectX wrapper covering DirectX 8.
Making demands of an open source project usually doesn't go well. Perhaps we should demand that you provide a fix.
I would be able to run the UT2004 editor flawlessly - without the dire need of installing Windows 7 and relocating my machine into North Korea so that Comrade Kim protects my machine from American eavesdropping ... preferably next to a well-maintained power station if in the Democratic People's Republic of Korea.
Good luck with that. The only well-maintained power stations are near Kim's villas and KPA military bases, which don't take kindly to foreigners of any nationality, or unauthorized domestic persons getting near them (shoot on sight).
If you find this issue hard to read due to untidy structure, try studying every nook and cranny of this big long text.
Again, not the way to get people to help you. That's a surefire way to get most people to ignore you.
Best of luck fixing your problem.
A native Linux version of UnrealEd would require a new subsystem to be designed that doesn't use Windows-specific protocols and the source code behind the UT2004 3369 patch is required to make this event happen without the necessity of quantum computation ... for the quest to find the source behind the Direct3D 9 renderer found in the 64-bit version of the 3369 patch for Windows - or the full 3369 patch including the editor and it's like the holy grail of native Linux UT2004 modding without VMWare.
Try debugging a Wine instance of UT2004's UnrealEd with GDB, that is one way to find the bug that I want fixed and staged.
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #15 from gdm413229 raemochrie@gmail.com --- Created attachment 55886 --> https://bugs.winehq.org/attachment.cgi?id=55886 UnrealEd 3.0 selection-prohibiting bug evidence from the Unreal Engine 2's perspective.
This is the evidence provided to me via the log window of UT2004's UnrealEd.
https://bugs.winehq.org/show_bug.cgi?id=37180
Adam mad.magicmyth@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mad.magicmyth@gmail.com
--- Comment #16 from Adam mad.magicmyth@gmail.com --- Just wanted to add that there is a known bug with UnrealEd 3 that produces this same behaviour of not being able to simply (right/left) click without going into a drag operation. It is caused by the user having anti-aliasing forced on the app (via driver). Hopefully that might give wine devs a hint as to what is going wrong here?
Note I tried forcing MSAA off via winetricks but that had no affect (plus it does not look like anti-aliasing is taking place anyway based on rendering edges).
https://bugs.winehq.org/show_bug.cgi?id=37180
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #17 from Fabian Maurer dark.shadow4@web.de --- Is there a free demo of this?
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #18 from GreatEmerald pastas4@gmail.com --- Yes, in fact there is, it's called Unreal Engine 2 Runtime: https://docs.unrealengine.com/udk/Two/UnrealEngine2Runtime22262002.html
The download link is dead, but it's available on the web archive: http://web.archive.org/web/20061123114124/http://udn.epicgames.com:80/Files/...
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #19 from AntiSol antisol+winehq@antisol.org --- Is that the correct version? Based on the filename it looks like that might be unrealed 2 rather than 3 (i.e it's for UT99 rather than UT2004), and the different versions of unrealed don't have the same issues. You should (IIRC) be able to double-check the version in help->about, and there might be a "2" or "3" included in the splash screen. This bug only occurs in 3.
If you see my comment at https://bugs.winehq.org/show_bug.cgi?id=37180#c7 there's info on getting a free copy of Postal 2 (same engine and editor) from Running With Scissors. If you email Jon @ RWS (see the mailing list post for email) he may still be willing to give you a free game key if you're willing to look into this. Note however that this was a couple of years ago and Jon and I were very underwhelmed by the response (we had one response who took his free game key and then we never heard another word from him), so it's possible he'll be less receptive now. Also don't reply to the mailing list thread, Jon won't see it, he unsubscribed after a few weeks.
If you have any trouble getting in touch with him let me know and I'll see if there's anything I can do.
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #20 from GreatEmerald pastas4@gmail.com --- It is the correct version. "2226" stands for the Unreal Engine 2 patch version, which corresponds to Unreal Tournament 2003, which uses UnrealEd 3.
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #21 from AntiSol antisol+winehq@antisol.org --- OK, awesome, thanks!
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #22 from Fabian Maurer dark.shadow4@web.de --- (In reply to GreatEmerald from comment #18)
Yes, in fact there is, it's called Unreal Engine 2 Runtime
How do I test this issue with that runtime? Because I don't see anything obviously broken, it doesn't seem to require mouse input on the map.
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #23 from GreatEmerald pastas4@gmail.com --- (In reply to Fabian Maurer from comment #22)
How do I test this issue with that runtime? Because I don't see anything obviously broken, it doesn't seem to require mouse input on the map.
You need to run System/UnrealEd.exe, then load the map, then right-click in the 3D viewport. A context menu should appear, but it doesn't.
https://bugs.winehq.org/show_bug.cgi?id=37180
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #24 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with vanilla wine-4.5?
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #25 from AntiSol antisol+winehq@antisol.org --- (In reply to joaopa from comment #24)
Does the bug still occur with vanilla wine-4.5?
yes
https://bugs.winehq.org/show_bug.cgi?id=37180
pattietreutel katyaberezyaka@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |katyaberezyaka@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #26 from MagicMyth mad.magicmyth@gmail.com --- Just adding that this bug is still present in Wine 5.0-rc1.
Is there anything more information any developer wants to help resolve this issue? If so just let me know what is useful and I'll try to help.
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #27 from joaopa jeremielapuree@yahoo.fr --- A lot of work was done for dinput,xinput... Does the bug still occur with wine-7.0-rc5?
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #28 from AntiSol antisol+winehq@antisol.org --- (In reply to joaopa from comment #27)
A lot of work was done for dinput,xinput... Does the bug still occur with wine-7.0-rc5?
yes
https://bugs.winehq.org/show_bug.cgi?id=37180
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW
--- Comment #29 from Fabian Maurer dark.shadow4@web.de --- I tested on windows according to comment 23, and I don't get any context menu. For me the problem is that the mouse locks into areas and can't be moved out, and that left/right mouse button can't be used to look around the terrain.
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #30 from AntiSol antisol+winehq@antisol.org --- (In reply to Fabian Maurer from comment #29)
I tested on windows according to comment 23, and I don't get any context menu. For me the problem is that the mouse locks into areas and can't be moved out, and that left/right mouse button can't be used to look around the terrain.
what version of windows did you test on? it may not work with modern versions, I wouldn't know what versions it's compatible with, I've never used it on anything newer than XP.
Also, If you're running it in a VM, you won't see the same behaviour as on real hardware. IIRC you get no context menu in virtualbox, but I can't remember the exact details, it's been ~7 years since I tried it in a VM.
On windows XP, on real metal, a context menu appears.
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #31 from Fabian Maurer dark.shadow4@web.de ---
what version of windows did you test on? it may not work with modern versions, I wouldn't know what versions it's compatible with, I've never used it on anything newer than XP.
I tested on Win11, the only real Windows installation I have.
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #32 from MagicMyth mad.magicmyth@gmail.com --- I can confirm the issue still exists on wine 7.0-rc2.
It does seem this issue (plus others) started happening on Windows 10 with modern GPU drivers at some point as well going by the forum thread at:
https://www.epicgames.com/unrealtournament/forums/past-unreal-tournament-gam...
Seems some people found that forcing software rendering got it somewhat working on Windows 10. I tested on Plasma with compositing disabled but that had no affect.
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #33 from joaopa jeremielapuree@yahoo.fr --- At least, can an administrator put the link at URL place? http://web.archive.org/web/20061123114124/http://udn.epicgames.com:80/Files/...
https://bugs.winehq.org/show_bug.cgi?id=37180
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |http://web.archive.org/web/ | |20061123114124/http://udn.e | |picgames.com:80/Files/UE2/R | |untime/UE2Runtime-22262002_ | |Demo.exe
https://bugs.winehq.org/show_bug.cgi?id=37180
--- Comment #34 from AntiSol antisol+winehq@antisol.org --- (In reply to joaopa from comment #33)
At least, can an administrator put the link at URL place? http://web.archive.org/web/20061123114124/http://udn.epicgames.com:80/Files/ UE2/Runtime/UE2Runtime-22262002_Demo.exe
lol, no, that would require more effort than pasting in the good old "I can't be bothered investigating so I'm just going to ask if I can close this" message that we keep seeing every few years.
I for one am looking forward to chatting with you all again to confirm that, yes, the bug still exists in ~2025 and that perhaps actually investigating it would be prudent, rather than repeatedly asking if it magically went away.
Maybe we'll have unrealed running on a good emulation layer inside the browser by then and won't even need wine.
I live in hope.
-
wine-bugs＠winehq.org -
WineHQ Bugzilla