Using smaller textures won't give you better speed, it just reduces the VRAM footprint. It's far from stable, the aforementioned problems are still there. Unfortunately I don't know how to get any debug output from Warp3D, so the visual glitches (menu, track map) will stay there for the time being.
Indeed, altrough what i also meant is that even in a 8x8 setting the game doesn't reduce so mutch its VRAM consume (and i have 128MB!) so at the end better using an higher value such 512 ecc ..
Aniway i just tested TORCS and it seems mutch better in term of VRAM consume, also stability is good
Speed in game however is quite similar to Speed Dreams (5-10 FPS using the default settings) so not very playable on my little Sam440 ...
Just one problem still, the game will crash when you switch from window mode to fullscreen (and viceversa), you can ignore the DSI but if possible would be cool if you can fix it
I don't test it on Amiga os but on pegasos ii 1266mhz and 9800pro on mos for have it playable I need to reduce the texture size this because VRAM limitation of 128mb, the best setting is under 512 . For have texture up we need 512 mb or more of vmem
@All with sam440 Don't bother with speeddream and torcs or any big games: you can't expect that such games will playable on your machines. Be in hope it will works with something like integrated radeon are naive as well :) 1ghz and r9250 for sure minimum and even that is not enough.
@SinanSam460 A RadeonHD Warp3D driver wouldn't help much, especially on Sam machines. A more modern graphics stack (Gallium3D) would be necessary. The current OpenGL implementation translates between two high level APIs, which always comes with a performance penalty. There's no support for vertex buffer objects either, which could drastically reduce the amount of data that has to be pumped through the system bus for every frame.
This is just like television, only you can see much further.
@utri007 Ultimate Stunts - This game lacks polish, it's not worth to port in in its current state. Unknown Horizons - Already on my list, see the first post. PlaneShift - No dice, uses Cg shaders. Glest - I'm pretty sure this one has been already ported by someone else.
I'd rather not add any more FPS' to my list :P
This is just like television, only you can see much further.
On TORCS: I tried an old Logitech wheel with this. First, get rid of PCI#? in libs:amigainput (and reboot). Calibrate the wheel in AmigaInput prefs by selecting USB-"wheel model"-0 and "test/calibrate". Turn the wheel all the way to the left and press the right pedal all the way down and press a button before you release the pedal. Center the wheel, stay off the pedals and press a button. Then turn the wheel all the way right and press only the left pedal all the way down and press a button. Then you can save the settings. Calibrate it also in TORCS. Worked for me.
It can be a good idea to use a different driver name for each control method, then the game calibration is needed less.
I couldn't change the view to a first person view yet, tried editing config/graph.xml but so far must have used the wrong values. Function keys crash it.
Got enough of a framerate for cruising, but I feel that it would be higher if I could get rid of the car model, with first person view.
Really appreciate BSzili's efforts here, but sadly they are let down by the absence of Warp3D and or Gallium3D. If and when they arrive, I can see the likes of Torcs and Speed dreams being great fun on AmigaOS4.
@ddni TORCS are fine on my peg2 by speed. But if you didn't have something like radeon9250 in your x1000 and only test with wazp3d, then sure will be slow.
I got the correct view working in TORCS (by F2 - sometimes it works without alignment error but just DSI). Avoid using the mouse when selecting a course and use cursor keys. I don't know how to change the track type without the mouse. Historic cars rock!
@Thematic Odd, I didn't get any DSIs while changing views, although I had a crash once in amigainput.library after toggling the help. The context became invalid somehow. Don't forget to turn of the rear view mirror if you haven't done already, it causes the scene to be drawn twice, and nearly halves the framerate. I might disable it completely, since it's buggy anyway, the colors are wrong due to some texture format mismatch.
This is just like television, only you can see much further.
-SpeedDreams fills 80% of my GFX memory when loading. And 100% when the race begins => OS freeze
But not a problem because
-TORCS runs pretty well and is playable. At least, it's very faster than SuperTuxKart. Enough to play with my son and to avoid to boot on Linux.
Thank you
Nevertheless, just 3 bugs on my system.
1) F2 to switch view causes a DSI
2) when rechoosing another race after have finished / abandoned one make the OS freeze. If I select this race after a fresh start of TORCS, it's OK.
3) when FullScreen is selected, it's impossible to fallback to windowed mode except by modifying full-screen attribute in config/screen.xml) because the mouse cursor is hidden
@zzd10h I can only give you the same advice I did give others: try to reduce the texture size. I don't want to add even harsher automatic limits, because there might be people, who doesn't use the compositor for their desktop, and have more free VRAM at their disposal.
This is just like television, only you can see much further.
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
