Hum... Karlos wrote on this forum he have the source of Warp3D : I sent an MP because I found a possible bug in the W3D_Picasso96MU.library in the function W3D_P96MU_AllocVMem. I fixed by myself, but absolutly not sure of my fix...
When I launched GLBlitzQuake just after a boot, I had planned fps. By cons, when I booted up another Warp3D program just before as Cow3D for example, then I was getting about 0.5 fps less with the same GLBlitzQuake...
I GOT AN ANSWER !! YES !!!
He said to me, he need an authorization to help me... And I'm still waiting since more than 1 year now...
If it's not a conspiracy, what is it ?
Have you ever worked in an enterprise? People are busy there, communications got lost. It's not because somebody wanted to act bad on you, it is just because the issue was lost. The answer is simple: Try again, be more persistent, try other means of communication. If, after two weeks, you do not get an answer, it does not mean that they don't want to fix the problem. It only means that the issue got lost because people are busy. This happened more than once to me.
I can tell you another story: I found a bug in the proprietary NVIDIA driver for the Linux kernel. As soon as I enabled panning, the screen was showing trash in the extended window area. I reported the bug to NVIDIA. I got a silly reply saying "I cannot reproduce the problem". I could reproduce it on four machines, with four different generations of NVIDIA cards.
Hence, I checked carefully where the bug was coming from, going though the code and observing return codes, until I found a function returning wrong values, or seemingly wrong values. I communicated with mailing lists of the kernel and X11 folks, trying to understand whether I guessed correctly. And finally got contact with the developers, more by accident, because apparently the NVIDIA folks also read the intel-core developer mailing lists: Problem is that NVIDIA only implements xrandr 1.2, not xrandr 2.0, and their panning function is a hack on top of xrandr 1.2 which does not implement the xrandr 2.0 interface correctly.
Now, does that mean that NVIDIA has started a conspiracy to prevent people from using Linux? Not the least! It just means that this is a typical enterprise, with many many levels of responsibility between the "customer care" (people that are usually just technical expert enough to tell you how to install a graphics driver) and the actual developers. It also means that I used - apparently - a feature that is seldom required, and they simply didn't think of all the consequences clearly of instead implementing xrandr 2.0 cleanly rather use a proprietary xrandr 1.2 extension. No conspiracy here. Just the usual lazyness. Most folks have better things to do than to serve you and solve your personal problems...
Now in this case here, the story is much simpler: You *do* have the developer at your hands, you do not need to get through a "customer (we do not) care" "service simulation", but you can ask directly.
So now, once again: Why didn't you just make your life easier and wrote an email?
There is *still* enough time to get mad at people later, but certain things should be done in the right order. First ask. Then shoot.
Got it?