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.