I tested the new version today too. Thanks Huno. The time demo on X1000 with RX550 improved from 13.4 to 14.5 fps. In game the frame rate swings from 60 to 5 fps. CPU use is pegged at 100%. It is an impressive port, although the frame rate inconsistencies mean there is still some way to go to consider the game playable.
You have to wait for quite a while. Give it a bit longer. I think mine took four minutes. I would have reset, except I got distracted by a phone call. The game started to my surprise.
My RX550 is silent too. It seems to be running as fast as I expect. Have you checked your Power prefs and saved to high? Also add the line “SYS:prefs/Power quiet” no quotes to your user-startup.
Any thoughts about having multiple installs across different physical disks all labelled with ide0.0: ? Each disk would be connected to a SATA power switch that allows only the desired boot drive to be powered up - selected before the machine is started.
If this is a possibility, then it would overcome some of the CFE boot menu loss limitation.
Thanks for the reply Hans. The RX590 fans only spin up to full speed once AmigaOS has started booting. During HW initialisation the fans are silent. This card has a bios switch for OC or silent mode it has no affect on fan speed in AOS.
The RX590 works. But the fans run constantly at full speed and it sounds like a jet plane. It is a powercolor Red Devil RX590. It is slower in gfxbench than the RX550. There is definitely something funky with the AOS support for it.
Wonder if someone could test what CPU usage they get from the Warp3DNova SDK examples? Personally I get 99% CPU use. I cannot recall if this was the same with a RadeonHD card.
Examples to try W3DNRenderToTex W3DNTextureCube W3DNBitMapCube
Tested Augustus on X1000 and RX550. Thank you for porting it. Runs stable. Feels slower than I expected - scrolling and recognising menu selections. Still perfectly playable though.
One issue that occurs each run, I notice the cursor needs to be well below the menu icon to actually activate on click? Seems like it is off target. Anyone else see this?