Rogen

And in v4.5.14 too by the looks of it (the final version release of v4.5). Cheers

If you're interested in the "Fully Loaded Mod package" the process is to PM me 🙂 Cheers

It's a pro vs. con thing and there were more cons to v5 and more pros to v4. I do have it installed though for various testing, and I do like some of the lighting improvements but not much else and I've found it's more trouble than it's worth with what it breaks. I'm hoping v6 is a significant advance on v5, wait and see I guess. Cheers

I wish they were that price in Australia... $2849~$3839 https://www.scorptec.com.au/product/graphics-cards/geforcertx4090?page=1 Cheers

So I've seen this [TERRAIN] section option TEXTURE_SIZE_EXP=10 for some time and have read the setting will improve the LOD radius (via increasing the ground texture resolution x4) for everything apart from PhotoReal according to LM on their forum. I did give it a go back when I had a lowly 1070 Ti GFX card, however with only 8 GB or ram the card would run out of available memory and thus the frame rate would died a sudden death, nor was the card's internal mem transfer rate high enough to transfer around such large textures, so I put it aside in my mind and left it at that. First a few snips of info from the LM website to better understand the function and how it works, please refrence the links for the full threads as there is quite a bit of further relevant info for reading. http://www.prepared3d.com/forum/viewtopic.php?p=172350&sid=58c7154c59fea6ee8f4ce3013d3d9bf7#p172350 Beau Hollis » Mon Dec 18, 2017 2:15 pm If High Resolution Terrain Textures is not checked: (default) Each terrain tile has a 256x256 texture generated. The texture exponent is 8 and cannot be changed. If "High Resolution Terrain Textures" is checked: Each terrain tile has a 512x512 texture generated. The texture exponent is 9 and can be set to 10 using a cfg tweak) This requires 4x the terrain texture memory and loading work as the default resolution setting. If TEXTURE_SIZE_EXP=10 and "High Resolution Terrain Textures" is checked: Each terrain tile has a 1024x1024 texture generated. This requires 16x the terrain texture memory and loading work. The load time and GPU memory requirements at this level are extreme and only a very small subset of GPUs can handle it today. We opted not to make available via the UI. We left the exponent tweak in so that power users could override the exponent used for "High Resolution" mode, while still being able to disable it via the UI. https://www.prepar3d.com/forum/viewtopic.php?p=166316&sid=a3a231e10c898e4019e88048d2ff680b#p166316 Beau Hollis » Thu Sep 07, 2017 11:54 am There is a known limitation of this setting currently, which is that photo-real (PR) textures are not improved because the PR source textures are at a fixed resolution and are already assigned to a specific LOD when they are build into the scenery. The snip above about the Photo-Real not being improved kind of put myself off using it as it felt like a half measure and in anycase not having enough memory meant I couldn't perform any valid testing anyway. Enter the new series 3000 GFX cards with their larger installed memory bases and huge internal mem transfer rates means such use may now be a viable option, and now that I do actually have a 3080Ti with 12 GB of memory I though would give it a trial again. So does setting TEXTURE_SIZE_EXP to 10 make a difference ? Indeed it does, where for starters graphics card mem use typicaly doubles in any given situation and I've been able to fly in situations where practically all of my 12 GB of ram has been utilised. As for sharpness, yes that too is improved, and there is a lot less terrain texture popping, as in a lot less of those blurry triangles of ground textures that don't pop into sharpness until you're practically over top of them. Although I didn't notice much difference to general ground textures themselves where non-photo-real was in use, photo-real did benefit greatly which I was surprised about given LM's statement. For myself it's a thumbs up, I get improved ground textures and more use out of my GFX card, and do note a restart of P3D is required when changing the setting. I wouldn't try it if I didn't have a 3080Ti at least, additionally I'm running P3D v4.5 with DX11, so v5.3 users may have a different experience with v5's DX12 implementation. My conclusion is using the setting of 10 was entirely impractical prior to the release of these advanced GFX cards, unless you had a Titan or something else very high end, but has certainly proved a useful setting now that these advaced GFX cards are more mainstream. Cheers Pic of very high memory utilisation: Pic of TEXTURE_SIZE_EXP=9 Pic of TEXTURE_SIZE_EXP=10, check the background mountain details. The comparision was created by taking the first pic at 9 and saving the scenario, shutting the sim down and swapping to 10, restarting and loading the same scenario point. General flying using PR with the 10 setting.

