[RESOLVED] New com_queueevent overflow error

[Scott Archer]

I was having an issue where I woul dbe flooded with the error com_queueevent overflow and my mouse would just move down randomly. When I went back to using my desktop, I updated to the fall creators update ( Thx Microsoft) and ever since the same issue has reappeared.

The Windows 10 Fall Creators update seems to have caused this problem for a few people (Callum J has had a similar issue this evening and I believe Klaw did on Saturday.)


Update: the previous mentioned fix is ineffective (and has been removed), right now the only solution is a roll back to pre-the fall creators update of Windows 10 (or use a previous version of Windows.)
In the meantime:
If you have Windows 10, please open the Feedback app, search for the topic "SDL library has broken with the new creators update" and upvote it to get Microsoft's attention. Leaving a comment would also be appreciated.




Please be assured every effort to fix the issue on our side, and every effort to contact Microsoft to fix the issue their side, is being made.

[Serris]

As of UE 1.31 and SE 1.21, RPG-X should be saving its configurations to the root of the drive you installed it to. Try deleting your HMConfig files in both C:\RPG-X (or whatever drive you installed it on) and in AppData.

[Callum603]

As of UE 1.31 and SE 1.21, RPG-X should be saving its configurations to the root of the drive you installed it to. Try deleting your HMConfig files in both C:\RPG-X (or whatever drive you installed it on) and in AppData.

I tried this, still doesn't work for me.

I installed RPG-X on an install (and machine) that has never had it on before, tried Jack's fix, no luck for me.  Jack's fix works so long as I play at the default resolution, switching to 1920x1080 (or any other resolution) it seems to break the mouse again, in fact 1920x1080 wont allow me to tab into my game.

For reference I am on Windows 10 (unfortunately) Fall Creators Update, Version: 1709, Build: 16299.125.  Hardware just in case relevant - Intel i7 8700k, GTX 1080Ti, Mouse is a Logitech G500s (set to 2000DPI).

Just a side note, at least for me, it didn't put the RPG-X folder on the root of the drive I installed it to, instead on my C drive, which annoyed me greatly, I updated the fs_homepath in the shortcut to fix this.

[Klaw]

So this wasn't just me?! I'll include some more relevant data tomorrow

[Jack Telford]

No, it's not just you. It seems that the update has caused the issue and even when I did get it working again I was having resolution issues and alt-tab issues just like Callum. For now I rolled back my computer to the older version.

[Klaw]

A rollback (or total avoidance of the Fall Creator's Update) does appear to be the current solution.

if you rollback, be sure to mention that RPG-X is broken in that update in the comments box - who knows, maybe one of their programmers will be on the lookout, and try to fix it for later.

[Serris]

Does anyone know if the 2.4 beta Telex and Martin developed is affected by this bug?

[Callum603]

The 2.4 is affected. I tried it last night.

[Klaw]

What I read, in some frantic googling on Saturday was com_queevent : overflow had something to do with the mouse. It was seemibgly common across the quake 3 engine, but none of the threads that I read were very recent (2014 was newest, I believe).

Best guess, with barely any real facts - something in the creators update is doing something with the mouse drivers/hardware/compatibility  that it never did before

[Serris]

Klaw was right on the money. It looks like the implementation of SDL mouse input present in the rpgxEF engine isn't playing nicely with the Fall Creators Update. Until either Telex, Martin, or Microsoft can address this, the only solution is to avoid updating if you're on Windows 10.

[Scott Archer]

If you have Windows 10, please open the Feedback app, search for the topic "SDL library has broken with the new creators update" and upvote it to get Microsoft's attention. Leaving a comment would also be appreciated.


Also, every version at least back to 2.0 is affected by this bug

[Telex Ferra]

Can someone provide a more complete log of the errors?

EDIT: Found this commit in ioq3 to fix this issue. If my development VM weren't hosed I would send out a PR. Maarten, could you see if this fix works and can be incorporated into 2.4? https://github.com/ioquake/ioq3/commit/be1c71d36306637490348a128ecc2245b909c5da

[Scott Archer]

For now, a solution is to do '/in_mouse 1' in the console and then restart your game. We are looking at implementing this in the installer.
Telex, if you and Martin can get that to work, that would be fantastic!

[Ryan Stokes]

Everybody thought I was crazy when I noticed this a few months ago (maybe september or something)
I was running a Windows Insider build from the fast ring so I probably got something new that broke it back then.

Logs were useless. Callum tried to help then but we couldn't seem to pinpoint the issue. Seems he's done it now.