AndyFX, it starts to become
very irritating. All I see is you, shouting at bugs everywhere in the forum, but I can't even understand your posts !
It's very kind from you to report bugs, no trouble with that, but, please, do report it correctly ! It's currently not the case, at least for me.
Let me demonstrate you what I mean, using this current thread as an example (but it's almost always the case with you):
You create a new thread (this one), starting with "New BUG". Then comes a bunch of code, with only 3 lines of Raydium related code. In this code, you move the mouse yourself before calling camera_freemove, which make no sense to me (and you don't explain why you do this)
But as I try keep Raydium as bug-free as I can (and it takes me a lot of time), I decide to try to reproduce the "bug".
So I created
this file. It the very basic skel.c, where I added exactly your 3 lines (what else can I do, you don't explain anything about these 3 lines ?). And guess what, it works as it should be.
Then (because I'm very invested in Raydium, did I already said it ?), I tried to read your post a second time. A third one, ... and something randomly comes into my mind: Perhaps it has something to do with FREEMOVE_NORMAL and FREEMOVE_FIXED switchs ? (that would explain why your code shows a call to fixed camera, after all) and come with
this second demo. And guess what ? works again.
Then comes your second post, with a new bunch of code, showing a "press" variable that comes from nowhere, and where you become a bit too much aggressive to me, and where you talk about things that your code does not even shows.
The end, 40 wasted minutes.
So, it's then very simple: when you detect a bug, create the smallest possible compilable demo that shows it, and take your time to explain the bug in a understandable way. I'm not some sort of "working for free" monkey you can shout at it to correct bugs.