johncott

According to the Prepar3d forums Nvidia is aware of this and the fixed was supposed to be in their next Game Ready Driver version 610.47. Tried the new driver and it reset the Prepar3d profile and had to use the profile inspector to change it again to get the effects to work. Looks like a permanent fix is on the way though.

I just loaded P3dV5 with the latest 595.97 driver with a 5070TI GPU and was able to enable and disable the HDR Lighting and the setting does change the lighting in the sim. I do not use the RTX Dynamic Vibrance option that you mentioned. What does it do? Still do not have the effects like fireworks, chimney smoke, water fountains, etc.

I cleared my cookies for AVSIM and I stopped getting the Bad Request errors. John C.

If you decided to install ORBX vector, search for this in the library "Global_default_Vector_Removal". It's a fix that will greatly improve the performance of ORBX Vector in P3DV5 and V6. John C.

simHeaven X-World pay ware looks interesting but will have to get rid of the very large buildings artifacts that show up as a result of the footprints scenery before I will pay for it. These artifacts also are present in Bing Maps. To see what I mean, with X-World North America loaded take off from RW 13 CYRM Rocky Mountain House, Alberta and you will see what I'm talking about. They are quite numerous throughout western Canada and the USA. The automatic algorithm used to make the footprints data needs some work. I have manually removed them from Canada and some parts of the Northern USA, but it is a lot of time-consuming work. I did email simHeaven a few months ago about it and they did mention there would be and upgrade in late 2025 or early 2026. If simHeaven is counting on third party data for the Footprints sections of their scenery, this building artifacts issue will probably still exist unless the footprints scenery is manually modified. John C.

There are various issues with the aircraft lights and effects in P3DV5 and V6. The new NVidia 50XX series of cards have issues with various effects in P3DV5 and V6. They worked ok in P3DV4. There are known issues with aircraft lighting in P3DV5. They changed something in V5 and this affected the aircraft lights showing up on the ground and objects. Two people can have the same aircraft, and the lights will perform differently. Sometimes the lights will not show up on ground but will show up ok on the aircraft other times they will show up on the ground and not on the aircraft. Do an internet search and you will find a lot of posts regarding this subject/ Two recommendations: Make sure in Options-Lighting that Dynamic Lighting is enabled. If the landing lights are dim or not showing up on the ground and nearby buildings and Dynamic Light is enabled, you can modify the fx_landing.fx effect in the effects folder. Use a test editor and change the "Falloff Exponent=2.00" to " Falloff Exponent=1.25". Please be aware, not every aircraft uses the default landing light effect. John C.

Did you confirm that the effects folder that came with the Ryan Navion B download is installed correctly? The contents of this folder should contain 25 fx_XXXXXXX.fx files including the files I mentioned in the previous comment and one texture folder. The 25 fx_XXXXXXX.fx files go in your main effects folder and the *.BMP files in the texture folder go in your texture folder in your main effects folder or you can just drag the effects folder from the Ryan Navion B download into your main P3DV5 folder and answer yes to overwrite any files. For the issue you're having, the two things I mentioned should be the only fixes you need to get the Ryan Navion lights working. Some other planes will need the landing_lights FX files modified. I got your P.M. and will respond when I get a chance. John C.

I would suggest you double check these two items first: Make sure Dynamic Lighting is enabled in P3DV5.4. This is all I had to do to get the lights working for the Ryan B Navion. The Ryan B Navion is one of the few planes that worked ok once dynamic lighting was enabled. Make sure the following files are in the P3DV5.4 main "effects" folder. fx_LDRNavion_landing_lg.fx fx_LDRvclight.fx fx_LDRnavred.fx fx_LDRnavgre.fx fx_LDRstrobeL.fx fx_LDRstrobeR.fx fx_LDRbeacon.fx fx_LDRNavionTaxiLight.fx There is an aircraft lighting issue in P3DV5 and for the majority of the aircraft in P3DV5 I had to modify the default "fx_landing.fx" effect and change the "Lights" section of the "aircraft.cfg" to use my modified landing light. AS mentioned, the Ryan B Navion is not one of these. Also, if you have issues with the sounds for the Ryan B Navion I do have a fix for it and can email it to you. John C.

