Port to non windows platforms (and possibly the latest stable ioquake3 as well)

[Danfun64]

q3mme appears to be windows exclusive. Not only that, but the source base is outdated. It would be really nice if q3mme was ported to use ioquake3.

[entdark]

Never to ioq3.

I am able to port to Mac and Android. But is that effort really worth?
Making features for the features sake is a nonsense.
If you tell me actual reasons why the mod has to be cross-platform then I will probably make it so.

[Danfun64]

Not everybody can run Windows. At this very moment I'm running x86_64 Ubuntu Linux right now.

More importantly, not everybody can run x86 programs. If somebody wants to run this on an ARM, PPC, or MIPS computer, for example, they can't. The closest thing your mod has to a rival, wolfcamql, is both cross platform and ioquake3 based. Wolfcamql, while capable of playing Quake 3 demos, is very much grounded in Quake Live to the point where playing Open Arena demos doesn't really work out, not to mention QL-isms like the hud and announcer sounds. To add to the irony, Quake Live can only be played on x86 platforms, while Wolfcamql can run on anything, whereas the opposite is true concerning Quake 3/Open Arena and Q3MME.

I would like both of these projects to succeed in their own way, but at the present moment wolfcamql has superior tech, not to mention the security fixes and ioquake3 features that q3mme lacks, some of the ladder may be needed for Open Arena levels to look 100% right...

Of course, this is your project, and you don't have to make these changes if you don't want to.

Out of curiosity, why do you not want to port to ioquake3? Too much work? It may or may not be a good idea to compare q3mme to whatever you based the code on, compare it to the latest ioquake3, and re-implement it manually. If you do so you probably won't have to do that work again as long as you keep the repository synced with the ioq3 rep. Again, this is your project, your decision. I'm just offering suggestions, and if you decline them, that is that.

[Danfun64]

Actually, there are two reasons why porting to ioquake3 would be wise. The first is that ioquake3, while retaining backwards compatibility with .dm_68, is starting to create new demo formats of its own that might not be 100% compatible with q3mme. Secondly, somebody might want to heard ioquake3's voip feature while replaying demos in q3mme.

[entdark]

There are many things done in ioq3 that make the game look and work not the same as id designed it. And some of those things are worse. Much worse. And they are not optional.
q3mme is more enhanced than ioq3 in many ways anyways. So it'd better say ioq3 lacks many features.

The reason you listed are not actual reasons. They are hypothetical reasons.
If ioq3 is making their own demo format that is not compatible with q3a, then they at least has to give it a new protocol number. But if they are not giving it, then it's very bad from their side.
And if more people will use that new demo format, and ask to implement it in q3mme, then I will make it.
The world does not round about ioq3.

Solving problems have to be done if the problems exist. If someone comes and says they have plenty demos with voip and it's very needed for their movie, then I will moar likely implement it.
But if you come and start imagining problems like "somebody might want to heard ioquake3's voip feature while replaying demos in q3mme" then it is not the problem.
If to think the same way, we can start imaging many other problems like, what if someone wants to run the game in 10x10 resolution window because they want it on their new Windows Watch? Yeah, that reason is exaggerated but I hope you got my point.

Do YOU need q3mme on linux and want to work with it? Or do you want the mod just runnable on there? Answer yourself at first.

As I said, I can port the mod to Mac (x86_64) and Android (x86, x86_64, armeabi, armeabi-v7a, arm64-v8a, mips, mips64) if it has the actual need.

And the project is not mine, everyone can take a part in the development.

[Danfun64]

OK then, you're not going to implement either of these. At the very least can you help me with running q3mme on wine and double or triple clicking occur when I only click once, when I don't have this bug on quake live on wine?

[entdark]

Define clicking.

[Danfun64]

...

I guess, pressing the left mouse button softly? Q3MME in Wine reads the input twice instead of the correct amount of once.

[entdark]

So mouse clicking everywhere when the q3mme window in focus?
Does it happen in demos playback? In menu? In the console?
Does it happen in quake3.exe?

Be more precise, please, I cannot read mind.

[Danfun64]

Yes
Not sure about demos playback or the console, but definately the menu.

As for quake3.exe, you'll have to give me some time, as I don't have quake3.exe set up.

[Danfun64]

I've just confirmed that quake3.exe in wine does not have this issue. Only q3mme.

[entdark]

I will see, thanks.