I didn't get any DSIs, so you have to give me the exact steps on how to reproduce them. I'll delete libsmpeg.so from my SDK, the linker always links to it instead of the static library.

Oh boy, where should I begin... It looks like I picked the wrong game for my first port. RTTR bots have a nasty bug which sometimes corrupts the heap. Problems like these are pretty time consuming to track down, and right now I'm busy with university assignments and exams.
Still, I didn't want to look like some wanker, who accepts a machine donation for nothing. I was in a desperate rush to find something I can port quickly, and will most likely be stable. In the end I chose Odamex, which is a multiplayer-oriented Doom port. It comes with a fully functional server browser (except for the file chooser). I know, it's an FPS, but had to improvise

http://bszili.morphos.me/ports/odamex-os4.lha

PS: I just noticed I forgot to convert the icons into the OS4 format... I'll reupload it later.

PPSSPP also uses C++11 features, so you couldn't compile it with GCC 4.2.x anyway.

@fryguy
You shouldn't overwrite the included xadopus.module with the old version on aminet. I fixed a couple of bugs, and added support for password protected archives.

@ScottCabit
fryguy had the guru because he didn't have the DOPUS5: assign, which is the exact opposite of your problem. If you have an assign to the wrong path you will have DSI's and whatnot.

Actually the executable creates that assign at startup if it doesn't exists, so this is definitely a bug. I have a clean 3.1 hardfile somewhere, I'll check out if I can reproduce this.

@saimo
I replied that to 328gts, because he was convinced that no one is willing to vote here
As for the voting process, it took me for a while to figure out what's going on. It's a bit confusing to have multiple games on the page.

@328gts
Don't assume no one has voted just because they didn't announce it. I for one voted 2 times from 2 different browsers.

A slightly more interesting screenshot:
http://s1064.photobucket.com/user/BSz ... /AmigaOS4/trans2.jpg.html
I doesn't download anything yet, because a function clogs the event handler in libtransmission. (On the screenshot I have no connection to the router, before someone points it out :) )

I've done it again... The RAM arrived, I put it in, and it didn't work well. I've read at many places that older Pega2 revs are fine with 2x512 MB, if I use the same exact brand, type, etc. Nevertheless I got the usual memory corruptuon problems, crashes, random transfer errors, graphic glitches. Mind you both modules work fine by themselves.
Now I'm left with a slightly corrupted SFS system partition, and 512 MB RAM. I might try SFSDoctor on MorphOS. I know OS4 and MOS SFS are not exactly compatible, but I have to reinstall OS4 anyway, so I have nothing to lose. I have two questions regarding my little venture:

1) Does anybody have a Pegasos II Rev 2B3 compatible 1024MB DDR module lying around? I don't have the money and fortitude to weed though all the 128x4 high density junk on the net

2) What FS has the best revovery tools I could use for my system partition? FFS2?

edit: Meanwhile I tried SFSDoctor 1.1, and it fixed the block read error. Fortunately I used SFS\00 which seems to be compatible enough.

Just to give you all a heartbeat: http://s1064.photobucket.com/user/BSz ... gaOS4/trans-grab.jpg.html
It's not working yet, libtransmission still needs a lot of work.

@utri007
Unity is a proprietary closed source engine. It couldn't be ported even if it was open source without programmable shaders.

@kas1e
You misunderstood the purpose of the counter. Look at this example:

The patches have to be removed one-by-one, when their counter is zero.

@kas1e
There is no mystery here. The fullscreen/window switches involve tearing down the old window and GL context, so the texture get flushed as well. This doesn't happen in games where the whole graphics subsystem is restarted, and the textures are reloaded "manually".

@kas1e
And how is that different from what snoopium does? The trick is how you remove the patches. Snoopium for example adds an counter to each patched function, and atomically increases/decreases it when the function is called. This way you don't remove a patch when the function is in use.

@kas1e
The credit crash is a known issue, and I'll fix it soon. I'm more worried about the one when I try to save/load games.
I can't fix the other one, it looks like Warp3D/MiniGL and SDL's on-the-fly fullscreen switching don't play nice together. I'll disable that, e.g. you'll have to restart the game to switch to fullscreen.

@kas1e
Magellan crashes AROS too, when I expunge dopus5.library with an "avail flush", so this issue isn't specific to OS4. It probably would do the same on MorphOS too... I'll try to figure out how programs like NetworkSnoop or Snoopium remove their patches without crashing the system.

@broadblues
Thanks for confirming this.

@all
New test version: http://www24.zippyshare.com/v/15301278/file.htm
It should fix most of the problems mentioned before. Network play, and singleplayer against bots should work. There's one catch though, you can't save/load the game without getting unknown errors. The crashes happen mostly at random delete calls. Anyone knows what causes these type of errors? How could I debug this? And no, it's not causes by the small stack

@kas1e
This is not some obscure hard to reproduce bug. MiniGL advertises to support 2048x2048 textures, but it won't load them. If you want me to make a test case, then it can be arranged. I just googled "opengl textured quad", and this is what come up: http://www.gamedev.net/page/resources ... ping-an-introduction-r947

edit: Again, this is not about the texture size supported by the hardware, but the inconsistency in minigl.

@kas1e
There's no need for me to make one, it can be reproduced with any OpenGL program. You just have to replace one of the textures with a 2048x2048 one.