Jump to content

jfwharton

Members
  • Content Count

    215
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

30 Neutral

About jfwharton

  • Rank
    Member

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thank you very much. That took care of it. Amazing program!
  2. I am running the latest version of Little NavMap and I export flight plans for multiple simulators and aircraft. With the last few updates the export names for FSX and P3D changed. Before when exporting for FSX and P3D it would use the format in this example, IFR Denver Intl (KDEN) to Albuquerque International Sunport (KABQ).pln. But now it exports to KDEN Denver Intl.pln. Is there a setting somewhere that I have missed that will change the export name format back to what it was, or at least include the departure and destination airport in the name? All other exports include the departure and destination airports. All except the export for FSX, P3D and now FS2020.
  3. I have been playing around with the settings for the Lear 35 for P3D v4.5 and nothing affects the brightness of the VC screen. In my attempts I somehow messed up the file and ended up copying the Reality XP GTN.ini from the P3D v5.1 installation and pasted it into the P3D v4.5 installation. Now the displays almost match. So don't know what was going on with the file originally in P3D v4.5 but at least the issue has been solved.
  4. I am having one issue however. Not a big one but one that is confusing me. I made the same changes to my Flysimware Lear 35A, Falcon 50 in both P3D v4.5 and v5.1. In v5.1 the GTN popups in both aircraft are very close in brightness to the VC GTN panels. However in P3D v4.5 the popup and VC panel in the Falcon 50 are very close but they are not in the Lear 35A. So I have no idea how to correct this and why it is happening to begin with. I use the same installer for both and select which version of P3D to install the aircraft to. Any ideas?
  5. OK I finally think I have it! On my Flysimware Falcon 50 I opened up the panel.cfg and the RealityXP GTN.ini files after making backups. I found the reference for the [GTN_750_1.DEFAULT]. Copied it and created a new section called [GTN_750_1.MYGTN]. In there I set the screen brightness to -40. In the panel.cfg file there were two references for the GTn 750. Window 6 which is in the upper section of the file and [VCockpit29] under the VC section. In [VCockpit29] I added the reference at the end to MYGTN ( gauge00=rxpGTN!GTN_750_1, 0,0,677,794,MYGTN). Saved everything and started P3D v5. Started a flight with the Falcon 50 and compared the vc gauge brightness to the popup and they match. Thank you for sticking with me.
  6. Thank you for the encouragement and the information. It still doesn't make any sense to me. I was looking for a tutorial on the internet that would show me a before and after to go by. I will keep trying but as I said, even though I have read your information it just doesn't click.
  7. Thank you for the information but it doesn't make any sense to me. The documentation is only helpful if one fully understands how the programming for the Reality XP GTN works, but I do not. So for right now I'm going to leave everything as is. I made a change to the popup panel from the linked post above that helped with the GTNs that were converted from the F1 GTN but I still do not understand how to adjust the brightness on the aircraft that have a Reality XP GTN installer. I really wasn't expecting to have to learn a new programming language just to use the Reality XP GTN. I'm hoping that F1 updates their software so I can go back to that. It didn't have this issue.
  8. The xTremeprototypes Lear 25 V5, the flysimware Falcon 50, lear 35A and some others. All have an option during the install to select the Reality XP GTN 750.
  9. I finally found what was causing the issue. The MILVIZ WX radar. Since there isn't a way to install the aircraft without the weather radar and for now I don't want to uninstall it because it works in P3D v4.5, I have gone into each aircraft's panel.cfg file and remarked out the weather radar gauges. This has for now fixed the stuttering issue. Yeah!
  10. Thanks for the response but none of that makes any sense for me. I just want something simple. As it is it took me hours for reconfigure the aircraft that I have that have the Reality XP GTN in them. So I thank you but guess I'll just have to accept the overly bright screen on some of my aircraft because the brightness wasn't set correctly by Reality XP. It took me two days to configure my aircraft and right now I'm very tempted to go back to the Flight1 GTN series where I didn't have this issue.
  11. I checked and that feature was not turned on. But thanks for mentioning it.
  12. I will look into that. I do use FSUIPC6 but when I had disabled it the sim still had the stutter.
  13. Thanks but that isn't worth it. Will just not use the flysimware aircraft much any more.
  14. I already tried that, disabling the GTN. But I have the GTN and WX radar in other aircraft and they don't have this issue. Thanks for the suggestions. But I have already checked, everything is up to date. Also this only happens in P3D v5.1. I have the same aircraft, scenery and addons in P3D v4.5 and no issue.
  15. I would also ask the question to Reality XP as to why all of this is even necessary to begin with. By that I am asking why the VC panel screen brightness is different from the Popup panel screen brightness? Shouldn't they be set to be the same brightness to begin with?
×
×
  • Create New...