Jump to content

MammyJammy

Members
  • Content Count

    84
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

78 Good

Profile Information

  • Gender
    Male

Flight Sim Profile

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

Recent Profile Visitors

681 profile views
  1. I have a placeholder in the doc to include directions on installing the ISG gauges. It's not all that difficult, but the default install makes it trickier than it needs to be. The cliff notes version is this: Install the ISG gauges using the download file included with your purchase from whatever online vendor like SimMarket. When you run the install, it may put them in a default FSX location of: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Gauges This won't work so you need to copy the "ISG" folder from that directory into the "Gauges" directory of your P3D install, where ever you have it installed on your PC. Download the most recent version of the ISG gauges from the ISG forums at: http://www.fsbuild.com/forum/viewforum.php?f=4 Download the latest version from one of the posts at the top of the forum. As of this post (2022-12-04) the latest are the 189 beta gauges. The DC-10 ISG integration won't work without the updates from the ISG site. From the zip file you download, copy the files over the existing files in your P3D/Gauges/ISG folder. It should over-write the existing ISG gauge files. That's it for the install. From there you can follow the directions in the DC-10 document to integrate the panel and FMC gauges. There is a way that I managed to get working with some symbolically linked folders to install the ISG gauges outside the P3D main directory, but it takes a lot more effort and doesn't really impact P3D upgrades too much (unless you totally wipe your PC).
  2. The directions to change the panel to support LNAV are part of the ISG gauge integration. In order for the LNAV to work, you have to have the ISG FMC installed such that it can create a flightplan for the LNAV to follow. Not that I am aware of, however I've used PFPX for a long time. Included in the doc are some recommendations on fuel and drag bias numbers to get the planning to be more effective. PFPX and the "lite" profile for it also under-plans the fuel burn significantly. If you are willing to unpack and edit the XML gauges I'm sure you could, but otherwise I don't know if that's an out-of-the-box capability. I could look into creating a KG gauge and including it someday...I have some other doc updates to make that I've been too busy to circle on.
  3. MAKE SURE you do not copy panels from the passenger DC-10 configurations to the freighters (-Fs)! The door panel gauge is different for the freighters and includes the click-spots for opening the main cargo door.
  4. On page 4 of the installation guide there is a table with a bunch of links to required software packages. The second link in the table is to the ZIP file that supports many of the customizations I've made to improve the DC-10 in P3Dv5. Within that ZIP file is a subdirectory... ISG -> Aircraft. Inside it are three starter ISG files for the DC1010, DC1030, and DC1040. If you don't have them, make sure you've downloaded the latest package (which isn't that new these days...). From there follow the document's instructions and paste them into the /Aircraft subdirectory of your ISG installation. I have on my to-do list an update to the section for installing the ISG gauges, as they may install into a default FSX path which then requires you to copy some stuff around the ol' fashioned way.
  5. No worries @Ray Proudfoot - I've been playing around with setups for those additional programs myself (I'm using the [Programs] section of FSUIPC as I don't want to run yet another thing like Process Lasso) and I have the processes running on the first core. I haven't seen the utilization of either the OS or any of the add-ons create any bottlenecks or thread interrupts across the first physical core and logical processor. My observations of the newer P3D versions, particularly 5.3, is that it really does benefit from as many cores as you can give it. I originally had some mask-offs of some of the efficiency cores for those extra programs, such as leaving the last E-core open for add-ons, but found it made a negligible difference in performance vs. giving that extra core to P3D for things like scenery loading, etc. The only issue I still have RE CPU performance with 5.3 HF2 is the loading stutters related to large BGL files. The two areas where I have scenarios to reliably test these issues are the Heathrow example I mentioned earlier, and a departure from LAX (Orbx TE Southern CA + FSDT KLAX). I'm hopeful a fix comes at some point from LM as it's really the last performance issue I'm having with my sim environment.
  6. Hi @Ray Proudfoot - The new affinity mask settings in 5.3 give some extra flexibility for how to manage the primary P3D threads separate from other threads it may spawn, such as EXE or DLLs associated with add-ons (through an add-on.xml or exe.xml/dll.xml configurations). This means you can still give extra cores to the P3D process space to keep those things away from the primary cores. In another thread, Rob Ainscough did some testing and found that reducing the basic AffinityMask didn't make a difference, and my findings have been similar. So what does First Core Free mean in the tool? It means that it will mask off the first core from the primary P3D threads/tasks. These are the heavier hitters of P3D, including the Main, Render, and FrameWorker ThreadSchedulers as well as all the other threads that support them such as scenery loading. The first core can still be used by other stuff and you can force affinity for things with FSUIPC, Process Lasso, Task Manager, etc. that still need to run within the P3D process space. Task Manager will show the affinity of the primary AffinityMask, but not the P3DCoreAffinityMask, which is where the heavy workloads are. Hmmm....Interesting - That has not been my observation, but I can give it a test over the weekend. I am running a similar setup on a 12900K (the first processor in many years I've run with hyperthreading on) with the first core free and FSUIPC's [Programs] section handling startup for a bunch of other stuff like ActiveSky, PFPX, and Navigraph Charts affinitized to the first core. My first core usage (both the physical core and the logical processor that go with it) hovers around 16% when P3D is running. If I'm recalling a past test correctly, it's somewhere in the 9% range with just the OS and the first core fully masked off from P3D via the AffinityMask setting. My current test count using a saved scenerio on approach to EGLL with Orbx TrueEarth and Aerosoft Heathrow is somewhere above 83 - Lots of affinity mask and Nvidia settings testing. The only other performance observation I've had with 5.3 and a processor with hyperthreading on is to make sure the cores with the ThreadScheduler, primarily the MainThreadScheduler, has the logical processor masked off. This gives you the advantage of all the other logical cores with hyperthreading but gives the MainThreadScheduler all the physical compute for that core. For your CPU, something like this: https://izn-flightsim.s3.amazonaws.com/affinity.html?cores=6&threads=12&affinity=4095&coreAffinity=4084&mainThread=0&renderThread=1&frameThread=3#presetAnchor [JobScheduler] AffinityMask=4095 P3DCoreAffinityMask=4084 MainThreadScheduler=0 RenderThreadScheduler=1 FrameWorkerThreadScheduler=3 The calculator will also be handy for making sure the ThreadSchedulers are numbered correctly, as it is the zero-indexed count of cores within the P3DCoreAffinityMask that indicate where they will run. If you have hyperthreading on, make sure they are running on physical cores, not logical processors.
  7. You may continue to have issues with frame rate drops on long-hauls with the A330. The weather radar in the Aerosoft A330 will continue to run in the background, even if you have it shut off on the pedestal from within the VC (the default is for it to run in a full scan, regardless if it is on in the VC). The config @mokeiko mentions is an edit that's required to adjust the background tasks for the weather radar, and is one of the two perf improvements in the link I included above. the copy/paste version: The weather radar in the Airbus series can also cause frame rate drops, particularly during long-haul flights. By default the Aerosoft Airbus will run the weather radar in the background, regardless if it is on, which on some systems can cause a memory/loop processing leak. Navigate to the directory into which you installed the Aerosoft Airbus. From there, go into the "Data" directory and open the file named "AB_ND_GDI.ini" Add this section to the bottom of the file and save: [WXRadar] WXBackgroundScan=0 WXBackgroundScanProto=0 // Remark: Some WX data are normally required to be scanned in background even when WX Radar is switched off. // Due to performance reasons on some customersystems currently the user can select between following background scanning modes: 0 = COMPLETE OFF (best frame rates), // 1 = LIMITED SCAN, 2 = FULL SCAN (normal status). As long as WX Radar is switched on, this parameter has no affect! This parameter is allowed to be changed at // runtime (just change this parameter in INI file and safe it) You can change the WXBackgroundScan to 1 if you prefer a limited scan and see no degradation in frame rates.
  8. I've encountered the same issue and there is a fix for it. There's some tuning you can do for the Aerosoft A330 to get it to behave on long-haul routes. Go here: https://izn-flightsim.s3.amazonaws.com/affinity.html The very bottom section on the page titled " Beyond Affinity Masks - Optimizing Prepar3D Performance (Prepar3D System Tuning Guide)" has a section for Prepar3D Add-Ons. In there is some stuff you can use for the A330 to reduce the load on the nav display and weather radar. If after you do this you still encounter problems, turn the weather radar on the center pedestal off.
  9. Back in 2019 I was headed back stateside from India via EHAM on a KLM 777-200ER. The forecast was very similar with strong winds gusting north of 40 knots out of the SW. We ended up landing on Rwy 22, the Oostbaan, which clocks in at a whopping 6,600 ft / 2,000m. With that arrival, I have landed or taken off on every runway at Schiphol. Could be some fun weather to try putting the heavies down on the Oostbaan from the front seat in P3D, instead of just along for the real-life ride...
  10. Getting the A330 working with FSUIPC is a borderline dark art, mostly because finding any info on how to do it is difficult. But have no fear! You can set it up to work pretty easily. Here's how I have it working on my ThrottleTek, which has no reverse zone on the throttle axes themselves, rather as a button on a separate part of the throttle. I don't have the Honeycomb so if it has a reverse detent/zone on the axis, this may not work. Load up P3D and hop into a scenario with the Aerosoft Airbus A330 loaded. For each axis, make sure it's configured in FSUIPC as below, with the Axis Throttle X Set (1 and 2, respectively). Check the "Profile specific" button and create or use a profile for the A330. Scan each axis and set as "Send to FS as normal axis" with the pictured Axis setting. From there, go to the Joystick Calibration tab and skip forward to the throttles section. Again, check the Profile specific? box in the upper-right. Set the range for each throttle axis and make sure that BOTH No reverse zone at the top and Exclude THROTTLEn_SET at the bottom are both checked. Hit OK, and close P3D. Find your FSUIPC install directory (either in the /Modules sub directory of your P3D base, or within the FSUIPC6 folder in your Prepar3D v5 Add Ons folder in My Documents). Open up the FSUIPC6.ini file and scroll down until you find the joystick calibration section for your Airbus profile. Mine is called "Airbus", yours may be "A330". Just make sure you find the right section for this profile. Within that profile, make sure the line UseAxisControlsForNRZ (bolded below) is set to "Yes". This is the real key to getting the throttles working in the Airbus. It will default to No so you need to change it. Again: UseAxisControlsForNRZ=Yes My config is below. Yours will be different certainly, as the calibration values for your joystick will be different. Just for reference as you edit the appropriate line in your own FSUIPC6.ini. [JoystickCalibration.Airbus] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=Yes FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 SteeringTillerControl=0 MaxSteerSpeed=60 RudderBlendLowest=1 Throttle1=-7647,-512,512,8088/32 SlopeThrottle1=4 Throttle2=-8392,-512,512,7968/32 SlopeThrottle2=4 Save the file and close it. Load up P3D, select the same A330, and give it a shot. The throttles should work.
  11. My advice for both of you would be the same, given you have 4 core processors with hyperthreading on: 1) Give P3D as many cores as you can. The newer 64-bit versions are much better at leveraging high core counts, so give P3D as much as you can. If you mask off 1 core and 1 HT logical processor, you are giving up 25% of your compute power. You can move the ThreadSchedulers around to give some breathing room from the OS and other stuff far more effectively w/ P3D 5.3. 2) Only put the ThreadSchedulers on physical cores. You want these to have as much horsepower as possible and that's not in the hyper thread of a given core. The worst case would be running two thread schedulers on the same core/HT core. Yikes, don't do that...You'll run out of compute on that core. For both, I'd recommend something more like this, leveraging all cores but being specific about where the ThreadSchedulers go: https://izn-flightsim.s3.amazonaws.com/affinity.html?cores=4&threads=8&affinity=255&coreAffinity=255&mainThread=2&renderThread=4&frameThread=6#presetAnchor If you really want to keep a core open for your OS, go for it, but I'd give it only a single core if you can. As per some other recommendations in this thread, I'd still leave the full AffinityMask on all cores. Something like one of these options: https://izn-flightsim.s3.amazonaws.com/affinity.html?cores=4&threads=8&affinity=255&coreAffinity=252&mainThread=0&renderThread=2&frameThread=4#presetAnchor OR https://izn-flightsim.s3.amazonaws.com/affinity.html?cores=4&threads=8&affinity=255&coreAffinity=254&mainThread=1&renderThread=3&frameThread=5#presetAnchor Of course you will have to test what works best on your respective systems and the type of flying you do. The free core may work better based on your add-ons, so experiment. Hope it helps.
  12. I stand corrected. I just did another test with NCP adaptive Vsync on for the Prepar3D.exe profile and OFF within P3D...Sure enough, 30fps.
  13. The Adaptive (half refresh rate) setting in Nvidia Control Panel requires VSync in P3D to be set to ON, at which point P3D will run at 30 fps. You do not need to use the external frame limiter in NCP with this configuration. As far as I know, this is not new to P3D, at least not the 64-bit versions, as I've run with this in both P3Dv4 and all revs of P3Dv5. The FPS chart below is with this exact configuration, and outside of some scenery loading blips, it runs consistently at 30 fps. In all the tests I have run, the most stable frames using adaptive vsync is with the P3D frame limiter set to unlocked.
  14. It has been my current config for a year +. My old 1080Ti card would work by forcing my Dell monitor which runs at 60Hz down to 30Hz. It was the best for smooth frames I have found to-date. My new 3000-series GPU doesn't like running while connected via DisplayPort to a monitor set at a non-supported refresh rate, so the Adaptive is what I have been using. It keeps the frames pretty darn steady at 30 fps in my case.
  15. If you feel your PC and usage of P3D can sustain 60 fps (Vsync at 60Hz), you can have the best of both worlds by leaving your monitor at 120Hz yet force the VSync for P3D only to 60Hz. Here's how: Right-Click on an empty space on your desktop and choose "Nvidia Control Panel" Under "3D Settings" menu, choose "Manage 3D Settings" On the tabs at the right, click on "Program Settings" Select "Prepar3D.exe" from the program list. Scroll down in the box settings box and set "Vertical Sync" to "Adaptive (half refresh rate)". For your 120Hz monitor, this will set the vertical sync rate to 60Hz Click Apply In P3D, set VSync to ON with triple buffering and set the frame limiter to UNLOCKED.
×
×
  • Create New...