The missing effects was just an issue with the Nvidia 50XX series cards. The 30XX and 40XX series far as I know had no issues.

Did you delete and rename the Prepar3D.cfg file C:\Users\yourname\AppData\Roaming\Lockheed Martin\Prepar3D v5 and let P3DV5 rebuilt it? In the C:\ProgramData\Lockheed Martin\Prepar3D v5 there is an effects.cfg file, you can check to see if this file is there. Other than this I'm running out of ideas.

Did you check to see if your effects folder is in the main P3DV5 folder? If it's missing, maybe it got accidently move by an unintentional drag and drop. If it's missing, you can do a search for it and put it back in the proper location or you can do a search for some of the lighting effects files for the Ryan B Navion to see if you have them and where they are located. Here is a list of the lighting effects files to look for: fx_LDRNavion_landing_lg.fx fx_LDRvclight.fx fx_LDRnavred.fx fx_LDRnavgre.fx fx_LDRstrobeL.fx fx_LDRstrobeR.fx fx_LDRbeacon.fx fx_LDRNavionTaxiLight.fx If the effects folder is where it's supposed to be and the files are in that folder, I'm not sure where to go from here without a full install. Since every plane and add-on could install effects to the effect folder you many have to install everything. Please note that there are issues with the aircraft lighting in P3DV5.3 and 5.4 and what works for one aircraft will not work for the next one as dave2013 mentioned. John C.

This looks like an effects folder issue. I wonder if its corrupted or got moved or renamed by mistake. For the Ryan B Navion the light bulbs are part of the model but the effects and how they show up on the runway are effects that are stored in the effects folder. You can check in your main P3D folder if there is an effects folder and that the files are there.

Did you check the to see if the Dynamic lighting option is enabled as I mentioned in my previous post. Under lighting, turn on Dynamic lighting if it's not on and see if that fixes the issue. For the Ryan B Navion by turning the Dynamic lighting option on and off, I could toggle the landing light splash showing up on the runway. John C.

I have the RYAN Navion B and it works ok without any mods, one of the few planes that the lights work ok for me without some tinkering. This may be a setting. In options, under lighting, turn on Dynamic lighting if it's not on and see if that fixes the issue. Also check out the links below for more info on this issue. https://www.prepar3d.com/forum/viewtopic.php?t=142654 https://www.prepar3d.com/forum/viewtopic.php?t=144113 John C.

I might have another solution for your problem. Which plane is this? I can look into it tomorrow. Unfortunately I’m using 5.4 as well and have a lot of issues with aircraft landing lights and interior lights I think some are cause by the 50xx card and some are issues with 5.4. I have modified some fx files to fix the problems I was having. I was hoping the 50xx problem would be solved by now, but looks like they’re playing the blame game now. John C.

If you're using a Nvidia 50XX series card there is a bug with the effects for P3DV5 and P3DV6. Not sure if the landing lights are part of the problem. I do know most of the landing lights for my 100 plus planes worked find with my 2070 card and most stopped working with my 5070 card. Also, a lot of interior lights have issues. This 50XX bug also includes the effects like the Las Vegas fireworks, smoke from stacks, red tower lights, etc. LM and NVidia are aware of the issue. Here is a link to the issue on the P3D forums regarding this issue. It was just updated on October 10. RTX5090 GPU - Prepar3D Forums John C.

I fly a lot in the Canadian North and also use FreeMeshX and find the best visual experience is using ORBX Vector, FreeMeshX and ORBX Global landclass for this area of the world. With the default mesh and default vector data there are lakes and rivers either sticking out of the ground or sunken into the ground. This works best for me and depends on the flying you're doing. John C.

