avusm575

Hi yvessamuel, To me it sounds like the AI-airplanes are confused because of a missing file or something wrong within the AI-aircraft folders. Try to click on the troublesome planes in AI-Aircraft Editor and see if the AC Folder and AC Status boxes are displayed in green (OK) or red (not OK).

I just wanted to report back that the Airbuses still work with my joystick and throttle quadrant connected, and with RAASPRO activated. But I got another CTD when I changed "atc_model=A318CFM" to "atc_model=A318" in aircraft.cfg. I changed it because I thought it would be a good thing for ATC and SODE VDGS to recognize the aircraft type. I changed it back to the original atc_model=A318CFM and then i did not get CTD.

Hi juaness! I'm on P3Dv4.5 so it's probably not the same brightness / lighting as P3Dv5, but I use a tweak because I think both day and night is too dark in my sim with HDR brightness set to 1.000000. However, if you think the daytime view is not to dark in your sim, then the following tweak is useless to you. I use it to make all my too-dark-views brighter, such as Virtual Cockpit and all the outside views. Let's say I want a brighter VC. Then I open cameras.cfg and find "Title = Virtual Cockpit". At the end of that section, I add this line: LightAmplification=1.25 I guess I then get 25% brighter view both day and night. I also add the LightAmplification=1.25 line in the views section for each addon aircraft in aircraft.cfg if I think the views are too dark. This might work for you, or it might not. If you don't like it, you can try another value better suited for P3Dv5 and your screen, or revert back to the original cameras.cfg / views. Or perhaps it doesn't work at all in P3Dv5? I'm quite happy with my sim lighting now, so I don't want to change a thing. I don't know for sure if moving the HDR brightness slider to the right would produce the same result, as kmax59 suggests. If so, then the tweak is worthless, but I believe I tested this years ago and imagined the tweak to be better.

Hi! I've got P3Dv4.5 and bought the A318-A321 Professional on sale a couple of days ago, but got CTD as well (before I could see the VC). First I temporarily disabled RAASPRO because I've seen someone say that this could work. That didn't help. Then I updated all drivers, still CTD. Then I got a new nVidia driver, but also uninstalled the Airbuses. When reinstalling the Airbuses, this time I followed the Aerosoft advise of temporarily disable the antivirus. I did restart the PC after every step. After the last step I started P3D, but forgot to plug in my joystick and throttle quadrant. But luckily after all of this, I finally got to see the virtual cockpit and got no CTD. Tomorrow the plan is to try to plug in my joystick, then the quadrant and then activate RAASPRO again to see if that works.

Hi Matt, I'm using the RFSL-models in P3Dv4 and presumably the models should work in P3Dv5 too, but I don't know for sure. As far as I know, there are no RFSL PBR-models made. The file RFSL_CRJ200Fv3_B.dds you're mentioning is a bump-texture, not a PBR-texture. The bump-texture is only used by bump models. Regarding texture.cfg, if used, they should always point to a folder or to folders, not a file. And if texture.cfg is in a subfolder you must point it two steps back. Example texture.cfg one step back and you want it to point to CCData: [fltsim] fallback.1=..\CCData or two steps back from a subfolder such as Airline\Registration: [fltsim] fallback.1=..\..\CCData Does your RFSL-models not show at all in the sim or is it some kind of texture trouble? In general, to check if AI-planes are OK, I recommend you get the excellent program AIAE (AI Aircraft Editor), but I don't know if the program checks for missing bump- and PBR-textures. It can be several reasons why AI-planes is not showing in the sim/missing texure(s), such as mdl-name not matching model.cfg, forward slash "/" instead of backslash "\" when pointing to a texture subfolder or [fltsim.x] in aircraft.cfg not beginning with [fltsim.0]. AIAE detects that and repairs the latter.

That's the trick I've used for years. My preferred zoom is 0.7. To get it to work in VC, I have created a shortcut / key assignment in P3D for "View (set to default -1x). After P3D starts up in VC, I press the key and I immediately get zoom 0.7. Then it stays like that until I restart P3D and I have to press the key again.

Before updating, did you open the configurator for EGLL and LEMD and click the "Reset all to default"-button? If not, maybe something did go bad after updating and you should reinstall the airports. After updating you can also try to open Lorby and click "Save" and "Yes" to clear the scenery index to make sure the layer number in the addon.xml files for the airports are okay.

I had both P3D v4.5 (not iFly 737-800) and also the Steam game American Truck Simulator CTD in circa September-October 2023, which I belive was caused by a bad Windows 10 update. The CTD's went away after I recently updated Windows 10 again. I also updated my BIOS, but it may or may not have had anything to do with the CTD's going away.