SimForums.com Homepage
Forum Home Forum Home > General Discussion Forums > Hardware, Software, and Computer Technology
  New Posts New Posts RSS Feed - Switch to P3D
  FAQ FAQ  Forum Search   Register Register  Login Login

Topic ClosedSwitch to P3D

 Post Reply Post Reply Page  123 4>
Author
Message
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Topic: Switch to P3D
    Posted: November-04-2015 at 8:16am
Anyone here moved from FSX to P3D ? thinking of going ahead with it. seems alot better.
W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
vic_baron View Drop Down
Senior Member
Senior Member


Joined: October-03-2007
Points: 1057
Direct Link To This Post Posted: November-04-2015 at 12:14pm
I did and haven't looked back. It is under continual development which is a big plus. Bottom line - they have a 60 day refund policy - give it a try.
 
Only suggestion - forget all the tweaks you use for FSX - either they are not needed or are now in the code. Start with a fresh cfg file and just adjust your settings according to your hardware.
 
Just as a FYI, when I first tried it, I hated it - it was a stutter blurry mess. Sent it back. After hearing others success and approval, I tried again only took it step by step. Followed Nick's Bible in setting up the hardware and went on.  Sure glad I did.
 
Vic
3770K 4.7G ASUS Z77 1600 7-8-7 GTX1080ti 850W 2-1TB WD HDD,1tb VRap, HAF942 - H100 water W10 Pro

7700K 5.0g Asus X270F 3600 15-15-15 RTX3090 1000W PSU 2-256G OCZ SSD, 1TB,HAFX-H100 Water W10 Pro
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-05-2015 at 5:55am
Thats me install it all now :) hopefully pain free lol

What NI settings are you using and game settings?
W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
crossave View Drop Down
Intermediate Group
Intermediate Group


Joined: October-24-2011
Points: 66
Direct Link To This Post Posted: November-05-2015 at 9:00am
Do you have to choose between the two?  Can you have both installed on same computer to compare?
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-05-2015 at 10:48am
Will Nick set a guide for P3D and NI settings ? :)
W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
vic_baron View Drop Down
Senior Member
Senior Member


Joined: October-03-2007
Points: 1057
Direct Link To This Post Posted: November-05-2015 at 12:27pm
Yes you can have both. Nick's guide works fine with the exception of a few tweaks which are not needed ( HIGHMEMFIX, BufferPools) - just follow his guide but make no tweaks initially. I'm sure if there are any specific P3D tweaks, Nick will let us know as they occur.
 
NI does not function fully with P3D. Depending on the system, some people have had the shimmers and very poor AA. They have had success using 4SGSS in NI.
 
Basically use NI to set the AA Mode to ENHANCE the application - and then set 4SGSS.
 
You will probably get a solid frame rate hit in dense clouds but it's your call.
 
Try it bare bones with the default and go from there.
 
Finally, IMHO, if you want the BEST visuals - use GEXP3D and UTX and don't look back.
 
Vic
3770K 4.7G ASUS Z77 1600 7-8-7 GTX1080ti 850W 2-1TB WD HDD,1tb VRap, HAF942 - H100 water W10 Pro

7700K 5.0g Asus X270F 3600 15-15-15 RTX3090 1000W PSU 2-256G OCZ SSD, 1TB,HAFX-H100 Water W10 Pro
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-06-2015 at 9:14am
I'm using this guide and some of the tweaks

http://www.codelegend.com/forums/viewtopic.php?f=2&t=601

I've decided not to even use NI at the moment
W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
NickN View Drop Down
Certified Professional
Certified Professional


Joined: November-21-2007
Points: 21176
Direct Link To This Post Posted: November-06-2015 at 10:14am
NVI has exceptionally limited use in P3D 2x and above
 
Right now the only thing it can be used for is Sparce Grid SS and all that does is tone down texture swimming on some objects like radio towers, bridges, fences and on some large city buildings in the distance. In order to use it, it requires setting up the NV driver system first for the P3D application, then making changes to NVI that are completely different than the way it was used in the past to enhance or override the application settings.
 
Because P3D is constantly changing and the way Nvidia drivers change, it require the game profile in the Nvidia driver control panel be edited in order to assure NVI will take control of SSGS. NVI cant be used for standard AA control, only SSGS and some SLi settings.
 
In game we use ANSO x16 +  MSAA 8 samples   (MSAA 4 samples if you use SGSS x2-x4 in NVI)  Be aware any use of NVI will kill performance, especially in weather and around large airports.
 
Frame lock and Vsync can be different for different systems. Some find locking at 20-30 works best, others find locking at 60 with/without Vsync or running unlimited works best. The problem with P3D is that there is actually more need for trial and error testing with frame lock over FSX and even different planes/scenery can drive a different frame lock/Vsync setup
 
NVI 1/2 Vsync doesn't work in P3D so any tweaks around that are useless
 
Most past tweaks have little or no effect. The only ones that have value with P3D 2x and above are:
 
[DISPLAY]
TEXTURE_BANDWIDTH_MULT=80 to 160 adjustable   this has far less effect than it did with FSX but still works. The effects are hardly noticeable in P3D but are there
 
[MAIN]
HideInfoText=1   still gets rid of all the screen readout junk unless you want it
FIBER_FRAME_TIME_FRACTION=0.10 to .33   adjustable
 
 
[SIM]
OPTIMIZE_PARTS=1
 
 
Those will have the most impact past scenery and AI settings.
 
None of the other tweaks for FSX are useful except in the case of Hyperthreading being ON in a system
 
Unlike FSX, in P3D if hyperthreading is enabled on a system then a proper Affinity Mask should be used. If HT is not enabled do NOT use affinity mask at all.
 
And be aware, I don't care who is pushing HT 'ON',... Although changes with P3D development have introduced better HT support, HT is not something the sim makes solid consistent use of and never will until the entire core is rewritten for that purpose. You are still far better off taking a good higher CPU speed and leaving HT OFF for cooler temps over HT ON and setting a proper affinity mask. Those who don't clock at all may find turning HT ON and setting a proper affinity mask works better
 
It really comes down to the system itself and the type of processor in use too.
 
Many find leaving all tweaks out other than OPTIMIZE_PARTS=1 is the best way to run
 
 
its all trial and error, just like FSX was. And just like FSX today, tomorrow and this week you may fly smooth and happy, and next week or next month a new plane or scenery introduces a wild card and you start all over again looking for the smoothest way to run.
 
The one thing people still don't seem to get is, there is no such thing as a NORM SETUP/BEST TWEAKS/ALWAYS WORKS IN EVERY SITUATION with Flight Simulator. What works today, may need to be changed tomorrow and more than 2-3-4 sets of config and settings saved for different situations.
 
There is no miracle with P3D.. although there have been good changes and advances,...  its the same song, just a different tune.
 
 
 
 
 
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-06-2015 at 11:42am
Brilliant nick i will take all that all on board and adjust my system for what you have said. I run HT off and will remove the AM=14 tweak that i placed in.

Would you recommend just leave NVI completely out of P3D and adjust within P3D settings? Will you ever make a guide for P3D?
W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-06-2015 at 11:45am
Could you take a pict of your NVI settings and game settings nick and post it just want a rough idea. It all confuses me with all these words.

Thanks
W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
NickN View Drop Down
Certified Professional
Certified Professional


