downscc

I've seen the app hang or close on splash screen several times. It has always been caused by a problem with an addon. A simple textual error in an add-on.xml file will certainly do this, but also errors in the path or addons not compatible with the P3D version you have. The second clue that it is an addon is that you've recently added something and you never see the creating scenery database progress bar.

I've used it a few times in v4.5.... just not sure if it works in v5. It is easy to use so all you need now is to verify it's compatibility with v5.

It is pretty common to see higher minimums on CAT I charts for conditions that include inoperative ALS/RAIL.

Works fine in my P3Dv5. The Imaginesim configurator should place "ImagineSim_ZSPD1_PD4_Stands.xml' file in the programdata\12bpilot\sode\xml\ folder and a corresponding folder full of mdl files in the sode simobject folder.

In real world, those approach and runway lights are not on during daytime VMC conditions. It is only when the airport goes into IMC conditions (read: low visibility) that those lights are burning during daylight. So what you are saying is ILS requires lighting, and yes when conditions require a precision approach the lights will be on. The simulator platforms have never had this feature, and must be added by the scenery developer. The good news is that SODE has made this very easy for them, all they need to know how to do is to include DL lights in their scenery and the appropriate logic in the SODE XML to control them.

You should be. Airport Design Editor is the gold standard in creating airport bgl files (AF, AFCAD files) because it is really a good piece of software and it is free from scruffyduck software. There is a very active and valuable forum for ADE over in FSDeveloper. The latest version works with P3Dv5 bgl files. Even if you don't want to get into modifying airports, it's handy for opening a default airport and looking at parking and navaids.

Thanks, I had a look at that but note the airports are just AF files designed for default airports that don't match their photorealistic scenery. I'm not interesting in going in that direction, but again, thanks for the referral.

A few scenery developers are starting to use the SODE environmental probe to turn on lights if it is low visibility, or dusk or night. As more and more start doing this it's irrelevant what LM does with P3D.

You are throwing out the baby with the bath water. Don't uninstall it. Simply navigate to the Navigraph programs folder and double click on simlink.exe to get things back to normal. On occasion (it happens about 10% of my long haul flights) that exe process will quit running for whatever reason. Restart it . Simple. No need to close the simulator. All it took was 10 min of troubleshooting to find the problem. I've reported it to Navigraph. Don't need drama.

Often the easiest way is to look at a source like FlightAware and see what they are using out there in the real world. Starting with basics, you look at the charts. I use Navigraph Desktop Charts but there are many ways to do this. Go down the list of SIDS (I usually only look at the RNAV procedures) and I look for one that is appropriate for my departure runway and gets me going in the direction I want to be going. It's that simple. The last waypoint on the procedure might be a GPS waypoint not connected to an airway so from there you use a DIRECT to get to your first enroute fix or airway. Note some places like KSFO will have special SIDS for quiet hours (night). Trying to use the FMS to pick a procedure will always take you much longer and be a frustrating exercise than getting used to using charts. If you don't have a dispatcher working for you, get charts.

That looks like the envshade hack to me... I don't know why it's used by so many.

If you have Orbx So Germany region you need to turn off their AF file, and CVX file is there is one.

I got my private license at SAC (1975)... I've not found anything but if you do please share here.

The NGXu does not use the PMDG_HUD entry anymore in the dll.xml. Rather, their interface module includes the HUD within it along with other functions. It makes sense that you are not loading the HUD if you have a problem in the xml. Don't go down this path, return to your original troubleshooting. You first post above, #1, looks correct so I suspect things like extra white space after the closing ">" or perhaps the required CRLF characters are not there but something has modified the end of line sequence.

Why? You should not change this, because everytime you install an airport scenery that uses SODE it expects those folders to be in that one place and only that place.

You can put addons any place you want. However, you need to understand how your existing addons are discovered by P3D and change the path from the old to new location. Some addons still use the legacy scenery.cfg method, change the path in the section for that addon. Some addons use the autodiscovery method with an add-on.xml file in the P3D addon documents folder, change the path in that xml file. Some addons use the add-on.cfg file in the P3D program data folder, change the path in the section for that addon. It helps to understand how these things work. Very easy to understand information in the Learning Center > SDK > Addons sections.

In most cases I just copies and pasted the folder and add-on.xml files from v4 documents to v5 documents. I also check with developer to see if their was an updated version for v5 and in those cases I would install to v5 only. I also took this opportunity to take advantage of the discovery path method where one entry is made for each developer in the program data add-on.cfg file and those add-on.xml files are placed in each main folder for each product. This method works better than the auto discovery method on my opinion.

You should be using a mesh texture setting of 5 m. And even then, I've seen a few small bumps sticking up at their KIAH and over at FB's KDEN.

I haven't gotten notification of updates from HiFi for last two updates. It's a thing now. If you have to kill the process then most likely you have an addon that uses a dll and that dll is not responding. This results in P3D just sitting there waiting for the other thing to happen, a classic example of AppHang.

You don't give us a clue as to just how long your shutdown is.... I can't guess. Shutdown time depends. In my configuration with tons of addons it can take 40-50 sec., that is normal to me. ASCA spinning/popping clouds... no not normal. Is this with ASP3D? It is the weather engine and not the cloud art (which is just a bunch of graphics) that you should be concerned about. My first thought is you don't have their latest updates for both ASP3D and ASCA that dropped a few days ago.

I kept it simple and when I wanted to change the stop position, or even the location of the instrument, I simply edited the xml file. It is pretty easy to read and figure out. No SDK required. The Placement tool is great if you have multiple adjustments but just one or two are easier done manually.

It was already installed into the Orbx Library, I installed via Orbx Central but Central didn't indicate an update for CYVR so I downloaded the update zip from the FSS forum (I think, I've slept since then). LOL inspite of me checking Central as recently as yesterday, today it announced and update for CYVR. Funny.

The update I received failed to install because I didn't install the scenery to the P3D folders. I figured out how to manually move the bgl and dds files to the appropriate folders. Too bad some developers still haven't read the P3D SDK for addons. I just installed RJBB from technobrain and those dudes are still installing to P3D folders and using the legacy scenery.cfg method!

The downloads page for HiFi is pretty clear in that ASCA is not used if you use EA. It doesn't hurt anything if it is installed but it's just not used. I had a problem after the update to ASP3D 7652 and ASCA 7651 but all I had to do was reboot and all is working as expected with P3Dv5.1.

ditto simfan1983. If you look at the running processes you'll probably note that simlink.exe is not running. When this executable stops running, and it seems to do it 10% of my sessions, Navigraph still has a .dll module attached and that module will cause the application to hang in quick short duration periodic pauses. I've complained to Navigraph but they don't think it is a problem. My solution is to open the program files\navigraph\simlink\ folder and double click on NavigraphSimlink.exe. This will stop the periodic hangs.