GP79 conversion with permission

@Arnao: I remember this happen in a very early version too. Is it possible that maybe something went wrong during the initial conversion with the Tyrell's ?
Or would it possible to convert only one Tyrell again to see if it happen again with a fresh conversion ?
I do not know enough about the steps and how much work it is but if in case of: It does not happen again after a new conversion this would be a work around solution ?
 
Quick kind of OT question guys, if you don`t mind.

I upgraded to the 327.23 drivers from the 320.49 drivers and I think the AA seems to be worse with the 327.23`s than it was with the 320.49`s, especially on white lines going round the tracks... any of you notice this at all?
 
tjc said:
Quick kind of OT question guys, if you don`t mind.

I upgraded to the 327.23 drivers from the 320.49 drivers and I think the AA seems to be worse with the 327.23`s than it was with the 320.49`s, especially on white lines going round the tracks... any of you notice this at all?
Click to expand...

Yes I've noticed this. Originally thought it was the new tracks I was using but it's on Silverstone and mores where I dad really very good white lines before
 
Hm :confused: can't remember how it was before. But what I can say is I had big problems with the 331.40 beta. I installed this version because the bf4 open beta requires this driver version.
In rF2 with the same settings (I always clear the driver settings if I install a new gfx driver and load my preferred settings with the nvidia inspector) I had a lot of micro stuttering.
During the upgrade of my system to a 2 way sli system I've learned that (sometimes) it is important to remove all driver fragments.
If you have time following steps give you maybe a different result:
- Take a screenshot of the white lines. And if you want measure the fps on a certain point.
- Backup/export your rF2 profile settings with nvi
- Take a screenshot of your custom rF2 nvidia control panel settings (if you had some:) )
- Clear or reset all rF2 custom settings in nvidia control panel then do a fresh nvidia install (not express)
- Select the rF2 Profile in nvi and click on "restore current profile to nvidia defaults"
- Start rF2 and look how your AA works and make a screenshot.
- Export in nvi the current rF2 Profile (don't overwrite the other exported Profile)
- Import with nvi the "old" rF2 profile and apply it (I think two times) .
- Start rF2 and make screenshot.
- repeat this procedure with the 320.49 driver version
- compare your screenshots

Additional you can measure the given fps and compare them between the different driver versions.
One thing I noticed in nvidia inspector. There is a section called "Undefined" this section contains also some driver flags
not sure but since I've set the values for them to "0" (expect the values which contain the "$" character my fps are (again) stable around 60 fps.
I believe that this was caused due the nvidia beta driver experiment :p

At the moment all works satisfying for me.
 
one thing that isnt helping is that last week randomly and for no reason the settings screen of NVinspector lost all of its 'names', and now all the settings are in some code language. i can change them still, but i cant understand what they are.

blue link at the bottom says click here to resolve, but just get an error. anyone else had this?

i have updated NVI to latest and still not fixed

will try a screen grab but dont want to go too far OT
 
Hi,

So I think that we need a new beta tester with an ATI card...
Me and Zonder have an ATI card and we no more have black screen till internal V0.43_REV4 update...
So if someone with an ATI card want to test closed V0.43 please PM me...
For Nvidia user,Alpha, Hedlum or Samuel... I want to do a test that I already did only for me... I will remove Zonder cockpit for tyrrell in the gen files...and I will make a special update to test...

Thanks all for your help
 
@rob1178 It looks like the CustomSettingNames_en-EN.xml file is lost or write protected.
Take a look in the home directory of nvidiaInspector.exe.
In the same directory should be the CustomSettingNames_en-EN.xml .
nvi only need nvidiaInspector.exe and CustomSettingNames_en-EN.xml to run.
Put it for example in your Documents directory to avoid problems with ntfs permissions or UAC.

hope this helps.
 
I'm running nVidia with 331.40 drivers.

So there hasn't been black screens reported at all with ATI users?

I was beginning to think maybe it was the 300 build, but maybe not.
 
alpha-bravo said:
@rob1178 It looks like the CustomSettingNames_en-EN.xml file is lost or write protected.
Take a look in the home directory of nvidiaInspector.exe.
In the same directory should be the CustomSettingNames_en-EN.xml .
nvi only need nvidiaInspector.exe and CustomSettingNames_en-EN.xml to run.
Put it for example in your Documents directory to avoid problems with ntfs permissions or UAC.

hope this helps.
Click to expand...

Thank you, I will test this and report back
 
Me and Arnao are runing AMD, black screens been happening to us before, but we can't get them in latest iteration of our test version 0.43rev5
 
Thanks for the replies on my drivers question guys...

I`ll maybe roll back the drivers just to test things out.

If I find any major improvements etc I`ll let you all know.

Sorry for the OT btw. :)
 
alpha-bravo said:
@rob1178 It looks like the CustomSettingNames_en-EN.xml file is lost or write protected.
Take a look in the home directory of nvidiaInspector.exe.
In the same directory should be the CustomSettingNames_en-EN.xml .
nvi only need nvidiaInspector.exe and CustomSettingNames_en-EN.xml to run.
Put it for example in your Documents directory to avoid problems with ntfs permissions or UAC.

hope this helps.
Click to expand...

i had 'tidied' my desktop and had moved the custmsettingsname-en.xml file into another folder. i replaced it to where the app is, and its fine now.

thank you
 
Great work here, new cockpits put this mod now in a different level.
Are you planning to update all? That would be sweet.
 
ATI user here, HD4850, getting black screen on and off in Tyrell cockpit (haven't tried others) whilst driving the 0.42 unrestricted.
 
You must log in or register to reply here.
Back
Top