Joined: November-21-2007
Points: 21176
Direct Link To This Post Posted: November-06-2015 at 12:42pm
I don't use NVI in P3D
 
I know how it works and have played around with it, but find its not worth the perf loss for a little distance texture swimming control
 
 
 
 
 
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-06-2015 at 1:32pm
Cool i'll go with the tweaks you mentioned.

What about AM=14 if my HT is off ?
W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
NickN View Drop Down
Certified Professional
Certified Professional


Joined: November-21-2007
Points: 21176
Direct Link To This Post Posted: November-06-2015 at 1:50pm
I posted NOT to use any AM if you don't run HT
 
Eliminate any Affinity Mask unless you use HT
 
If you do use HT you need a proper calculation for the value, 14 WONT WORK
 
AM in P3D is not like FSX at all
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-06-2015 at 3:19pm
Ok nick cheers
W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-06-2015 at 6:42pm
What about these tweaks 

http://www.prepar3d.com/SDKv2/LearningCenter/getting_started/performance/tuning_guide.html
W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
NickN View Drop Down
Certified Professional
Certified Professional


Joined: November-21-2007
Points: 21176
Direct Link To This Post Posted: November-06-2015 at 6:57pm
what about them
 
did I mention them? If I did, they have value, if not they don't
 
Trust me..  with P3D v3 the best thought process you can have is
 
a. STOP THINKING TWEAK, TWEAK, TWEAK
 
b. STOP THINKING FSX
 
 
 
The only other tweak I would offer is one for panning speed...
 
 
Open the Cameras.cfg in the P3D config file folder in notepad
 
Edit the following under the headings:

[CameraDefinition.002]
Title = Virtual Cockpit
PitchPanRate=50  <---change this
HeadingPanRate=90 <---change this
ClipMode=Normal  <---add this
 
 
[CameraDefinition.003]
Title = Spot
PitchPanRate=50  <---change this
HeadingPanRate=90 <---change this
ClipMode=spot <---add this
 
[CameraDefinition.004]
Title = Locked Spot
PitchPanRate=50  <---change this
HeadingPanRate=90 <---change this

save and close..   leave the original where it is, and then take a COPY of that file and drop it into the main P3D install directory
 
 I will post a startup settings list for you to get the ball rolling. I cant now but will do it later tonight
 
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-06-2015 at 7:34pm
This is mine will i go through them all?


[CameraDefinition.201]
Title = EZCA VC cam
Guid = {67CFDFFC-E78E-4445-B317-36A6888AECA8}
Description = This is the description of the virtual cockpit view.
Origin = Virtual Cockpit
MomentumEffect =No
SnapPbhAdjust = Swivel
SnapPbhReturn = False
PanPbhAdjust = Swivel
PanPbhReturn = False
Track = None
ShowAxis = YES
AllowZoom = TRUE
InitialZoom = 0.30
SmoothZoomTime = 3.0
ZoomPanScalar = 1.0
ShowWeather = Yes
XyzAdjust = TRUE
ShowLensFlare=FALSE
Category = Cockpit
PitchPanRate=30
HeadingPanRate=75
PanAcceleratorTime=0
HotKeySelect=0
cyclehidden=Yes
clipmode=minimum

[CameraDefinition.202]
Title= EZCA World cam
Guid={910DD22E-0B8F-434B-85F4-837FAC80F287}
Description=EZdok universal world camera
Origin=Fixed
SnapPbhAdjust=Swivel
SnapPbhReturn=False
PanPbhAdjust=Swivel
PanPbhReturn=False
Track=none
ShowAxis=No
AllowZoom=Yes
InitialZoom=1
SmoothZoomTime=1
ShowWeather=Yes
XyzAdjust=True
Transition=No
ShowLensFlare=TRUE
Category=Custom
ClipMode=Spot
PitchPanRate=30
HeadingPanRate=75
PanAcceleratorTime=0
HotKeySelect=5
cyclehidden=Yes
FixedLongitude=37.910548752051
FixedLatitude=55.4228687612085
FixedAltitude=3000




[CameraDefinition.203]
Title= EZCA Aircraft cam
Guid={9975B7A2-68A4-4F72-9203-788AB1A63B7A}
Description=Universal camera for EZdok cam utility
Origin=Center
SnapPbhAdjust=Swivel
SnapPbhReturn=FALSE
PanPbhAdjust=Swivel
PanPbhReturn=FALSE
Track=None
ShowAxis=FALSE
AllowZoom=TRUE
InitialZoom=0.40
ShowWeather=Yes
InitialXyz=0,0,0
InitialPbh=10, 0, 0
XyzAdjust=TRUE
Category=Aircraft
MomentumEffect=FALSE
ClipMode=Minimum
HotKeySelect=4
cyclehidden=Yes


[CameraDefinition.001]
Title = Cockpit
Guid = {B1386D92-4782-4682-A137-738E25D1BAB5}
Description = This is the description of the cockpit view
Origin = Cockpit
ShowPanel = Yes
SnapPbhAdjust = Ordinal
SnapPbhReturn = True
PanPbhAdjust = Ordinal
PanPbhReturn = True
Track = None
ShowAxis = FrontOnly
AllowZoom = TRUE
InitialZoom = 1.0
SmoothZoomTime = 2.0
ShowWeather = Yes
XyzAdjust = TRUE
ShowLensFlare=FALSE
Category = Cockpit
HotKeySelect=2


[CameraDefinition.003]
Title = Spot
Guid = {BCA3FDD1-FB83-4BBA-8407-4922A7F0D00C}
Description = This is the description of the spot view.
Origin = Center
SnapPbhAdjust = Ordinal
SnapPbhReturn = False
PanPbhAdjust = Swivel
PanPbhReturn = False
Track = FlatChase
ShowAxis = No
AllowZoom = Yes
InitialZoom = 1.0
SmoothZoomTime = 2.0
ShowWeather = Yes
XyzAdjust = FALSE
Transition = Yes
ShowLensFlare=TRUE
Category = Outside
ClipMode = Spot
PitchPanRate=30
HeadingPanRate=75
PanAcceleratorTime=0

[CameraDefinition.004]
Title = Locked Spot
Guid = {BCA3FDD1-FB83-4BBA-8407-4922A7F0D00D}
Description = This is the description of the spot view.
Origin = Center
SnapPbhAdjust = Swivel
SnapPbhReturn = False
PanPbhAdjust = Swivel
PanPbhReturn = False
Track = FlatChaseLocked
ShowAxis = No
AllowZoom = Yes
InitialZoom = 1.0
SmoothZoomTime = 2.0
ShowWeather = Yes
XyzAdjust = FALSE
Transition = Yes
ShowLensFlare=TRUE
Category = Outside
ClipMode = Spot
PitchPanRate=30
HeadingPanRate=75
PanAcceleratorTime=0
HotKeySelect=3

[CameraDefinition.005]
Title = FlyBy
Guid = {6B79DD49-9B4A-439D-BF40-ACBF157B0BA0}
Description = This is the description of the fly by view.
Origin = Center
SnapPbhAdjust = Swivel
SnapPbhReturn = False
PanPbhAdjust = Swivel
PanPbhReturn = False
Track = FlyBy
ShowAxis = No
AllowZoom = Yes
InitialZoom = 10.0
SmoothZoomTime = 2.0
ShowWeather = Yes
XyzAdjust = FALSE
Transition = No
ChaseDistance = 500
ChaseHeading = 15
ChaseAltitude = 10
ChaseTime = 20
ShowLensFlare=FALSE
Category = Outside
ClipMode = Tower

