[P3D V5] Tips and Tricks
Results 1 to 13 of 13

Thread: [P3D V5] Tips and Tricks

  1. #1

    Icon4 [P3D V5] Tips and Tricks

    Hi,

    Since there is a lot of confusion and problems running V5 in the moment I thought I'd open a thread with tips and tricks regarding the configuration.

    I myself had - or still have sometimes - the dreaded memory runout on my 970 card and noticed, that it is bound to the truesky config. When I go from the medium setting to high it eats almost 1 gig of memory (I observed it jumping from 2.1 to 3 gig). My card has 3.2 (from four) to give, and with a 3gig usage it is pretty much topped out and prone to crash.
    First step is to tone down the TrueSky settings and second the other lighting/shadow configs. There's a point where the sim starts to run well enough.

    Maybe other here found similar config tricks which helped and would like to share them?


    Cheers,
    Mark
    My scenery development galleries:
    https://www.dropbox.com/sh/x0skkam7xu8zz8r/DFwnonB1nH

    Solomon 1943 V2 Open beta download: http://www.sim-outhouse.com/download...on-1943-V2.zip
    Solomon 1943 V2 update 2013-02-05 download: http://www.sim-outhouse.com/download...2013-02-05.zip


    Current Project: DHC-4 / C-7a Caribou by Tailored Radials
    Dev-Gallery at https://www.dropbox.com/sh/qjdtcoxeg...bAG-2V4Ja?dl=0

  2. #2
    Great thread Mark, for those who have purchased most late version Milviz aircraft you will probably find they CTD when installed in full. Something will will help is to disable TrueGlass and RealLight. I have my Milviz F-86 and Milviz FG1D Corsair working perfectly. Also we found that disabling the windshield.dll to windshield.dll.off in the panel folder will allow the fantastic Jahn C-47 / DC3 to function perfectly.
    Last edited by stovall; April 22nd, 2020 at 07:37.
    Regards, Tom Stovall KRDD


  3. #3
    I take it you are running the Milviz (vs. Section 8) F-86? That's great news, if true. Can't wait to load that one.

    Kent

  4. #4
    Quote Originally Posted by stovall View Post
    Great thread Mark, for those who have purchased most late version Milviz aircraft you will probably find they CTD when installed in full. Something will will help is to disable TrueGlass and RealLight. I have my Milviz F-86 and Milviz FG1D Corsair working perfectly. Also we found that disabling the windshield.dll to windshield.dll.off in the panel folder will allow the fantastic Jahn C-47 / DC3 to function perfectly.

    How did you get Milviz FG1D Corsair to work? All i get a CTD. Thanks in advance
    Greg :USA-flag:

  5. #5
    Quote Originally Posted by Gregory Paul View Post
    How did you get Milviz FG1D Corsair to work? All i get a CTD. Thanks in advance
    You need to not load TrueGlass and RealLight. That will cause a CTD every time. You can go to the panel folder before launching the aircraft and disable truelight.dll to truelight.dll.off. Actually that is all you have to do even if during the install you install everything. Worked for me.
    Regards, Tom Stovall KRDD


  6. #6
    Thank you for the tip on the Milviz aircraft, Tom! I had run into a CTD with the F-86 as well, and I'm glad it is such a simple fix.

  7. #7
    As we wait for our weather software partners to update their products, we always can use FSXWX (free!) to inject weather into P3D V5. I found that there is one setting which is crucial: Time has to be set to "Current". If you don't set this, FSXWX throws an error and does nothing. The other settings which work with my P3D configuration (TrueSky = ON, set to "Medium) are as follows:


    My scenery development galleries:
    https://www.dropbox.com/sh/x0skkam7xu8zz8r/DFwnonB1nH

    Solomon 1943 V2 Open beta download: http://www.sim-outhouse.com/download...on-1943-V2.zip
    Solomon 1943 V2 update 2013-02-05 download: http://www.sim-outhouse.com/download...2013-02-05.zip


    Current Project: DHC-4 / C-7a Caribou by Tailored Radials
    Dev-Gallery at https://www.dropbox.com/sh/qjdtcoxeg...bAG-2V4Ja?dl=0

  8. #8
    I may need to clarify about the use of the terrain detail texture "detail1.bmp" that I mentioned in another thread. Apparently it is used but one has to make sure that the entry DETAIL TEXTURE=1 exists in the prepar3d.cfg.

    Although this should be set to 1 by default, mine was set to 0. Setting it to 1 activated the detail texture and I was able also to use the REX one for grass.

  9. #9
    Quote Originally Posted by Dimus View Post
    I may need to clarify about the use of the terrain detail texture "detail1.bmp" that I mentioned in another thread. Apparently it is used but one has to make sure that the entry DETAIL TEXTURE=1 exists in the prepar3d.cfg.

    Although this should be set to 1 by default, mine was set to 0. Setting it to 1 activated the detail texture and I was able also to use the REX one for grass.
    Ahhh great stuff, I missed that already!! Thanks Dimus!!


    Cheers,
    Mark
    My scenery development galleries:
    https://www.dropbox.com/sh/x0skkam7xu8zz8r/DFwnonB1nH

    Solomon 1943 V2 Open beta download: http://www.sim-outhouse.com/download...on-1943-V2.zip
    Solomon 1943 V2 update 2013-02-05 download: http://www.sim-outhouse.com/download...2013-02-05.zip


    Current Project: DHC-4 / C-7a Caribou by Tailored Radials
    Dev-Gallery at https://www.dropbox.com/sh/qjdtcoxeg...bAG-2V4Ja?dl=0

  10. #10

    Scenery Design Upgraded to P3D v5

    Arno has been busy updating Fxeditor, ScenProc and especially ModelConverterX. You can update everything by clicking HERE!
    Regards, Tom Stovall KRDD


  11. #11
    Quote Originally Posted by Dimus View Post
    I may need to clarify about the use of the terrain detail texture "detail1.bmp" that I mentioned in another thread. Apparently it is used but one has to make sure that the entry DETAIL TEXTURE=1 exists in the prepar3d.cfg.

    Although this should be set to 1 by default, mine was set to 0. Setting it to 1 activated the detail texture and I was able also to use the REX one for grass.
    I lost the detail bitmap again and I checked the prepar3d.cfg file. The setting had gone back to 0. In the meantime I had installed new ORBX regions. Can't say if this was the reason why the setting changed, but if you suddenly miss the detail check the setting again.

  12. #12
    That must have been ORBX. I fiddled around with the texture and made a new one in 4k the past days and the setting never reverted back.

    Cheers,
    Mark
    My scenery development galleries:
    https://www.dropbox.com/sh/x0skkam7xu8zz8r/DFwnonB1nH

    Solomon 1943 V2 Open beta download: http://www.sim-outhouse.com/download...on-1943-V2.zip
    Solomon 1943 V2 update 2013-02-05 download: http://www.sim-outhouse.com/download...2013-02-05.zip


    Current Project: DHC-4 / C-7a Caribou by Tailored Radials
    Dev-Gallery at https://www.dropbox.com/sh/qjdtcoxeg...bAG-2V4Ja?dl=0

  13. #13
    SOH-CM-2021 BendyFlyer's Avatar
    Join Date
    Nov 2012
    Location
    Country New South Wales Australia
    Posts
    1,433

    Joysticks and Controllers and P3DV5 - some other stuff!

    There are almost never ending threads on various forums with people encountering problems with setting up their joystick or controllers with P3D. Unfortunately I cannot provide a HOWTO due to the endless permutations of such devices. I can share with you a lesson hard learnt. P3DV5 is not forgiving to a setup where you introduce a conflict between the key commands allocated within the program and what you want the controller to do! I learnt this the hardway after spending 3 whole fruitless days chasing down what I first thought was a model clash, then a scenery clash, then a display driver issue, then maybe a disk error or corruption issue. The problem started when I carelessly (in retrospect) reallocated a number of functions done by key command by P3D to my joystick buttons. Like a lot of simmers I had grown accustomed to doing this because of poor VC modelling, old 2D panels in FSX and before it made life easier then! What happened was I could load a model and a scenery then use my new joystick allocations to switch views to the mouse view pan (I like this in the VC because it enables me to quickly shift my view to the area I am interested in to operate a button or control etc.) repeatedly the sim would hang then CTD. Check of the event logs - no errors no other software issue infact nothing logged at all!

    Back tracking over all the changes - I had rebuilt P3D from the ground up due to some other corruption issues (caused I believe by a sudden mains power failure mid sim - WIN10 does not handle such events the same way as WIN7 did - WIn7 would tell you this had happened and basically let you restart in safe mode or whatever - NOT WIN10 it just restarts unless it is totally fractured). This caused all sorts of issues that various repairs would not rectify so bite the bullet - clean it all up and start again. Plenty of backups etc so time consuming and major reloads of some stuff as I reconfigured a number of things that in retrospect were not a good idea (not keeping as much as you can out of the main sim and using the addon xml method extensively by the way making xml addon scripts you soon learn who has hidden anti-piracy buried all through their initial installation as well).

    So I worked out that for some reason P3D was letting me add in new control commands and not getting rid of the old ones or overwriting them so you could have 2 or 3 such commands for one function trying to work - in other words instant recipe for command conflict when the sim is running and hence the crash to desktop outcome - it just cannot handle that!

    I minimised what I wanted buttons to do first! In other words if the VC has a button or a switch use that via the mouse not a controller button. I was left with brake, park brake set, trim, normal throttle, spoilers and a mouse view function and I ditched the rest. I then went through the P3D setup menu in the sim and eliminated any obvious duplicate entries for the same function. Saved all that and now the joystick works perfectly, the sim runs perfectly again and no more CTD by something as minor as going from VC to F11 to then trying to mouse view pan.

    Now this maybe obvious to some but also using FSUIPS to smooth things out is also worth the time and effort.

    May not work for everybody but an interesting insight and a lesson well learned.

Members who have read this thread: 0

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •