open All Channels
seplocked Macintosh
blankseplocked Incursion 1.6 Bugs
 
This thread is older than 90 days and has been locked due to inactivity.


 
Pages: 1 2 3 [4]

Author Topic

stacy gemini
Posted - 2011.06.11 11:23:00 - [91]
 

Originally by: RenderMonkey
Superb find Gem!
Restoring those old values you indicated on the config file fixed all my graphics issues - fps back to normal now with all windows open :)
EVE is playable again.

CCP take note of Stacy Gemini's post - it's a fixer.


Glad it was a fix for you as well.
Now this is verified on 2 machines.

Delilah Wild
Posted - 2011.06.11 20:30:00 - [92]
 

Hello All,

I still can't select bookmarks or celestials in the map. Nor will a group of them in close proximity 'list out' as they did in the past. I've read this was not a platform specific bug, and that it was fixed. The former may be true, the latter is definitely not.

Cheers

Computer: 2009 Macbook Pro; OS X 10.6.2; 2.4 GHz Intel Core 2 Duo; 4 GB memory, Nvidia GeForce 9400M; Nvidia GeForce 9600M GT.

Manssell
Posted - 2011.06.14 02:30:00 - [93]
 

Originally by: stacy gemini
Update
been suffering from the low fps bug when i remembered that at one time i edited my config file to get some boost in performance.
i got that hack from around here somewhere.
so i tried restoring from the back up that i made of the config before i made the changes.

the config file is in user\library\preference\eve preference

i edited some entries in it pertaining to the graphics

this is what mine currently looks like now (old config)

"[d3dgl]
"AnisotropicTextureFiltering" = "Y"
"VertexShaders" = "Y"
"PixelShaders" = "Y"
"PixelShadersLevel" = "3.0"
"ClipSpaceFix" = "Y"
"FragmentOffset" = "Auto"
"FixedProgram" = "Y"
"RectangleTextures" = "Auto"
"DynamicVBO" = "N"
"IndexVBO" = "N"

"FBO" = "Y"
"FBOBackBuffer" = "N"
"GLSL" = "M"
"VertexShadersLevel" = "3.0"
"FloatTextures" = "Y"
"OcclusionQueries" = "Y"
"ForceMOVACompliance"="N"
"ATIINTZ" = "Y"


note the N values in :
1. dynamicVBO
2. IndexVBO
3. FBO Backbuffer

So i restored from my config backup having the above values
booted into the game
got 30-40 fps with all my windows in game up, including fps window(ctrl+F) im betting its higher with fps windows closed
windows still give a hit on performance but its perfectly playable now

maybe you guys can verify this fix.
make a backup of your config and then change those entries i enumerated to N if you have Y, and maybe vice versa



Yep!!!!!!! Worked for me! THANK YOU!


CCP Take notice!

Kael'Jierr
Posted - 2011.06.15 03:04:00 - [94]
 

\0/ Gem's fix worked for me!

maconie
Minmatar
Ordos Humanitas
Posted - 2011.06.16 05:29:00 - [95]
 

Excellent fix from Stacey Gemini, game runs a lot smoother, I am still getting lock outs though but it starts to happen after about 10 mins. I think this is now down to heat, the GPU diode was at 75C last night

Finally we are getting somewhere though.

Thanks again

TG Skeletor
Posted - 2011.06.20 22:10:00 - [96]
 

Originally by: stacy gemini
Update

this is what mine currently looks like now (old config)

"[d3dgl]
"AnisotropicTextureFiltering" = "Y"
"VertexShaders" = "Y"
"PixelShaders" = "Y"
"PixelShadersLevel" = "3.0"
"ClipSpaceFix" = "Y"
"FragmentOffset" = "Auto"
"FixedProgram" = "Y"
"RectangleTextures" = "Auto"
"DynamicVBO" = "N"
"IndexVBO" = "N"

"FBO" = "Y"
"FBOBackBuffer" = "N"
"GLSL" = "M"
"VertexShadersLevel" = "3.0"
"FloatTextures" = "Y"
"OcclusionQueries" = "Y"
"ForceMOVACompliance"="N"
"ATIINTZ" = "Y"