[CameraDefinition.006]
Title = Top-Down
Guid = {A2849229-938A-448f-8AC6-01EF2291C171}
Description = This is the description of the map or top down view.
Origin = Center
SnapPbhAdjust = Orthogonal
PanPbhAdjust = Orthogonal
Track = None
ShowAxis = Yes
AllowZoom = Yes
InitialZoom = 256
MinZoom = 0.7
SmoothZoomTime = 2.0
ShowWeather = No
XyzAdjust = FALSE
Transition = No
ShowLensFlare=FALSE
Category = Outside

[CameraDefinition.007]
Title = Nearest Tower
Guid = {60BC0819-BD04-4AF6-8954-8FC8AA3545FF}
Description = This is the description of the tower view.
Origin = Tower
SnapPbhAdjust = Swivel
SnapPbhReturn = False
PanPbhAdjust = Swivel
PanPbhReturn = False
Track = Track
ShowAxis = No
AllowZoom = Yes
InitialZoom = 8.0
SmoothZoomTime = 2.0
ShowWeather = Yes
XyzAdjust = FALSE
Transition = No
ShowLensFlare=FALSE
Category = Tower
ClipMode = Tower
NoSortTitle = True

[CameraDefinition.008]
Title = Facilities Tower
Guid = {AA8C80C0-9EE2-4284-A1C2-B20CD3F5F3D9}
Description = This is the description of the tower view.
Origin = Fixed
InstancedBased = Yes
SnapPbhAdjust = None
PanPbhAdjust = None
Track = Track
ShowAxis = No
AllowZoom = Yes
InitialZoom = 8.0
SmoothZoomTime = 2.0
ShowWeather = Yes
XyzAdjust = FALSE
Transition = No
ShowLensFlare=FALSE
Category = Tower
CycleHideRadius = 7
ClipMode = Tower

[CameraDefinition.009]
Title = Facilities Runway
Guid = {607C4520-CA6F-4135-AE10-8BF28838068F}
Description = This is the description of the runway view.
Origin = Virtual Cockpit
InstancedBased = Yes
SnapPbhAdjust = None
PanPbhAdjust = None
TargetCategory = Fixed
Track = TrackBank
ShowAxis = Yes
AllowZoom = Yes
InitialZoom = 1.0
SmoothZoomTime = 2.0
ShowWeather = Yes
XyzAdjust = FALSE
Transition = No
ShowLensFlare=FALSE
Category = Runway
CycleHideRadius = 7
ClipMode = Tower
CycleHidden=Yes

[CameraDefinition.010]
Title = AI Planes
Guid = {75A8357E-AB58-4294-9416-90C73FAFDD90}
Description = This is the description of the AI aircraft view.
Origin = Center
SnapPbhAdjust = Swivel
SnapPbhReturn = False
PanPbhAdjust = Swivel
PanPbhReturn = False
Track = FlatChaseLocked
InstancedBased = Yes
ShowAxis = No
AllowZoom = Yes
InitialZoom = 1.0
SmoothZoomTime = 2.0
ShowWeather = Yes
XyzAdjust = FALSE
Transition = No
ShowLensFlare=TRUE
Category = AirTraffic
TargetCategory = Container
ClipMode = Spot
PitchPanRate=30
HeadingPanRate=75
PanAcceleratorTime=0
CycleHidden=Yes

[CameraDefinition.011]
Title = Multiplayer Planes
Guid = {2559BCED-9F13-4bc0-88C8-3996B9311681}
Description = This is the description of the Multiplayer other aircraft view.
Origin = Virtual Cockpit
InstancedBased = Yes
SnapPbhAdjust = None
PanPbhAdjust = None
TargetCategory = Container
Track = TrackBank
ShowAxis = Yes
AllowZoom = Yes
InitialZoom = 1.0
SmoothZoomTime = 2.0
ShowWeather = Yes
XyzAdjust = FALSE
Transition = No
ShowLensFlare=FALSE
Category = MultiPlayer
CycleHideRadius = 7
ClipMode = Tower
CycleHidden=Yes

[CameraDefinition.012]
Title = IR (White Hot)
Guid = {57A3758A-D596-4260-8AF0-302A5E4DF5CE}
SensorMode = IRWhiteHot
Description = Basic Infrared Sensor Camera (White Hot)
Origin = Cockpit
ShowPanel = No
SnapPbhAdjust = Ordinal
SnapPbhReturn = True
PanPbhAdjust = Ordinal
PanPbhReturn = True
Track = None
ShowAxis = FrontOnly
AllowZoom = TRUE
InitialZoom = 1.0
SmoothZoomTime = 2.0
ShowWeather = Yes
XyzAdjust = TRUE
ShowLensFlare=FALSE
Category = Sensor
CycleHidden=Yes

[CameraDefinition.013]
Title = IR (Black Hot)
Guid = {DD3A45A5-C8BE-417A-B69E-32F402D56F36}
SensorMode = IRBlackHot
Description = Basic Infrared Sensor Camera (Black Hot)
Origin = Cockpit
ShowPanel = No
SnapPbhAdjust = Ordinal
SnapPbhReturn = True
PanPbhAdjust = Ordinal
PanPbhReturn = True
Track = None
ShowAxis = FrontOnly
AllowZoom = TRUE
InitialZoom = 1.0
SmoothZoomTime = 2.0
ShowWeather = Yes
XyzAdjust = TRUE
ShowLensFlare=FALSE
Category = Sensor
CycleHidden=Yes

[CameraDefinition.014]
Title = NVG (White Hot)
Guid = {61C3B6FB-FF9E-4B9C-978E-AA7C7F70F5A9}
Description = Green Colorization based NVG Sensor Camera (White Hot)
PostProcess00 = NVGBloomPostProcess
Origin = Cockpit
ShowPanel = No
SnapPbhAdjust = Ordinal
SnapPbhReturn = True
PanPbhAdjust = Ordinal
PanPbhReturn = True
Track = None
ShowAxis = FrontOnly
AllowZoom = TRUE
InitialZoom = 1.0
SmoothZoomTime = 2.0
ShowWeather = Yes
XyzAdjust = TRUE
ShowLensFlare=FALSE
Category = Sensor
CycleHidden=Yes
LightAmplification=1.5
AmbientBoost=0.15

[CameraDefinition.015]
Title = NVG (Black Hot)
Guid = {28212611-2528-4BD4-B944-565C30A39985}
Description = Green Colorization based NVG Sensor Camera (Black Hot)
PostProcess00 = NVGBloomPostProcess
PostProcess01 =GreenScaleInverter
Origin = Cockpit
ShowPanel = No
SnapPbhAdjust = Ordinal
SnapPbhReturn = True
PanPbhAdjust = Ordinal
PanPbhReturn = True
Track = None
ShowAxis = FrontOnly
AllowZoom = TRUE
InitialZoom = 1.0
SmoothZoomTime = 2.0
ShowWeather = Yes
XyzAdjust = TRUE
ShowLensFlare=FALSE
Category = Sensor
CycleHidden=Yes
LightAmplification=1.5
AmbientBoost=0.15