Hi @ggerolamo, So you know the process... Cheers

Hi @gperticara @whamil77 hasn't visited AVSIM since July 12, 2022. When he did pop in it was only for a few posts, from what was mentioned health probs were the issue, really don't know anything more unfortunately. But if you take alook at the post/thread below 🙂 Cheers

I believe you've already PM'd me 🙂 Cheers

If you're looking for performance with the most FSX compatibility regarding running FSX addons, then P3D v3 would likely be your best bet. P3D v3 is 32 bit and will by virtue therefore run the majority of FSX 32 bit addons. There is the issue of getting addons installed in P3D given most FSX apps are looking for FSX named folders, but you can typically work around that by pointing the FSX registry key paths to P3D paths and also drop a copy of the FSX.exe into the root of P3D as there are the occasional addons looking for not only the path, but also confirming the executable exists. You could also use junction point/s to map the FSX path to the P3D path. e.g mklink /J "FSX root path\FSX" "P3D root path\Prepar3D v3" Personally I did run both FSX-SE and P3Dv3 for a time, however then moved to P3D v4.5 as the majority of planes I owned started arriving with 64 bit counterparts. Additionally v4.5 being 64 bit has no out of memory issues like that of the 32 bit FSX-SE and P3D v3 and I certainly don't miss the OOMs and the planning and effort to workaround. The few planes I could not migrate due to no x64 version being available, well... such is life and although a con, having no OOMs is a huge pro. Cheers

If you're looking for performance with the most FSX compatibility regarding running FSX addons, then P3D v3 would likely be your best bet. P3D v3 is 32 bit and will by virtue therefore run the majority of FSX 32 bit addons. There is the issue of getting addons installed in P3D given most FSX apps are looking for FSX named folders, but you can typically work around that by pointing the FSX registry key paths to P3D paths and also drop a copy of the FSX.exe into the root of P3D as there are the occasional addons looking for not only the path, but also confirming the executable exists. You could also use junction point/s to map the FSX path to the P3D path. e.g mklink /J "FSX root path\FSX" "P3D root path\Prepar3D v3" Personally I did run both FSX-SE and P3Dv3 for a time, however then moved to P3D v4.5 as the majority of planes I owned started arriving with 64 bit counterparts. Additionally v4.5 being 64 bit has no out of memory issues like that of the 32 bit FSX-SE and P3D v3 and I certainly don't miss the OOMs and the planning and effort to workaround. The few planes I could not migrate due to no x64 version being available, well... such is life and although a con, having no OOMs is a huge pro. Cheers

Hey @newtie , Have you not downloaded the fully loaded pack ? It does include everything and more including 4 different preconfigured panel.cfgs and a panel.cfg.Readme.txt describing them and how to edit. Cheers

Commenting out the panel.cfg lines is all it takes. For instance: For the Avidyne Popup gauge lines are assigned to keyboard number buttons where "Window00" refers to key number 1. [Window Titles] Window00=EX500 When reading down the panel.cfg we come across the "[Window00]" entry lines where you would basically comment out the gauge lines with // The lines are enabled in the below sample. //-------------------------------------------------------- // EX500 [Window00] Background_color = 1,1,0 size_mm = 851,571 //position = 8 visible = 0 ident = 0 no_luminous = 1 window_size = 0.369, 0.440 window_pos = 0.000, 0.450 gauge00=EX500_PC12!EX500_config, 0,0, 1, 1 gauge01=EX500_PC12!EX500, 0,0,851,571 gauge02=PC12CAR!ToggleCARG500, 100,0,760, 60 //-------------------------------------------------------- That takes care of the popup where if you then search the remaining panel.cfg text for "EX500_PC12" you'll find the rest of the lines. //-------------------------------------------------------- [Vcockpit04] Background_color=0,0,0 size_mm=513,512 visible=0 pixel_size=513,512 texture=$Panel_4 //gauge00=EX500_PC12!EX500_config, 0, 0, 1, 1 //gauge01=EX500_PC12!EX500_3D, 0, 0, 513,409 //gauge02=EX500_PC12!EX500_Update, 0, 0, 1, 1 //gauge03=PC12CAR!ToggleCARG500, 0, 0, 513, 32 // Embed the Roland Weather Radar fully into the EX500 GPS bezel. Also note the Roland Weather Radar requires Active Sky Next (ASN). // As the Roland Weather Radar is embedded there are click spots within the display mouse scroll wheel functionality to control On/Off. Tilt, Range and Gain. // The spots are left of the centerline. // Note the EX500 is still available as a popup. gauge00=PC12CAR!ToggleCARG500, 0, 0, 513, 32 gauge01=RolASNRadar!ORadGauge, 71, 57, 372,262, sweep|beam|icing|nogps|starton //-------------------------------------------------------- In this instance they are commented out as the Roland Weather Radar is used instead, although if the popup [Window00] lines are left uncommented the Avidyne would still be available as a popup. When looking at the gauge lines the "EX500_PC12" part is refering to the cab or directory of the gauge, the next part "EX500_config" refers to the actual xml gauge itself within the cab or directory. gauge00=EX500_PC12!EX500_config Once edited and saved you'll need to reload the plane to see changes, I have a key combo assigned to perform the reload. Hope the above helps. Cheers