note the N values in :
1. dynamicVBO
2. IndexVBO
3. FBO Backbuffer

So i restored from my config backup having the above values
booted into the game got 30-40 fps with all my windows in game up, including fps window(ctrl+F) im betting its higher with fps windows closed windows still give a hit on performance but its perfectly playable now


Hi all,

TransGaming Skeletor here - while we are always happy to hear when people are able to work around a problem, the fact that the suggestions posted above are improving performance for some people is somewhat surprising to us.

First off, we should note that the config file should definitely not be touched unless you're sure that you know what you're doing. Changes here can definitely cause bad things to happen, ranging from small graphics anomalies to your Mac freezing and requiring a reboot - the latter can happen due to bugs in the 3D graphics drivers that a particular config setting may be designed to avoid.

The three config settings mentioned earlier (IndexVBO, DynamicVBO, and FBOBackBuffer) control different aspects of how Cider's OpenGL code works. The first two control how geometry data for the world is loaded into video memory, and the last one controls the path through which the final image is rendered onto the screen. In the case of DynamicVBO and IndexVBO, disabling these will cause less geometry data to be stored in VRAM on your graphics card, which should make things run more slowly, not faster. In the case of FBOBackbuffer, disabling this could provide a very small speed improvement (one screen-sized copy operation per frame is avoided), but at the cost of losing anti-aliasing and other graphics effects.

Our suspicion we had in reading the complaints above is that perhaps the issues you are seeing are related to the amount of VRAM available in your graphics cards. Some of the people who have posted about performance in the thread appear to be running older Macs with ATI X1600 or NVidia 7300 GPUs, many of which shipped with 128 MB of VRAM. The one thing that the three options above have in common is that they each use up some VRAM. Turning them off would increase the amount of VRAM available for other things such as texture data in the UI windows. In situations where VRAM is limited, the OS has to do quite a bit of work to swap textures in and out, which can result in a significant framerate drops if VRAM is full. This swapping effect can happen even on a card with 256 MB of VRAM if other in-game options such as texture detail are set to high. If you have a card with limited amounts of VRAM you may want to try reducing texture detail, LODs, etc rather than making the changes above, as that should do a better job at keeping VRAM usage in check than flipping the config options.

If you're ambitious and want to verify whether this is your problem, and you have the Apple Developer Tools installed on your system, you can open up Apple's OpenGL Driver Monitor application, press Cmd-1 to open the main monitoring window for your primary video card, pull out the 'parameters' sidebar, and double click on 'Current Free Video Memory' to track the amount of VRAM being used by the game in real time. The other important number here (in fact perhaps more important) is the "texture page on data" parameter, which will show you if large amounts of texture data are being swapped on to the card at runtime.

- TG Skeletor

Gunther Gabel
Caldari
Posted - 2011.06.21 04:42:00 - [97]
 

TG Skeletor,
Not to knock you in the dirt....but bringing us this info a few hours prior to a gigantic patch prolly isn't going to do us any good for this problem.

That being said, I am one of those with a X1600 and 256mb vram. I was told that turning those 3 off basically killed AA. Either way, it definitely works. I went from 4fps to 38fps. I can't check the game currently and by the time I get to that computer, servers will be down for incarna update.

I have been on SiSi alot and even with a Mac Pro with a 5770 video card, I only get about 24fps in CQ and it is very laggy and window are very slow to respond. If we can't turn that **** off, maybe you can come up with some tips to help us tone that crap down so we can actually play and get to stuff after incarna :)

Gunther

Gunther Gabel
Caldari
Posted - 2011.06.21 21:42:00 - [98]
 

I guess it REALLY doesn't matter now, we are all locked out of the game....

A heads up would have been rather rather than a cool slap when we started the client up



Pages: 1 2 3 [4]

This thread is older than 90 days and has been locked due to inactivity.


 


The new forums are live

Please adjust your bookmarks to https://forums.eveonline.com

These forums are archived and read-only