Hi,
Well because of the insane lack of no linux server, i was trying to create some UT3 love with VMWare. Well it works fine no errors, but when i connect and the match starts, walking goes fine, but when more FPS needed, it goes terrible laggy. It's not the HW that makes it slow, the cpu is Dual Xeon 3,1ghz and 2gb ram. The cpu is only used 30-40% and ram isnt even close to full.
So my question is, why does the UT3 server turn out so laggy (but not laggy as i normally experience with online gaming) on a VMWare setup? Is there any known info about this, should i install something? And oow yea, the server is connected to a 1Gbit fiber connection, so its definatly not the link-speed either.
This is all errors i get in startup log:
Well because of the insane lack of no linux server, i was trying to create some UT3 love with VMWare. Well it works fine no errors, but when i connect and the match starts, walking goes fine, but when more FPS needed, it goes terrible laggy. It's not the HW that makes it slow, the cpu is Dual Xeon 3,1ghz and 2gb ram. The cpu is only used 30-40% and ram isnt even close to full.
So my question is, why does the UT3 server turn out so laggy (but not laggy as i normally experience with online gaming) on a VMWare setup? Is there any known info about this, should i install something? And oow yea, the server is connected to a 1Gbit fiber connection, so its definatly not the link-speed either.
This is all errors i get in startup log:
Code:
Init: WinSock: Socket queue 131072 / 131072 Log: NetMode is now 1 Log: Primary PhysX scene will be in software. Log: Creating Primary PhysX Scene. Log: No Cached Brush Physics Data Found Or Out Of Date (Model_54) (Owner: Blocki ngVolume_324) - Cooking Now. Log: No Cached Brush Physics Data Found Or Out Of Date (Model_56) (Owner: Blocki ngVolume_326) - Cooking Now. Log: No Cached Brush Physics Data Found Or Out Of Date (Model_56) (Owner: Blocki ngVolume_794) - Cooking Now. Log: Novodex Terrain Creation (Terrain_1): 1.966234 ms Log: Novodex Terrain Creation (Terrain_2): 2.912138 ms
Comment