I wonder if this happens only here. After the update, as soon as I moved a window for the first time, I noticed a major slowdown. I hoped it was just an impression, but then I had to accept that it was not so: window moving and resizing *are* less smooth. The perception of the slowdown is strong. For a more objective test, I used a proggie I've created in 2004 which performs various graphical operations: a particular test dropped from ~316 fps to ~260 fps.
I have a RADEON 9000 card, with the following monitor settings:
I just checked the Gears demo with the updated current beta system and OS4 Final and I also found the new release slower (116 fps instead of 132). However, I tracked down the cause:
With no "640x480" mode in my Radeon tooltypes and no "Picasso96Settings" file in Devs:, Gears was opening an 800x600 screen and running more slowly in that.
When I added a "640x480@70" mode in the Radeon tooltypes, Gears ran at its old speed again.
I don't think this is Saimo's problem on his WB, but it might be for other apps.
oh no! I use PPaint every day! I get a requester saying 'Attention Memory Save Mode' when i start it now. :/
I use PP a lot as well and that's really annoying indeed. I tried fiddling with the settings, but no matter what I do, it will insist on trying to close the WB and go in memory save mode. My guess is that it cannot handle the big numbers returned now for the CHIP memory because of the new (and great ) "unified" memory model. BTW: if you push the settings too much, it will eventually refuse to run complaining about missing blit libraries - the only way to roll back is editing by hand the prefs files or replacing them with working ones.
Quote:
And yes, window moving is slower here too.
I'm happy it's not just a problem with my setup (you know, I installed everything by hand after mounting the ISO image), but definitely unhappy with the slowdown I'd like to point out that IMHO it's not just a matter of window moving, but, a general issue with blitting (f.ex., even SDL blits are slower now).
try using the new mode tooltypes instead of the old p96 steeings file
Quote:
I have a RADEON 9000 card, with the following monitor settings: BOARDTYPE=Radeon CMPLENGTH=6 (CHIPTYPE=ATIRadeon.chip) (BORDERBLANK=Yes) (BIGSPRITE=Yes) SOFTSPRITE=No IGNOREMASK=Yes (DISPLAYCHAIN=Yes) FAKENATIVEMODES=No INTERRUPT=Yes VSYNCMIN=60 VSYNCMAX=85 HSYNCMIN=31500 HSYNCMAX=64000 SETTINGSFILE=ENVARC:Sys/P96.prefs
I know that I'm mixing the two things, but since I'm not defining any mode with the new method, the mix should not have side effect - in fact, if I remove the sync parameters from the tooltypes, nothing changes. I'm not keen on using the new method as it gives less freedom for fine-tuning and, anyway, I don't think it would change a thing given that the Picasso layer would still be there doing its job.
oh no! I use PPaint every day! I get a requester saying 'Attention Memory Save Mode' when i start it now. :/
I use PP a lot as well and that's really annoying indeed. I tried fiddling with the settings, but no matter what I do, it will insist on trying to close the WB and go in memory save mode. My guess is that it cannot handle the big numbers returned now for the CHIP memory because of the new (and great ) "unified" memory model. BTW: if you push the settings too much, it will eventually refuse to run complaining about missing blit libraries - the only way to roll back is editing by hand the prefs files or replacing them with working ones. saimo
Edit your startup-sequence, add "ADDCHIPRAM=2" to setpatch to add 2 mb of emulated chipram and get ppaint working.
Amiga user since 1985 AOS4, A-EON, IBrowse & Alinea Betatester
Edit your startup-sequence, add "ADDCHIPRAM=2" to setpatch to add 2 mb of emulated chipram and get ppaint working.
Thanks for the hint (I had just tried it after reading what you said in the "Report your 'AmigaOS 4.0 Final' bugs here!" thread). It works, but unfortunately that amount of CHIP RAM gets pre-allocated, so it is basically wasted. I'll do without, as I can live with PP trying to close the WB
I too noticed thta moving windows is slower. I just ignored it though, thinking it was just me seeing it differently. Now I've bumped into this thread, I thought I'd join in although I've not had chance to play with my Amiga since I installed the Final Update.
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
Donate
) "unified" memory model.
and speed is fantastic compared too update 4