[CameraDefinition.016]
Title = Weapons
Guid = {218F9779-FDCB-4607-9CCD-D662F8B1EB57}
Description = This is the description of the weapon view.
Origin = Center
SnapPbhAdjust = Swivel
SnapPbhReturn = False
PanPbhAdjust = Swivel
PanPbhReturn = False
Track = FlatChaseLocked
InstancedBased = Yes
ShowAxis = No
AllowZoom = Yes
InitialZoom = 1.0
SmoothZoomTime = 2.0
ShowWeather = Yes
XyzAdjust = FALSE
Transition = No
ShowLensFlare=TRUE
Category = Weapon
TargetCategory = Container
ClipMode = Spot
PitchPanRate=30
HeadingPanRate=75
PanAcceleratorTime=0
CycleHidden=Yes

[CameraDefinition.017]
Title = Static
Guid = {6BF83B82-57E7-46FA-BD6A-946DE0512AE6}
Description = This camera will only show TV like static/snow.
Origin = Cockpit
Track = None
PanelOnly = False
InstancedBased = Yes
AllowZoom = No
XyzAdjust = FALSE
Transition = Yes
ShowLensFlare = FALSE
Category = Custom
ClipMode = Minimum
CycleHidden = Yes
MenuHidden = Yes
PostProcess00 = SignalNoise

[CameraDefinition.018]
Title = RadarCamera
Guid = {037AB312-F502-4900-A853-581C9544F971}
Description = Calculate the geometry data from camera point of view.
SensorMode = GDATA
Origin = Center No Orient
Track = none
ShowPanel = No
SnapPbhAdjust = Ordinal
SnapPbhReturn = True
PanPbhAdjust = Ordinal
PanPbhReturn = True
ShowAxis = FrontOnly
AllowZoom = TRUE
InitialZoom = 1.0
SmoothZoomTime = 2.0
ShowWeather = Yes
XyzAdjust = TRUE
ShowLensFlare=FALSE
Category = Sensor
CycleHidden=Yes
InitialPbh=0, 0, 0
TextureSizeX = 31.0;
TextureSizeY = 256.0;
HideUserAircraft=1
HideSky = 1
HideParticles = 1
HideShadows = 1
HideReflection = 1
ShowLabels=FALSE
UseGlobalTerrainView = TRUE

[CameraDefinition.019]
Title = Oculus Cockpit
Guid = {3E7A2D8D-563C-4D36-9F95-B0F637F53677}
Description = Cockpit view using the Oculus.
Origin = Cockpit
ShowPanel = No
SnapPbhAdjust = Ordinal
SnapPbhReturn = True
PanPbhAdjust = Ordinal
PanPbhReturn = True
Track = None
ShowAxis = FrontOnly
AllowZoom = TRUE
InitialZoom = 1.0
SmoothZoomTime = 2.0
ShowWeather = Yes
XyzAdjust = TRUE
ShowLensFlare=FALSE
Category = HMD
HmdType=Oculus

[CameraDefinition.020]
Title = Oculus Virtual Cockpit
Guid = {C69C6771-EB1F-4346-ADD7-0F8910277CE3}
Description = Virtual Cockpit view using the Oculus.
Origin = Virtual Cockpit
MomentumEffect = Yes
SnapPbhAdjust = Swivel
SnapPbhReturn = False
PanPbhAdjust = Swivel
PanPbhReturn = False
Track = None
ShowAxis = YES
AllowZoom = TRUE
InitialZoom = 0.7
SmoothZoomTime = 2.0
ZoomPanScalar = 1.0
ShowWeather = Yes
XyzAdjust = TRUE
ShowLensFlare=FALSE
Category = HMD
PitchPanRate=30
HeadingPanRate=75
PanAcceleratorTime=0
HmdType=Oculus

W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
NickN View Drop Down
Certified Professional
Certified Professional


Joined: November-21-2007
Points: 21176
Direct Link To This Post Posted: November-06-2015 at 7:48pm
apparently you have some kind of camera software installed that writes to that file and overrides it, therefore forget what I posted and leave it alone
 
 
The pan speed tweak is designed for the default camera config and only header numbers 002, 003 and 004 are edited as I clearly show above.
 
 
 
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-06-2015 at 8:05pm
Yeh that will be ezdok cameras.


W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-06-2015 at 8:06pm
thanks for doing the startup settings
W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-06-2015 at 9:42pm
also have you got a link to setup UTX Europe V2.1?
W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
NickN View Drop Down
Certified Professional
Certified Professional


Joined: November-21-2007
Points: 21176
Direct Link To This Post Posted: November-06-2015 at 10:49pm
Back to Top
jafferhussain11 View Drop Down
Intermediate Group
Intermediate Group


Joined: June-24-2014
Location: kuwait/india
Points: 52
Direct Link To This Post Posted: November-06-2015 at 11:30pm
hey people,


Just my 2 cents worth here; 

do we or can we not find a solution in X-plane ? Fine the X-plane world looks Toyish(Because of lack of plausible ground textures) and there may be a dirth of quality planes but for all the Crying we see on various forums regarding the necessity of a good 64 bit platform to work with ;well its already there its called X-plane.

What i am trying to get at here is more of a shout out to developers. Like PMDG has started exploring that world with their first upcoming product (DC-6) , could we not see some more quality Developers taking a shot at it ? 

Like GEX AND UTX developers could try developing ground textures and land class stuff (just a good landclass product would change the face of XPLANE), Flight1 could easily tap into this 64-bit sketch board waiting to be Drawn on.It could also encourage some of its developers to focus on X-plane maybe ??

Look how bad our Tweak to Play ratio is (getting much better now by the way), which ever forum we goto we find only Hardware questions and topics regarding this tweak and that tweak,but all this because of old but enjoyable code : FSX/P3D. I personally enjoy P3D and FSX and i have had my Tweak marathons too but when i tested out X-plane 10.40 i see soo much Potential ; for Quailty developers to take a shot at and i see it has the potential to be a future sim platform but only and only if quality developers move to it.

it would be nice if some 'quality developers' (ahem ahem NICKN and flight1 guys) started seriously developing for X-plane .Business follows the business man; if developers move to X-plane the business should follow and in this flight sim business ;the fans follow along.

wishing for a bright future for the flight sim programs and community.

Sorry if i posted in the wrong thread :)

kind regards,

Jaff..     
jaff
Back to Top
NickN View Drop Down
Certified Professional
Certified Professional


Joined: November-21-2007
Points: 21176
Direct Link To This Post Posted: November-06-2015 at 11:45pm
I hear you.. the market is just not there with Xplane and their landclass system would be a rework from the ground up meaning it would not be FSX pricing out of the gate, that's for sure
 
That sticker shock probably wouldn't go over well for you
 
Planes are different since they have common denominators with modeling and 3D, terrain landclass code and texture assignment is all new in compare. So yes I can see PMDG and plane makers looking but scenery means starting over from scratch
 
 
We did investigate XP years ago and what we got was not promising in both development time and cost to produce vs return on investment
 
If the market was large enough to absorb the development time, that might be different.. unfortunately is isn't
 
 
Back to Top
jafferhussain11 View Drop Down
Intermediate Group
Intermediate Group


Joined: June-24-2014
Location: kuwait/india
Points: 52
Direct Link To This Post Posted: November-07-2015 at 12:02am
@NICK :

 Fair enough :) 

 the idea that while all games/programs out there are constantly adopting and  progressing ,seeing our fine old ESP/FSX based software lag terribly behind is saddening. 