Hi @Daniel Baker You could try enabling P3D logging and then check the log post freeze and see if it holds any clues. Or the windwos event log might have some info. P3D logging will be located in \Documents\Prepar3D v[version number] Files\ ContentErrors.txt is the one I concentrate on as as most issues tend to be related to some form of content. Also as a first step to any troubleshooting I delete the scenery index files and compiled shader files. Both will be automatically regenerated on P3D restart. Shader files can build up to many thousands and I've found a clean slate goes a long way to clearing up any latent issues. Cheers

Hi @brucewtb How do the look of these clouds compare ? Cheers

Hi @Choman, Not seeing such limitation here, both on the ground and in the air the rudder deflection is to the limit of the elevator cutouts. P3D v4.5 here and the ATR42 is v1.4. YD off, minimal deadzone in rudder axis, I'd check rudder axis and sensitivity as a first step. Pic taken today showing rudder max travel.

Hey @Lorby_SI, I gotta say thanks for this update. It makes using the tool sooo... very much nicer 🙂 Just one thing though. The Window doesn't seem to follow any of the standard Windows snap options. e.g. Draging the window to the left or right screen edge and top or bottom corner snaps do nothing. Nore do the snap key combos work. e.g. Windows key + left arrow/right + top/bottom arrow Cheers

Working buttons and knob in the VC Cheers

Screen DPI settings perhaps, are they set to more than 100% ? If so try setting lower (in Windows Display settings). Cheers

Yes there are selected aircraft listed in Orbx Central as available for purchase including ones I don't have. The above said clicking on Central's link to Orbx Direct returns a 404 page not found as does clicking on the Add to Cart link. So unless you've already got them, or they've done a deal and sold their back catalogue to LM, it's a plumb out of luck no deal. Seems a bit wierd really, I mean I can understand no further development of the existing range given they are finalised releases and have been for some time. And it's not as though their forum is blowing up with install issues, so really they could just leave them sitting as a back catalogue available to those who want them. They came across as a strange bunch and never inspired much confidence with myself which was why I was always hesitent to purchase their products, their cost verses reputation and confidence were not in equalibrium, as opposed to say A2A. I do find it surprising that people are infact offering to purchase and they are uninterested in taking money, even if the volume is low they could still take the money and provide a download link for virtually no effort. Anyway I'm glad I managed to purchase what I did during their flash sale, I would have liked to grab a couple more and did try to just after New Year but that ship had sailed by then (missed out by just days). Cheers

Thanks folks, I enjoyed flying in and out of these Nepal airports so much I decided to get back into the Aerosoft Twotter. Hadn't really flown since FSX days but after a tuneup of bug fixing and adding an icing gauge and matched lua scripting to iceup the control surfaces and also account for freezing rain, it's quite the different aircraft compared to the memory of FSX days and ideal for these STOL Nepal airports. Cheers

A bottle ??? A nappy ??? A catheter ??? Or Otto ?

