- ATI RADEON HD 3400 SERIES 3006 MB BIOS 32 BIT
- ATI RADEON HD 3400 SERIES 3006 MB BIOS MANUAL
- ATI RADEON HD 3400 SERIES 3006 MB BIOS WINDOWS
While I'm sure performance has been improved, it is still not feasible for low-end machines to participate in fleet battles of this size. N/A, never done a fleet battle like this beforeĭescribe your experience, make comments, suggestions, etc. On a scale of 1-10, how would you compare FPS and performance between this test and TQ? RAM 1.5GB DDR2 (EVE used an average of 530 MB during the test)Īverage FPS during the test: 4-5 fps, lowest 0.3 fpsĭid you notice any desyncs during the test? Yes, I got e warped when the last jump occurred due to grid problems. GPU NVidia GeForce 7300 (Settings bottomed out)
This should be fixed, a pilot that jumped should have all his 30 seconds of decloak delay starting from the moment he loaded grid.ĬPU AMD Sempron 3000+ (1.8 GHz Single-core) HOWEVER, when I loaded grid, the ship had already decloaked and was entering e-warp. When jumping from X-B into FD- we got traffic control, but when we actually jumped, grid loaded VERY fast. On a scale of 1-10, how would you compare FPS and performance between this test and TQ? (1=way worse, 5=same, 10=OMG this is awesome) - Client FPS was worse, many more hangs and hickups, I'd give it a 3. While seeting up a new fleet: 2fps + lots of hickups. While just sitting at gate with 200 people, zoomed out: 35fps. About module lag, well, 400 pl spamming F1-F8 and such isn't helping but I think this deserves to get a look into it.ĭid you have brackets turned on? - both on and off (different tabs)Īverage FPS during the test - Anywhere between 2-60fps. Brackets needs improvement imo, as well as overview. During fleet/jumps test, no module lag at all, but a lot in the fight. Graphical lag when a new member comes in fleet ( However reducing the overview window gets this better ). Only after the fight, when I jumpd back to FD. Jumps/fleets tests = 30-60, Fight test = 1-10
ATI RADEON HD 3400 SERIES 3006 MB BIOS MANUAL
Guns and modules only shot for 1 cycle before having to wait 1 min on manual turn off to turn them back on againĪt start, yes, after a while no longer = +10 fps roughly On a scale of 1-10, how would you compare FPS and performance between this test and TQ? 7 * Describe your experience, make comments, suggestions, etc.ĭid you have Audio enabled? Enabled, fleet audio crashedĭid you have brackets turned on? Brackets Offĭid you notice any desyncs during the test? During fleet change * On a scale of 1-10, how would you compare FPS and performance between this test and TQ? (1=way worse, 5=same, 10=OMG this is awesome) Modules responsive within 20 seconds or so Minor module lag, client crashed to desktop once. * Did you notice any desyncs during the test? Not unplayable but slow- 20-40 fps, dropped to less then 5 occasionallyĢ0-40, when the fight started it averaged around 20 Laggy when ppl where joining/exiting fleet, when jumping and fighting.
ATI RADEON HD 3400 SERIES 3006 MB BIOS 32 BIT
* OS version (XP, Vista 64bit, OS X, Linux - Fedora, etc.) win vista ultimate 32 bit
Mah Sig! MAAAH SIIIG!! WAAAAAAAAH WHERE MY SIIIGGGG?!!?!! On the last jump session change I was floating in void (nothing in space/overview/my ship missing) then started emergency warping but instead of warping to gate, I was 1M km away from gate. Where to upload my logserver workspace ?ġx nVidia GeForce 8800 GTS 512MB in 3360x1050 horizontal spanĪvg fps 60 (zoomed out all the way) to 12 (zoomed in all the way)ĭesync suspicius: Timer said needed to wait 2+ minutes before jumping with fleet but was able to jump in after about 30 secondsĬould not join audio after switching fleet Scale: 7, it was better then the 200 man fight we had on tranquil today, but I think that's because of my settings being different.ĭescribe: Fun, first real large fleet fight.