It's only for newer gfx cards right? Tested your exe on my Sam440 Flex 800 (Radeon 9250)
Edit: Ops, just re-read you used the HunoPPC libs!
Crash at startup:
Quote:
Crash log for task "wipegame" Generated by GrimReaper 53.19 Crash occured in module wipegame at address 0x6F27E340 Type of crash: DSI (Data Storage Interrupt) exception Alert number: 0x80000003
Tested also on AmigaOne G3 800 (Radeon 9200) Again crashed, but in a different way
Quote:
Crash log for task "wipegame" Generated by GrimReaper 53.19 Crash occured in module wipegame at address 0x7F9F64C4 Type of crash: DSI (Data Storage Interrupt) exception Alert number: 0x80000003
@geennaam Something very wrong somewhere. It was 60 fps always even old warpos version of wipeout over novabridge. Over gl4es it should be MUCH faster. Seems some debug libraries used somewhere, or something involved are cause of massive slowness.
@Sinan Seems you use something which together with fixing textures for you add very big overhead in terms of speed. Are you use some other libraries ftom sonewhere or debug versions of libraries ?
Something very wrong somewhere. It was 60 fps always even old warpos version of wipeout over novabridge. Over gl4es it should be MUCH faster. Seems some debug libraries used somewhere, or something involved are cause of massive slowness.
The WarpOS game was Wipeout 2097, which is a different game of the Wipeout series. The WarpOS port of Wipeout 2097 had to be optimized a lot since it was targeted at BlizzardPPC (160-240 MHz 603e CPU with very slow RAM speed) and CyberStormPPC (150-233 MHz 604e CPU) with a CyberVision64/3D (S3 ViRGE), BlizzardVisionPPC/CyberVisionPPC (Permidia2) or Voodoo3/4/5 gfx card. Of course a game halfway usable on BPPC/CSPPC and S3 ViRGE/Permedia2/Voodoo gfx cards is very fast on current CPUs and gfx cards, even if powerpc.library has to emulate a lot of unaligned FPU accesses and in case of Wipeout 2097 additionally the DSIs caused by debug output written to unallocated Chip RAM, but you can't expect such extreme optimizations in a game rewrite targeted at current PCs and gfx cards.
Ok I'm a bit confused, it's now purely about the gl4es port of WipeOut?
Otherwise if more tests are needed I also have the possibility to test it under Qemu with the new AmigaOnXe G4 (will soon be available in Qemu Master) emulation via Wazp3D (MiniGL) it should be similar to real hardware.
@samo79
Same result as you have under Qemu Pegasos 2 with the port from SinanSam460.
MacStudio ARM M1 Max Qemu//Pegasos2 AmigaOs4.1 FE / AmigaOne x5000/40 AmigaOs4.1 FE
So do you emulate misalignment on different instructions for different PowerPC cpu models? As seen people saying they are not getting exception under emulation. So clearly it’s not that exact.
It definitely wont make sese to check, such conditions under emulation, unless your looking for bugs, of course, you can have a option increase compatibility for this corner cases. to find this bugs in software. (But running 20% slower to find software bugs, won’t be something people want under normal conditions.)
Providing none exception on alignment bug, providing exception on no alignment bug. under reporting or over reporting issues, perhaps wont be useful as well, under development.
In any case if QEMU is faster than a real Pegasus II and AmigaONE-XE/SE/Micro/Sam440/460, then people are going to stop using this old computers, they might update to newer X50x0 / X1222, or simply stick to emulation (in that case there is no issue, no point fixing the bugs). That is if people can afford a expensive Apple M1/M2 laptop, after all they are as expensive as PowerPC hardware, that people are complaining about being overpriced.
Edited by LiveForIt on 2023/9/13 18:36:53 Edited by LiveForIt on 2023/9/13 18:38:13 Edited by LiveForIt on 2023/9/13 18:39:02 Edited by LiveForIt on 2023/9/13 18:42:15
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
Thank you for your response, it’s a really very special problem, I’ve never seen that. for information I am on the port for vita and I have just set the render_gl.c in native shader and I obtain between 70 and 90 (or even more in places) of FPS. For information, there is no original problem linked to the loading of data (alignment) I will provide you with an executable later
PS: Kas1e you were right, we must shoot at least 60 fps
Emulation will always be emulation. Anyone can check the software, you just have to assign them what to check. What expensive M1 laptop ? I use the basic version of the Apple Mini m1. Price ? 1/3 X5000 when I bought ... current price 1/2 A1222+ as it will come out one day .... Second hardware X86_64 price ... don't even ask 1/10 x5000 ? Always with a few attempts no matter on what hardware an idea may arise, maybe stupid maybe not - which may be useful. But if this is unnecessary I close my "blog"