Decided to take the PC12 out and up to height, 28,000 in this instance and where else but some nice high mountainous area like the top of the world. Approaching VNLK after having dropped height and still dropping speed. I's a tiny little landing strip, no go around here. And on the ground (with a thump - need more practice...). Nice panoramic shot coming into the parking area. There's always cats.. or dogs 🙂 Hard to believe the original airport as compared to that of today (pic taken in 1977 - credit Cliff Bancroft). And another from 1964 (credit Jim Fisher). In the air again, this time heading towards Everest. Everest It's really like a wasteland - a desert of cold. Heading over the other side dropping height for VNPL Phaplu airport. Looking for the airport, the GTN750 failed somewhere after Everest. It's software froze and I had to rely on the secondary GNS530 GPS to find the airport. and on the ground @ VNPL Phaplu, another "thumping" landing... Interesting airport, I suppose they are all pretty much the same style in the area. That's all folks. Cheers

As a mechanic myself, when you're positioned elbow deep and potentially upside down in the guts of a car, truck, plane, <insert named motor vehicle> etc. getting out of position to grab a tool in probably limited space is not at all efficient or at times even easy. And that's where I have an apprentice sharing the workload in passing the required tools and provisioning assistance and operations as I need them. And at one time I was incapacitated by 100,000 volts of spark energy and unable to move, and that's where my assistant cut the power, so there is the safety aspect as well. And in my other carreer as a software and support engineer, I can say software based automation is not risk free, nore is it at times even safe. There is always a spot for two people even if only to learn the ropes so to speak. Cheers

And for reference I've detailed the nuances here. The "Turbine Duke V2 P3D 4 Config" app will overwrite the panel config GTN entries replacing the rxp with the F1 entries each time a save (in the app) is performed. Therefore I've added additional commented entries to the panel.cfg so I can easily copy/paste manually if I choose to modify the config via the "Turbine Duke V2 P3D 4 Config" app (see panel.cfg spolier for the snips). Besides choosing the VC no bezel option, be sure matching GTNs are chosen for the popup and VC as it's easy to accidently select a 725 and then wonder why the popup and VC are acting independantly. With the GTNs installed , popup the GTN, with the cursor positioned on the top edge of the popup's bezel, hold down Shift and Right Click the mouse, this will open the GTN config window where various options can be set. If using the F1 bezel mapping gauge be sure to set the option of "Advanced Settings/Use simulator GPS Commands" as enabled. To install the mapping gauge (gauge in spoiler), extract the "RASDuke.CAB" to a folder of the same name within the same location, (it's in the Panel folder), then rename the CAB file to something like "RASDuke.CAB.orig". 7Zip is a good archive tool for CAB extraction. Copy/Paste the F1VC.xml spolier text into a text file named "F1VC.xml" (Notepad++ is ideal for this), be sure windows file extention visiblity is enabled, else the file name may end up named "F1VC.xml.txt" with the .txt not shown by Windows. I've added additional commenting to the F1VC script to better describe it's operation and note the F1 bezel buttons buttons will require double clicking to work but the knobs will be just fine. Copy the new "F1VC.xml" gauge file into the previously extracted "RASDuke" folder. Add the following line to the panel.cfg under [VCockpit01] being sure to add to the end of the [VCockpit01] gauges list. gauge27=RASDuke!F1VC, 0, 0, 1, 1 // Bridges the controls from the F1 GTN750 to the RXP GTN750. I then recab the RASDuke folder using the p3D SDK tools, but it's not neccesary to do so really. There are other ways to install and configure for using the F1VC.xml, this is simply the method I use to keep everything neat. Cheers F1VC.xml Panel.cfg snips

Hi @brucewtb Ah yes there is really nothing quite like RealAir aircraft, all of them are great to fly and very detailed both in looks and functionality. Pity about Sean's & Robert's breakup and then the passing of Sean's spouse sealed the end to further flightsim development. Do you have more than just the Duke Turbine ? Anyway... The RXP installer creates a menu item in the P3D menu for adding units as a popup or embeding in place of an existing F1 unit. So really it's no effort to install, just be sure to choose the no bezel option. You can also manually add if you're comfortable with editing panel.cfg. The only thing is the dials & buttons of the F1 bezel don't work although there is a gauge script that provides the function of mapping. Cheers