We see P3D now constantly developing and also theres Dovetail games trying to come up with a new sim albeit based on Microsoft technology but all these guys are still just refining old code. Nobody dares go Ground up ! ACES truly were kings i suppose....

Any way we got to enjoy what we have and hope for the best future :)

kind regards.




jaff
Back to Top
NickN View Drop Down
Certified Professional
Certified Professional


Joined: November-21-2007
Points: 21176
Direct Link To This Post Posted: November-07-2015 at 12:15am
P3D is not that developed in terms of hard core changes and true modern game render, it just has the ability to look prettier
 
its still ESP core and until backwards compatibility is scrapped and rewritten it will continue to be ESP core. Every checkbox and slider they add means the perf drops.
 
Granted P3D can be made to look pretty awesome in compare and they have managed to move some of the load off the CPU but don't believe the people who tell you they enabled all that eye candy 100% and are running the same payware airports and payware aircraft better in P3D over FSXSE..   its bull  Big smile
 
 
 
Back to Top
NickN View Drop Down
Certified Professional
Certified Professional


Joined: November-21-2007
Points: 21176
Direct Link To This Post Posted: November-07-2015 at 12:35am
Unfortunately I cant get into posting a setup tonight because I have to fly out for business in Toronto tomorrow and wont be back till late Monday.
 
 
 
First of all you need to stop reading into my posts like you did with the cameras.cfg and just follow the list, don't try to extrapolate or assume.
 
 
The initial setup is very simple.
 
Be advised, NONE OF THIS involves EZDOK, weather engines, airport addons, or any other 3rd party addon like that. To be quite frank we DONT set up any sim and tune it with addons like that, we get our flights SMOOTH FIRST AND then add in things one at a time so we can SEE when something changes and then decide if we need to LOWER a scenery setting OR get rid the addon
 
The PLANE TAKES PRIORITY OVER THE SCENERY OR ANY 3RD PARTY ADDON PERK
 
The name of the product is FLIGHT SIMULATOR  (Prepar3D is FSX with development upgrades, SAME THING)
 
Its not:

CAR AND TRUCK SIMULATOR
PEOPLE SIMUALTOR
PHOTO OP SIMULATOR
HD AIRPORT SIMULATOR
WALK AROUND THE PLANE, TERMINAL OR GAS STATION SIMULATOR
SURFS UP WAVES AND REFLECTIVE WATER SIMULATOR
WAVY GRASS AND SHINY HANGAR DOOR KNOB SIMULATOR
COW, BIRD, CHICKEN, HORSE AND AIRSOCK SIMULATOR
HOLODECK ON THE USS ENTERPRISE SIMULATOR
 
 
its    FLIGHT SIMULATOR, meaning the PLANE takes PRIORITY over ALL else
 
any addon you have that falls under the list I posted above which includes any environment addon that introduces 2048/4096 HD textures should be REMOVED or DISABLED for proper initial setup of any sim.
 
 
If you jumped on the Prepar3D bandwagon thinking you will run better on the same hardware with the same addons and with the same monitor spans/pixel displays but with a lot more eye candy... you got totally snookered.
 
These people in forums when it comes to FSXSE vs P3D are like Apple vs Microsoft, they are all nuts and none of them will believe anything but what they want to believe and will swear their sim version is better than anything else. P3D gives you more eye candy and it comes with as much work as FSXSE to get locked down if you want to get the eye candy goodies..  and if you are using hard hitting addons you may find those addons do not look as smooth in P3D without using SGSS settings that WHOOOOOPS, performance killer!
 
Six of one, 1/2 dozen of the other     Give and Take     
 
It means, FSXSE and P3D are at the core nearly the same until they scrap backwards compatibility code in either and rewrite from the ground, up
 
 
If you have been sitting there hacking based on guides like this: http://www.codelegend.com/forums/viewtopic.php?f=2&t=601
that needs to ALL GO AWAY and stop the tweaking NONSENSE. You need a clean default Prepar3D install with a clean config and if you use anything ONLY APPLY the items I posted above in that config, NOTHING ELSE
 
the only item of importance is, just like with FSX/SE..  that P3D is installed outside of Program Files in its own directory and then start clean with no crap tweaks, and, no 3rd party addons running to begin the process.
 
 
 
If you comprehend and understand these facts, I will move forward with initial setup as soon as I can. If I get time later tomorrow night when I get back to the hotel I will post then, if not it will be Monday or Tuesday of next week.
 

Sorry but real life takes priority.
 
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-07-2015 at 5:27am
Thanks alot Nick incase i forget have a safe trip.
</span>
Only thing i installed was active sky next, REX 4D and 737 NGX to start off with, i'm running no NVI settings followed your tweaking guide above. so pretty basic, and feeling its alot smoother at the moment it may change yes, like you said. But i have a good OS7 setup and descent hardware.

I thought P3D was a totally new platform, so i suppose they used the same code as FSX?

Enjoy the weekend.
W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
Avidean View Drop Down
Senior Member
Senior Member


Joined: February-04-2012
Points: 1349
Direct Link To This Post Posted: November-07-2015 at 7:08pm
Regarding HT=on or HT=off I have tried both properly.
No AF with HT=off and AF=254. At least I think that's what it was :-)
Whichever AF disables one of the LP's in the first Physical Processor
of an 17 4770k

I really couldn't see any difference but it struck me that with HT=on
all the other programs on my system that benefit from HT get what they
want :-)

Enjoy Toronto Nick. If your at a lose end, I'll happily buy you a beer or three. :-)
I hate feeling indebted to anyone. LOL
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-09-2015 at 7:33pm
What MSI afterburner? Can i disable that now?
W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
NickN View Drop Down
Certified Professional
Certified Professional


Joined: November-21-2007
Points: 21176
Direct Link To This Post Posted: November-10-2015 at 10:25pm
THIS IS NOT A GUIDE OR A COMPLETE DOCUMENT, IT IS A SMALL SNIPPET FROM A UNEDITED DOCUMENT THAT IS STILL IN PRODUCTION FOR PREPAR3D V2 AND V3
 
I POSTED A SMALL PORTION OF IT HERE TO HELP ONE PERSON GET STARTED.
 
IF YOU CAME HERE THINKING YOU CAN PICK AND PECK AT WHAT I POSTED WITH A SIM FULL OF ADDONS AND IT HAVE VALUE, YOU ARE WRONG.
 
THERE IS A COMPLETE METHODOLOGY INVOLVED THAT HAS NOT BEEN FULLY REVEALED AND ALL I AM POSTING HERE IS A SETUP BECAUSE THE PERSON ASKING FOR HELP DOESN'T HAVE A LOAD OF SILLY ADDONS LOADING DOWN HIS SIM.
 
THE FULL DOCUMENT WILL BE MADE AVAILABLE SOMTIME IN DECEMBER
 
 
 
 
I'm working on a guide that will be released in the GEX forums like the original FSX tuning thread was years ago.
 
MSI afterburner as outlined is used for fan control and GPU temp monitoring for Nvidia cards. I find it a good tool for making sure the video card runs cool. Its not for overclocking the video card in my outlines although it can be used for that. Video card overclocking nets very little in ESP render engines and is not worth the small increase in performance for the potential wear and tear on the card.
 
 
I outline its use to override the Nvidia video card BIOS and make darn sure the speed of the fan(s) on the card are running based on the temp of the card.
 
 
 
