Zdoom 2.5.0 won't work on wine

[Blaskowitz]

I'm using linux for a while and wanted a new version of zdoom, it works but i can't do anything at all.
Perhaps i should stick with the old version 2.2.0?

[Project Dark Fox]

If you're using Linux I think you should be compiling it FOR Linux so that it works natively. Aren't their instructions for it somewhere on the wiki...?

[Gez]

Randy develops ZDoom half on Windows and half on Linux. Blzut uses Linux exclusively. We have also a lot of Linux users in this community; some are even maintaining ZDoom installation packages. And, lastly, there's a stickied "Official ZDoom on Linux thread".

So, why do you want to use WINE?

[Demolisher]

I used GZDoom in wine, worked fine. It would be VERY helpful if you state exactly what "it works but i can't do anything at all" means.

[Blaskowitz]

it means i can't move my player, can't enter console commands or enter title screen.

[Demolisher]

Ok, so the title screen never comes up? can you get to the menu? Specifically, is it just that no keyboard or mouse movements are being recognized?

[Blaskowitz]

Yep

[NeuralStunner]

Yep

To which question? All three?

[Blaskowitz]

Yep

To which question? All three?

yes.

[Enjay]

Huh?

Q: The title screen never comes up?
A: Yes, it never comes up.

Q: Can you get to the menu?
A: Yes, I can get to the menu.

Q: Specifically, is it just that no keyboard or mouse movements are being recognized?
A: Yes, no keyboard or mouse movements are being recognized.

Is that really what you are trying to say?

[Sodaholic]

I assume you wish to run ZDoom in wine for one or both of these reasons: you want 32-bit graphics in software, or you're lazy.
Am I correct?

[randi]

Randy develops ZDoom half on Windows and half on Linux.

More like 90% on Windows and 10% on Linux. I much prefer Developer Studio over anything I've run across in Linux. Whenever I think about doing something major with Linux like an OpenGL version of the Direct3D code, I think about how much it will suck without Developer Studio, and I stop right there. (I use my Linux machine mostly for leaning Japanese, rather than programming, these days.)

Anyway, your problem is probably because Wine has RawInput stubs that return success even though they do nothing. If they would return a failure, there would be no problem. Add +norawinput 1 to your command line once (it will be saved to your config), and it won't try to use the RawInput functions.

[Blaskowitz]

I am using Open Suse and it could let me open non-exe files into text so i'll do that. Thanks. (would someone mind locking it, just in case... )

EDIT: err how do you go to wine command and how does it look like?

[wildweasel]

(would someone mind locking it, just in case... )

Just in case of what? Are you afraid people will insult you? This is a perfectly legit question, and people seem willing to give you assistance.

[Blaskowitz]

Whoa i need help finding that console command.