-
Forkboy2 started following FYI CTD MSFS 2024
-
FYI CTD MSFS 2024
I was getting weird CTDs when flying into LA area. 100% reproduceable, screen would freeze for 2 seconds and CTD at the exact same location every time. I updated my BIOS and hasn't happened once since then. I tried starting at iniBuilds KLAX 25L, and it won't let me start there. No CTD, but it moves me over to start at 25R for some reason.
-
MSFS 2020 freezes every time over same area of Washington DC
Update your BIOS. I had same issue (crash every time at same location approaching major city). Sim would stutter hard for 1-2 seconds then crash. Updating BIOS fixed it for me and several other people with same issue.
-
Starting apps with MSFS2024
MSFS Addon Linker does this.
- If you have IniBuilds KPSP...
- If you have IniBuilds KPSP...
-
BATC vs. SI Traffic handling.
I have both BATC and SI. They both have a variety of issues with handling of ground traffic.
-
MSFS 2024 - "Fly Now" fails to load
I had same issue, about 75% of the time the sim would fail to start after clicking Fly Now. This is going to sound crazy, but it works 100% of the time for me, and there are others with same findings. First, select your starting position at the airport. Then zoom the map view all the way out until you see the entire Earth. Then click Fly Now.
-
Cloud Shadow casting
Just a guess, but are you waiting a few minutes for the shader files to regenerate? When I've tinkered with shaders, it sometimes takes a good minute or two for everything to return to normal once the sim restarts.
-
All AI Traffic gone in P3DV3
Try enabling Wold folder by editing your scenery.cfg file. Change ACTIVE=FALSE to TRUE and REQUIRED=TRUE C:\ProgramData\Lockheed Martin\Prepar3D v3\scenery.cfg At least that's where I'd start.
-
Limit on entries in aircraft.cfg?
Yes, absolutely. AI textures should be mip-mapped. You can use imagetool.exe to add mip maps to an existing texture and convert it from 32-bit to DXT format. Imagetool is included with the FSX and P3D SDK, which you should be able to find online. Even with plug and play, it's very easy to make mistakes. For example, if you forget to change [fltsim.X] correctly, that aircraft and all others that follow it won't show up. AI Aircraft Editor will find that error and many others with the Validate Aircraft tool. It's free and definitely must-have program for people that manually edit aircraft.cfg files. All errors except atc_airlines undefined must be fixed.
-
Limit on entries in aircraft.cfg?
My understanding of how the textures work is they are only loaded when needed. So if you have 100 textures, FSX/P3D won't load them all initially. It will load them only when the particular livery needs to be displayed. Where you might notice it would be at an airport that is a hub for an airline that has lots of different liveries since then you might be loading 20 different textures instead of just one. Don't forget to validate your aircraft.cfg files with AI Aicraft Editor. If you do any manual editing of these files, 99.9% chance that you've introduced errors, which will prevent liveries from showing. This program will scan your aircraft.cfg files and report all the errors. http://www.owlsnest.eu/tools.php There are many other things you can do to improve performance. - Reduce complexity of AI aircraft MDL files by adjusting/removing LODs with ModelConverterX. This is especially a problem if you have 4K monitor. AI aircraft LODs were designed back in the days when we all had 1280x1024 monitors and become ineffective at 4K. In other words, at 4K, you are pretty much always seeing the most detailed LOD, which is very bad for performance. Note that some AI aircraft model authors forbid you from doing this so check the readme before you modify MDL files. - Make sure all AI textures are no larger than 1024x1024 and all have mip maps. Most can be converted to DXT1, which will make them significantly smaller file size. - Use a one common night texture for every aircraft model (save in main texture folder), instead of one night texture for every livery. Note, depending on model, you may lose tail lights when doing this, but you reduce texture load by 1/2. - Use single engine variant instead of separate model for each engine variant. Obviously only do this if you don't care if correct engine variant is shown. Also, you might see minor texture artifacts on some of the engines.
-
P3d v3.3 issues with blurries?
Here is a very simple trick to help with blurry textures. Change the default zoom level in all your views to be 40%-50%. If you previously had zoom level at 80% or above, you will see an instant and significant improvement.
-
4K TV settings for Windows
Forkboy2 replied to captain420's topic in Video Hardware: Monitors | Multi-Monitors | Video Cards | Drivers etcThe color settings for me were a bit trial and error. Very difficult to find settings that look good for web browsing, etc. and also don't make the clouds in FSX/P3D too bright at night. If you have NVIDIA card and aren't seeing good blacks, you might check out this post. https://www.reddit.com/r/pcgaming/comments/2p3xs7/nvidia_users_using_hdmi_output_youre_most_likely/ And don't forget to check out f.lux to dim brightness at night and DisplayFusion to set up virtual monitors.
-
Video slices as you pan around
I had major issues with screen tearing when I first installed my 4K monitor. Took me a while of fiddling with different settings, but I was eventually able to fix it. Can't remember exact settings that fixed it, but I think it was a combination of switching my monitor from 60 to 30 mhz and increasing max pre-rendered frames in NVIDIA Control Panel so you might give that a try.
-
Help with config and FPS in P3D V3.3
Probably not the answer you want to hear, but you will need to uninstall some of the FTX products if you want higher frame rates. You are expecting too much.
Forkboy2
Members
-
Joined
-
Last visited