I've had very good luck with P3D 5.4 and works well. I cannot compare to 4.5 because I moved from FSX to P3DV5. The only add-on that did not work well was ORBX vector. If you have ORBX Vector I have created a fix for this product and is available in the AVSIM library. If you already own P3DV5 and have downloaded various versions, then you can compare 5.3 and 5.4 to see what works better as per Ray Proudfoot's comment. If you going to purchase P3DV5, I'm not sure if you can download the 5.3 version. I only see the 5.4 version available. The only other issue with both P3DV5 and V6 is the special effects do not work with the NVIDIA 50xx cards. these special effects are things like fireworks, smoke, fountains, Niagara Falls, etc. It may also affect aircraft lighting as well like landing lights. According to LM this is being worked on by NVIDIA with no specific time frame for a solution. John C.

First of all I do not use MSFS 2020 very often, not sure how this will work. I do use P3DV5 and the best program for resizing P3DV5 DDS textures is the freeware Paint.net program. I did try one image from the MSFS 2020 default Cessna and it seem to work. Backup your original image just in case something goes wrong. Load the image in Paint.net, resize and save. I save the new file as a BC3 (Linear, DXT5) file. Let us know how it works. John C.

Here is a link to a post regarding this subject from last month. Hope this helps. John C.

I have not worked with MSFS 2020/2024 files and I'm not sure what the purpose of the json extensions files are in the MSFS 2020/2024 texture folders. To edit and resize DDS texture files, paint.net may be your answer. it's free, opens DDS files and has a resize feature. You may have to experiment with the save feature a bit to see which format works best. John C.

I do not have MSFS2024 but have MSFS2020. Could never really get into it. My first flight I tried with 2020 was from Jasper, AB (CYJA) to Hinton-Entrance, AB (CEE4). I followed the Athabasca River all the way. First problem, the river kept popping out of ground. Second problem, even though it was July, the Hinton-Entrance airport was covered in snow. My second flight, a week later decided to check out the Casey Emergency Airstrip in Quebec. Didn't expect this abandon strip to be in MSFS 2020 but wanted to see how it was rendered from the scenery engine MSFS2020 uses. I decided I would take-off from the nearest airstrip, Weymontachie, Quebec (CSU5). Could not take off because my plane was sitting on the roof of a large building that covers the whole airfield. Did try taking off from the next nearest airport, Parent (CYPP) and is all fairness, the Casey Emergency Airstrip was well rendered by the MSFS 2020 scenery engine, and I could land there. I do a lot of flying in the Canadian north and have check various parts in MSFS 2020 included northern parts of the western provinces and the three territories and the scenery varies from good to poor in a lot of areas because of poor satellite imagery. The main issue is with too many trees and all the same height, in real life the trees and not that tall in the Canadian north, but MSFS 2020 seems to have issues with tree height and way too many of them. The second issue in the Canadian North is MSFS 2020 has issues with water bodies and in some locations the MSFS scenery engine cannot distinguish whether there is water, snow or trees. I've seen the same waterbody have trees, snow and water. Do not know it 2024 is any better in the Canadian North. My other reasons for sticking with P3DV5 is the seasons and the default ATC works fairly well. In the winter I look out my window and there's snow on the ground, I take off from my local airport, there's snow on the ground. the other sims don't have that as a default feature. I will stick with P3DV5 for the foreseeable future. John C.

The 32 bit version is for all FSX and P3D versions, 32 and 64 bit versions. The 64 bit version is for X-Plane and MSFS. LittleNavMap runs independently of P3DV5 and it shouldn’t matter if it’s 32 or 64 bit. For example, I could use a 32 bit paint program to create a new set of textures for P3DV5, and It wouldn’t matter to P3Dv5. John C.

"What's New" works ok in the "Avsim Library" menu as well as the "Latest library Additions". In the "Hot Spots" section on the right side of the main startup page, the "File Library - What's New" link still gives me a 404 error. Logged out, cleared my cookies, logged back in and still having the issue. John C.

Thank you. The "Latest library Additions" now works good in the "AVSIM Library" drop down at the top of the page. The "File Library - What's New" in the "Hot Spots" section still has a 404 error. Can this please be fixed as well? John C.