here is a small snippet from the thread which is currently hidden.. it is by no means the entire document but it will show you how I start off. Your system may need to reduce the autogen trees and buildings a notch or two and perhaps the scenery radius a notch. I cant say for sure but once the thread is done you will be able to figure it out yourself and I will post a link to it in this thread.
 
 
I would start off with exactly what I show below for settings and if needed reduce in this order after each test flight if performance is not good after each test run:
 
try changing Frame Lock to unlimited with and without Vsync in different test flight flights. Sometimes it is best to set frame lock at 25 with Vsync/Triple buffer or without Vsync
 
The frame lock is harder to get locked down in P3D than other FS versions. Its a trial and error observation during the flight. Once you have found the best frame rate setting then if perf is still not good and/or stutters persist,..  move to reduce these in the order presented below, each one 1 tick at a time, not all at once! 
 
a. Autogen trees 1 or 2 notches
b. Autogen buildings 1 or 2 notches
c. Scenery complexity a notch
d. Scenery Radius 1 or 2 notches
 
 
 
============================================
 
 
PREPARING FOR THE FIRST FLIGHT CHECKS

 

There are a few things we must clearly understand before doing any of this..

 

Setup and tuning is done in steps, not leaps.

 

Changes are made in each step to find the smooth sweet spot with a default plane and then you add in your primary payware aircraft and start over. Addons stay out of the mix until that plane renders smooth and then the critical addons are introduced one-by-one with test flights in between. By doing it this way you get to know your sim and your hardware limitations as the elements are added and the sim re-tuned to accommodate them. By doing this you will learn how to make corrections fast if conditions change so you are not sitting there going round and round daily.

Every time you increase a slider or check a check box you add MORE to the render, therefore it takes AWAY from the performance, no matter if you can see that change right away, or not. Just because you can not see a obvious drop doesn't mean it didn't happen or wont rear its ugly head later when the scene or the aircraft is changed or another addon is loaded.

In the case where you have come here looking for ways to get your sim running better but already have a fully installed sim with all sorts of addons already installed.. you must understand, many of those need to be disabled and temporarily eliminated. Not doing so is going backwards. There is a reason you are here and unless you eliminate the pile you have in your sim it will be very difficult to ascertain what it is causing your issues. You would not be here reading this if your sim was running with little or no problems, so please heed my advice below...

In the first initial test flight, there are to be NO ENABLED:

a. payware airports
b. payware planes
c. external weather engines running
d. camera tools or any side programs like that
e. payware AI running in large number, keep AI very LOW or even OFF
f. big regional scenery packages that include a lot of extra airport/city models to render
g. addons other than very basic scenery addons such as landclass and basic ground textures

h. SweetFX, SHADE, ENB or anything that works like that including any manual hacks of the shader files. Get it out of the sim. Add them later if you cant do without them of course and suffer anything they may introduce

and MOST IMPORTANT..   NO HD, SHD or whatever they call it today environment textures for clouds, water, sky or airport grounds

IF you wish to use a 3rd party environment program for clouds/water/sky, thats fine as long as the graphics installed are 1024 x 1024 DXT which is close enough to sim default. PLEASE, do not run HD enviornment textures and especially textures that are not in DXT format, or, properly mip-mapped when tuning. If you add that junk in later you can live with the result but please don't do it now. 

If you use products such as UTX/GEP3D or addons that simply change ground textures and landclass or reshape the land they are ok as long as you have setup UTX so it doesn't slam the sim.

Those typically have a low footprint on the system and since their changes are total geographic in nature but add little or no heavy hitting models to the mix, they are ok and good to start with since you want to tune with them in play and build from there.

 

 

THE DESIRED TUNING ENVIRONMENT  

The first tuning flights are to establish a flight with a default aircraft that has:

1. A good size hub involved with several smaller airports in the area 25-45 miles around

2. A large city area with several other cities within the 25-45 mile area

3. Large bodies of water but also large amounts of all types of land with flat land, foothills and mountain ranges. A lot of different terrain and water bodies/features.

4. A static weather theme that has clouds, haze, fog, rain and storms that can appear.


To accomplish the goal we use Seattle, Washington and the hub KSEA on runway 34R pointed toward Seattle with the weather theme "building storms" and the time of year Summer/mid day. The goal is to place into the initial tuning of your sim every ground element the hardware will deal over time within one geographical are for the flight path and then trim for smooth flight as the aircraft takes off, circles the area and then lands.

Of course you can start out in New York City or the worse performing city in Flight sim, Tokyo, and do all this but in those locations you wont get a fair representation of the average scenery level setup your system will run. If tuned right you can compensate quickly for such cities later with a few simple slider changes on the fly as you approach them or boot a flight into them. 

 

 

 

SYNOPSIS OF THE TUNING PROCESS

Once smooth flight is established with a default plane, then a reboot of the system occurs and the payware planes can come into the picture with the SAME established settings that the default plane ran and the same flight path. The re-tune flight is run to get the payware plane flying as smooth as the default aircraft and work out the sliders.

 

Once the payware plane flight is locked down, then we reboot and either bring another payware plane into the sim for testing OR start adding in the addons starting with the one you consider most critical for your personal sim use. They are always added ONE AT A TIME with the same test flight repeated to find out if any scenery settings or frame lock strategy must change.

Once smooth flight is confirmed or achieved by tuning we reboot the computer and add in the NEXT critical addon, then rinse and repeat the test flight with the payware plane you prefer and the now 2 critical addons.

As you go along and add in your absolute necessary addons one at a time you will see when and if the performance begins to drop and reestablish smooth flight.

When all is said and done and all your addons have been added in, if that means during the entire test/tune process scenery complexity and autogen ends up being dropped a few notches, or, you lose cloud shadows, or, you cant run object reflections.. then so be it.

In some cases hardware ability may define that some addons may simply not be friendly and maintain a good amount of scenery sliders or AI. This is where you must decide what is more important to you in addons running in the sim with your payware plane but my philosophy always is: The PLANE takes priority over all else.

You are in the sim to fly a complex plane and safely land it under the most realistic smooth flight conditions possible, not look at the people, cars, gas stations, cows, shiny hanger knobs and pretty birds.
Alright, so those are the ground rules to tuning and a description of how its done.

Its the same process for FSX, FSXSE and any version of P3D.

 
 
 
 
=====================================================
 
 
IMPORTANT: DONT BANG YOUR HEAD AGAINST THE WALL TWEAKING, LESS IS TYPICALLY BETTER IN PREPAR3D AND THERE IS NOT A HECK OF A LOT OVER AND ABOVE WHAT I WILL SHOW THAT WILL MAKE MUCH DIFFERENCE....   ITS ALL IN THE HARDWARE, THE CLOCK, AND, THE SLIDERS/CHECKBOXES, AND, THE QUALITY IN TEXTURE DESIGN OF THE ADDONS YOU CHOOSE TO RUN - http://www.simforums.com/forums/guide-mipmapping-and-optimising-textures_topic52893.html
 
=============================================================
 
 
 
 
START PREPAR3D FOR THE FIRST TIME:
The first launch of Prepar3D is not for testing performance or making any judgment calls. The first launch is simply about setting up the primary monitor resolution and our initial graphics and scenery settings.
 
 
This is only to get the ball rolling do some quick visual checks and make the base setup selections for P3D.
 
 
FIRST:

