Thief III FM: Special Vintage Sept. 27/05 - by Gonchong
potterr on 1/10/2005 at 09:50
Try reducing further until it does not load up anymore then increase each slightly. Its a bit hit and miss at the moment as to what is the best settings for FMs
Kin on 1/10/2005 at 10:40
I reduced them to this point
[PCVertexPools]
DynamicVertexPool=3200000
StaticVertexPool=2700000
StaticShadowVertexPool=2100000
But i see no change at the jerky movement of the camera.
Should i hit a specific numbers or i have space for tryig different numbers?
If i decrese slightly (about hundrent numbers) it crashes before the loading screen just right after the black screen after i hit play.
Also here is the user.ini after those setings above
[BlockLoading]
LoadFromResourceBlockFiles=True
[Source Control]
UseSourceSafe=0
[Engine.Engine]
UpdateGameSys=0
[PCVertexPools]
DynamicVertexPool0=31457280
StaticVertexPool=2700000
StaticShadowVertexPool=2100000
DynamicVertexPool=3200000
Have no idea what those are but i think aomething has been added. :erg:
potterr on 1/10/2005 at 11:13
That looks ok at the moment, try reducing one number out of the 3 until it crashes, then raise it slightly, and repeat for each one. At some point you should see an improvement in frame rate. As mentioned before its hit and miss as to the best settings at the moment. Once I find out what peoples standard best working settings are I can updated GL to use that for FMs with no user.ini file changes.
Kin on 1/10/2005 at 11:50
So you can modify GL to atomaticaly detect the requirements of every FM and modify the ini file according to the mission requirements? :D
How you do all those things potterr, you are amazing. Well done and keep going.
potterr on 1/10/2005 at 11:55
Its partly to do with the user_patch.ini file the FM authors make. GL uses this to patch your user.ini file according to what the FM needs, if no user_patch.ini exists GL uses its own settings. However this is not an exact science yet and will need to be refined to work better. So at the moment I am looking for teh best settings on peoples PCs and the specs of the PCs as I may have to do a slight calculation to work out the best size. The thing is though that if all authors set their FMs up as best as possible first off then GL wouldn't need to do so much of this, but then its a hard thing for the authors to try and work out properly as thier FM may run fine on their PC and the beta testers PCs but not on everyones.
GlasWolf on 1/10/2005 at 16:13
This is just a hunch, but I suspect that the lowest vertex pool settings that will allow a mission to work will be the same on any machine. If they're not optimised though (like the original "add a zero to all the entries") then you'll run into problems with lower spec machines.
Kin on 1/10/2005 at 16:32
I got them here
[PCVertexPools]
DynamicVertexPool=0
StaticVertexPool=2620000
StaticShadowVertexPool=2080000
And i see very little difference in FPS
In rooms with low poly count it works fine but the camera jerks on larger and complex areas.
That zero on Dynamic vertex looks strange to me.
potterr on 1/10/2005 at 17:15
I think this may take a bit of time to work out the best optimisation fot the levels. I would have expected a better frame rate though.
Kin on 1/10/2005 at 18:20
Quote Posted by potterr
I think this may take a bit of time to work out the best optimisation fot the levels. I would have expected a better frame rate though.
Well i think it is the only problem that remains to be solved so we all can taff with T3 FMs for good.:cheeky:
Great job potterr!!! I believe you will find soon the solution:thumb:
Martin Karne on 1/10/2005 at 22:17
Ok at the start you got me there, oh no another weaponless bloodless violenceless fm, but I have found the weapons, so butchering or knocking up and the down the place.
Nice job, I had to run away from guards for a few times.
:eek:
