ThreadBoard ArchivesSite FeaturesActiveworlds SupportHistoric Archives |
whatever aw did... (Community)
whatever aw did... // CommunityryJun 7, 2006, 5:46am
in the upgrade fucked up my computer
I cant walk on 30 min visibility without totaly freezing for 4 seconds i restarted, reinstalled and still nothing it was fine before the update grr .scooterJun 7, 2006, 5:13pm
try this just to see if it makes the AV respond better (or diff) ...
set the performance tab settings in options - "keep frame rate at or near" = 30 "don't let vis fall below" = 30 (or what you want min vis to be) "limit frame rate to a max of about" = 30 then set Visibility to "Float" as setting Viz to a value over-rides those fps settings (if i understand correctly). ..Scooter [View Quote] ryJun 8, 2006, 5:48am
Hmm didnt help, but thanks.
Basically, i'll press and hold the forward arrow, ill start moving for 3 secs, then the whole world will just freeze for 4 seconds (not my computer just the 3d AW Things) and all animations stop, people stop etc... The original 4.1 release was fine on my computer, and this recent little build upgrade has done something terribly bad :( [View Quote] ryJun 8, 2006, 5:50am
Oh and also...
I reset my world (the 4.1 world server dosent put a starter object in) and I moved fine. Then I put a road at GZ (so ONE object total in the world) and it did the above mentioned lagging. So. I don't know if that helps narrow things mdown? [View Quote] sw comitJun 8, 2006, 6:20am
Try changing it to software rendering mode and see if it becomes stable;
Just as a test. [View Quote] young phalphaJun 10, 2006, 2:42am
this has worked for me...
right click desktop -> properties, settings tab, advanced button -> troubleshooting tab move the slider down until you get it stable if you need to keep having it go down until software mode kicks in, then this won't do any good for you... moving it down once to where cursor and bitmap acceleration was disabled, cleared many problems I was having that noone else was, granted this certainly isn't a long-term solution, hopefully it will be worked out eventually :) - YP [View Quote] |