If you already have a fully loaded sim with 3rd party addons/tool/scenery. etc PLEASE disable any of the addons I mentioned above before starting the process. Also make sure that if you have Nvidia Inspector on your system that it is set to PREPAR3D DEFAULT profile and there is no influence from NVI in the mix.

In Prepar3D NVI is useless for multi sample AA control. The sim itself must control that since its a DX11 application. The only AA Nvidia Inspector can control is Sparse Grid Supersampling (SGSS) and believe me, if you can avoid using that at ALL COSTS, I would...  it eats performance worse than in FSX especially in any heavy weather.
 
Leave NVI OUT of the tuning process. SGSS is something that comes LAST if you decide you wish to run with it.
 
 
We obtain the performance first, then see what it is that removes that performance so we can quickly make adjustments and don't desk-bang our heads in an endless tuning loop; AKA: The Flight Simulator Hamster Wheel
 
 
 
 
 
NEXT:
 
If you use Nvidia Inspector in the past for Prepar3D, please open it, select the Prepar3D profile and then click the green Nvidia icon in the top of the box, click APPLY. This clears the profile and assures NVI wont interfere with P3D using old settings.
 
 
Launch the Nvidia driver control and select the Manage 3D Settings> Click the tab Program Settings and then bring up the Prepar3D profile. Scroll down to:  
 
Power Management Mode and select PREFER MAXIMUM POWER 
 
Set Vertical Sync to: ADAPTIVE (half refresh rate)
 
click OK.
 
 
Close the driver control.
 
 
 
 
 
 
 

Launch Prepar3D and set up the test flight as shown below

 

When the flight boots realize that if this is the first time you have ever run Prepar3D and flown a plane in it for any length of time that the sims shader cache must build. In that process the flight scene may be slow to load, flickers and spikes may be seen, and, if this is the first time you are running P3D the first flight is NOT a tuning flight, its a flight to allow the shader cache to build because performance may not be very good during that time.

If this is a first run of Prepar3D for your system then tuning is worthless until a short flight is made around the area, the plane landed, the sim is closed, the system rebooted and THEN the next flight begins the actual slider and checkbox tuning process.

 
 

INITIAL TEST SETTINGS

Once your flight loads and the scenery has appeared, SAVE the flight and name it: TUNING FLIGHT for future use 

Bring up the settings menu. Follow the boxes I posted below and duplicate exactly what you see making sure your monitor is set correctly in the drop-down x32. What is shown in my monitor. You must set it correctly for yours. The monitors native Windows resolution is where I set mine.

 

NOTE: If you use a monitor span the higher the resolution you run the LOWER your performance may be. Its is best to keep large resolution spans as low as possible. Usually 2500-3300x is OK for large spans but not much higher, lower is always better. Huge 4500-5K spans are very hard on a system. I would avoid that and keep it reasonable.

 

BE AWARE: The settings I have posted below are for a decent modern Haswell or better computer system that runs a clock speed of at least 4Ghz+ and a 780 series video card or better. This is the initial setup to see what your system will do. It does not mean these settings will remain. The goal is to start reasonable, start with a good show flying a default plane, the whittle away at the settings as items are added to the sim.

 

 

Duplicate this setup and please do not add anything to it:

 
 
 FRAME LOCK and use of Vsync is going to be different for different systems and may be different for a assortment of planes/scenery combinations. That will all be trial and error and will probably be something that you will need to rework even though all other settings may find a common place where they are hardly ever changed after tuning.
 
Right now we are using ADAPTIVE (half refresh rate) vertical sync. This is very similar to Nvidia Inspector 1/2 refresh and you must run either 30 or 60 FPS locked to make use of it. If you run unlimited frame lock you will need to disable Vsync in Prepar3D or it may be very jerky with it enabled.
 
 
I am not going to get into the use of SSGS right now. Tuning comes first for smooth flights. Additional AA settings is something that should be considered last since they will have a very defined impact on performance if used.
 
 
 
 
The settings above are where most of the tuning will occur. Just about everyone should be able to run the water settings I posted however some may end up removing the terrain and vehicle reflections.
 
Scenery Complexity and Autogen sliders will be the primary tuning point other than AI traffic. On some slower systems the Detail Radius may end up dropped a notch or two but everything else should remain as shown.
 
 
 
 
 
 
 
Please do not use HDR at this time. I suggest it be left off altogether however you can decide that LATER, not now. HDR washes color from the image and I personally do not find the effect very realistic. We will be using CLOUD SHADOWS to create a dynamic lighting environment which I personally find far more realistic than HDR, especially when a good external weather engine is used.
 
Every setting shown above COSTS YOU so do be sure to duplicate what I posted above. You may or may not be able to run the cloud shadows if the system gets too bogged down with addons and a hard hitting plane, but we will start with them on. The settings I posted for them have an impact but not excessively hard.
 
 
 
 
 
 
 
 
PLEASE KEEP CLOUDS AT 60 MILES FOR NOW..    after tuning if you wish to test a higher value, 80 MILES is the MAX I would ever run. Any more in hard weather and the sim perf crushes. Even 80 can be hard on a system in heavy weather.
 
 
 
 
 
Shut off the car traffic as it can have a hard performance hit.
 
Depending on the AI system you use, 3rd party or the default, the AI settings will have a huge impact on your performance. The default AI really hits a system hard. A good designed replacement is recommended but for right now, keep all AI plane traffic set very low and do not raise the airport vehicle slider past what is shown as it will cost in performance. The features associated with that slider can be tested later if desired after everything else is setup.
 
 
 Remember the goal is that the PLANE takes priority over all else. Once the plane is smooth then the perks come in.
 
 
 
 
THE FIRST FLIGHT
 
Once initial settings are made we make a observation flight that has nothing to do with judging stutters, blurs, or anything for tuning. The purpose of this flight is to build the initial shader cache and to make sure we see a render and there is nothing exceptionally bad being seen such as nasty strange lines, anything that would indicate there may be a hardware problem or something very 'seriously' wrong and its constant
 
If you are seeing exceptionally bad graphic glitches or the image is not displaying then there is a possibility of a video card hardware failure or a issue with the video drivers. 
 
You will need to diagnose the 3D render corruption problem before proceeding.
 
You can use software such as 3DMark to test your system for render. If that benchmark software displays the same graphics visual glitches then there could be a defective video cards or the possibility of a corrupt OS install at play. This is an area that MUST BE diagnosed/repaired BEFORE continuing.
 
If you are not seeing any major graphic issues then continue on..
 
 
=======================================================
 
 
 
 
THE TEST FLIGHT FOR ALL INITIAL TUNING TESTS
 
You can refer back to this section as you progress if you may need to review this information. All initial tuning flights will follow the same flight path.
 
The the first thing we do before ANY flight now or in the future is to go to OUTSIDE - LOCKED SPOT VIEW and pan visually around the outside of the aircraft at least 5 to 7 times. This will help preload the buffers and helps considerably with initial flight visuals and performance.
 
You are on the runway at KSEA. Take off on runway 34R and head toward the city of Seattle. Fly as you normally would but keep the flight level at around a max of 5000ft. Continue past the city of Seattle and fly strait out toward Snohomish County Airport (KPAE). Just before KPAE airport turn right and begin a wide circle loop toward the mountains and finally back around toward the city of Seattle. Place yourself on the approach for runway 16L and proceed to land back at KSEA. You can park at any terminal.
 
 
 
NOTES AND WHAT TO OBSERVE:
During this flight you are welcome to use all views but do be aware that switching from tower to any other view will usually result in the ground being blurry for a period of time till the render catches back up. This is an issue that has been around since 2006 with FSX and is also noted in the Nvidia driver release notes for Flight Simulator as "not a Nvidia issue"
 
 
 
<IN PRODUCTION HERE: TO BE CONTINUED>
 
 
 
 After the first flight and the sim is closed:
 
EDIT THE CONFIG WITH BASICS ONLY AND DO NOT ADD ANY MORE..  
 
If you have already loaded your config with tweaks, please remove the Prepar3D.cfg file and let the sim build a new one after launch and close of the sim
 
KEEP IT SWEET AND SIMPLE...   THIS SECTION IS OPTIONAL. SOME OPT TO RUN A CLEAN DEFAULT CONFIG FILE, THAT IS OK IF YOU WISH. I have found the settings outlined below all have value and I have never tuned as system to date without using them.
 
NOTE: It is possible some of these may need to be adjusted or even eliminated completely. Right now its a fact finding mission and all of the settings outlined below usually have value more often that not, so we will add them now and adjust/remove as needed in observation of the result.
 
 
If you have not already done so, add/edit the following into the Prepar3D.cfg file using notepad.
 
2 of these you must manually add under the [HEADERS] I show below into the config. Copy/paste from here is fine. TBM is already in the config, simply edit the value.
 
NOTE: DONT ADD THE HEADER I POSTED BELOW, JUST THE LINE(S) BELOW THE MATCHING HEADER IN YOUR CONFIG!
 
[DISPLAY]
 
TEXTURE_BANDWIDTH_MULT=80   //start here
 
[MAIN]

HideInfoText=1  // gets rid of screen readout for brakes, etc.. unless you want that, then eliminate this line

FIBER_FRAME_TIME_FRACTION=0.12  //start here
 
 
[SIM]
 
OPTIMIZE_PARTS=1   //add for P3D v2.x, should already be in v3x
 
 
Save and close the config file.
 
Some of you may be wondering why I left out:
 
[JOBSCHEDULER]
AffinityMask=xxxx
 
That is because now is not the time to add this config entry, if it is even needed at all.
 
In Prepar3D use of that edit can, under the right conditions, have value especially for those who run their systems with Intel Hyperthread enabled. I personally do not use HT and opt for a higher/cooler clock speed. If I want HT enabled for audio/video or engineering programs that will make full real use of HT I will boot into the BIOS and enable HT for that purpose alone and shut it back off when finished.
 
#1 performance tweak anyone can do is overclock in FSX/ESP/P3D. Even a small overclock will have a positive influence on sim performance. Newer computers have automated performance features for those who don't know how to manually clock safely.
 
 
Once tuning has reached a certain point and addons are running in the sim, especially the utility addons such as weather engines, etc that is when testing AffinityMask comes into the mix. Putting it in the config now serves no purpose and is quite silly to do.
 
 
 
 ============================================
 
 
IN PRODUCTION
 
 
 
 
 
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-11-2015 at 6:16am
Nick before i start to read, thankyou ;) one other thing can i share this thread on AVSIM P3D ?
W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-11-2015 at 6:25am
I'm finding without using NVI and unlimited frames works best for me thats with default P3D settings, i will work through your guide later on. Not once has it stuttered like FSX its actually running smoothly :)
W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
NickN View Drop Down
Certified Professional
Certified Professional


Joined: November-21-2007
Points: 21176
Direct Link To This Post Posted: November-11-2015 at 11:18am
ok well then if it aint broke, don't fix it and disregard what I posted above
I thought you were doing things like browsing tweak sites and so forth to get the sim running better. If you are not having any problems then don't mess with or change anything.
 
 
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-11-2015 at 12:07pm
I'll do the P3D settings you posted above
W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
Avidean View Drop Down
Senior Member
Senior Member


Joined: February-04-2012
Points: 1349
Direct Link To This Post Posted: November-11-2015 at 12:41pm
I have already tried the setting Nick posted and P3D V3 Is looking far better than it was with my own setting. With my own setting I did see stutters. They where not that bad but with Nicks initial setting the in the TUNING FLIGHT the sim was really smooth even when panning :-)

And there was plenty of Auto gen.:-)
Back to Top
NickN View Drop Down
Certified Professional
Certified Professional


Joined: November-21-2007
Points: 21176
Direct Link To This Post Posted: November-11-2015 at 2:12pm
There is tweak that can effect the visual volume of autogen below the aircraft.. but it may create a load issue for some which is why I am not promoting it
 
 
 
If you use this remember you did it because later if you come across perf issues or OOM's, it could be caused by this.
 
Prepar3D reduces the autogen around the area of the plane by having the max autogen volume start out at LOD-2, and by reducing the LOD call to 0 it tells the sim to load'it-up everywhere
 
[SCENERY]
 
AUTOGEN_BATCH_LOD=0   //  the default is 2    
 
 
If you have a good eye you can see the difference in volume. Its not a performance tweak, just the opposite!  lol
 
 
 
 
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-11-2015 at 2:20pm
You set Vsync in P3D how does that work then?
W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
NickN View Drop Down
Certified Professional
Certified Professional


Joined: November-21-2007
Points: 21176
Direct Link To This Post Posted: November-11-2015 at 2:46pm
I'm not sure what you mean. The settings must be made in Prepar3D since it has direct control over the DX11 API though the game settings. That's why multi-sample AA and a few other setting wont work with NVI in P3D. The sim must control those
 
Vsync is used to control image or screen tearing https://en.wikipedia.org/wiki/Screen_tearing however with the changes made to P3D on the graphics side some people may find they run smoother with Vsync disabled and they may not see screen or image tearing.
 
As I posted above frame lock and Vsync are very system and scene render specific and there is no right way or wrong way to set them.
 
In some circumstances whereby the users system has a hard time running 30FPS constantly find it best under that condition to set frame lock to 20-25 and run with Vsync, others with the same frame limit may find setting to unlimited without Vsync (or with) does a better job.
 
There can be differences in that based on the plane in use. One plane may play nice with a locked 30 frame rate and another likes locked 60
 
I have seen circumstances where I fly out of one hub running locked 30 and when I enter the airspace of my destination the city scenery load demand I reset frame lock to unlimited.
 
 
The point is, there is no rule with frame lock/Vsync    its what ever works
 
I find most of the time I can leave it alone at 60 locked/Vsync on
 
 
 
Back to Top
Driver170 View Drop Down
Senior Member
Senior Member


Joined: March-26-2014
Location: UK
Points: 996
Direct Link To This Post Posted: November-11-2015 at 2:55pm
Can we choose to use windows 7 aero mode in window mode? Somehow i get better smoothness?
W10 Home, 10900K, ROG Maximus XII Hero, EVGA RTX 3080ti, GSkill Memory DIMM 32 GB DDR4-3600 Quad-Kit, Corsair Hydro Series iCUE H150i PRO XT, Fractal Design Define 7 Mid-Tower Case
Back to Top
 Post Reply Post Reply Page  123 4>
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.281 seconds.