RRVyper

Check your compatibility settings for TrackIR. Ensure 'Disable fullscreen optimizations' and 'Run this program as an administrator' are checked. Also, make sure the simconnect.manifest and simconnectSP2.manifest files in the TrackIR folder are not disabled. Randy

Although I have ASP3Dv6, I thought I would see if the free P3DWX program would work. The installation instructions had to be modified but it seems to be injecting live weather into the sim. Even historic weather seems to be working! The steps I took (after extracting the client files into their own folder) were renaming the original wxmapping.bin and replacing it with the (separately) downloaded version. The wxstationlist.bin was not located in %appdata$\Lockheed Martin\Prepar3D v6. I found it in the P3D_Root_Folder\Weather folder but P3D will ctd if you rename it so I left it alone. I also did not make any of the edits to Prepar3D.cfg, just left my current cloud settings that I have been using with AS. Might be of interest to someone who just wants to inject live weather into P3D. 😄 Randy

This is nothing more than a cash grab from loyal CP users. As Ray mentioned, the camera api appears unchanged and it would be a trivial task to add P3Dv6 support to the previous version. I’m sure people would be ok with a nominal upgrade fee in that case. As it is, in order to use their previous camera sets, which they have spent alot of time setting up, they are asked to pay the ridiculous “upgrade” fee for a program they can’t even use in older sim versions. What a grift! If I didn’t know better I would suspect this was a product meant for MSFS which was quickly modified to support P3Dv6 since MS/Asobo have no plans to open up the camera system in MSFS. Why else would a “Professional” version appear almost overnight? But I know better than to suspect that. Right? Randy

Hi Allan, I had to boot into safe mode to rename the Prepar3D v5 folder as it was 'in use' when I first tried, possibly due to me running a program beforehand. I haven't tried making a camera set for P3Dv6 since I already have the cameras made from P3Dv5 and they all worked. Once I had it working, after all the edits in the previous post, I reset them back to their original names, after deleting the 3 symlinks pointing to the corresponding P3Dv6 folders. I could then use EZCA in both sims without re-doing the renames and symlinks. Just confirm that there is an entry in the exe.xml file that auto-starts EZCA 3.1. Note that Chaseplane and EZCA will not work together. If you run the installer before doing the renaming and symlink creation, it will override Chaseplane, and vice versa if you run the Chaseplane install. At least that's what I remember when I was using Chaseplane. I think I'm remembering everything. I'm not at my PC right now. Sorry for the delay. I just got the notification email. Randy

All the wonderful Canadian airports (runways and aprons) from Ralph Eisenegger, the developer of Simaddons, are sloped, but there are issues with the sloped aprons in P3Dv6. 🙁 Randy

I think the reason for this was that when I switched back to EZCA v3.2.0.3 I forgot to redo the Windows 11 patch released by EZdok on 08 Apr, 2023. Seems to connect reliably now. 😃 Randy

I tried Chaseplane but was so used to EZCA that I went back to it and I guess really didn't give CP enough of a chance to win me over. I do think EZCA was a better program, though. It was easy to get EZCA to work with MJC and I think there was another solvable issue with the Aerosoft Airbus iirc, but never had any Milviz planes (I don't think there was a workaround for those). There were also Simconnect issues when people began switching to Windows 11. The devs have been absent from their forum for a long time now which is unfortunate. But there must be someone still working behind the scenes as there was a recent update for P3Dv5.4 and Active Sky. I'm cautiously hopeful. Randy

So, as expected, EZCA is working due to referencing P3Dv5. The cameras loaded fine from the EZCA database since they were already made in P3Dv5 and the aircraft name matched (same aircraft in P3Dv5. A bit of trickery was required. Note that the steps below will effectively disable P3Dv5 and could cause problems if you attempt to start P3Dv5 (or update/run any programs that reference P3Dv5). If you aren't comfortable doing this, or don't understand exactly what you are doing, I would suggest waiting until the dev (hopefully) updates the program. It should be fairly straightforward for them. Don't hold me responsible if you corrupt your P3D installations. This probably requires P3Dv5 to already be installed, although you could probably create relevant symbolic links to install EZCA if you don't already have it, but it may require a registry edit which I did not do. Also, EZCA will show a red lock for the World Camera since it is communicating with the wrong sim version. I'm not sure if anything else won't work. If you use the same aircraft in P3Dv6 that are in P3Dv5 you may get away with just using EZCA as is. Any camera sets previously created in P3Dv5 will be used by EZCA running in P3Dv6. However, installing new aircraft into P3Dv6 only may work. The steps below should solve that. Here's what I did - I strongly suggest reading the entire process before attempting it: First, I went into Safe Mode and renamed the P3Dv5 folders that EZCA uses: Prepar3D v5 (main folder) --> Prepar3D v5.off Documents\Prepar3D v5 Add-ons --> Prepar3D v5 Add-ons.off AppData\Roaming\Lockheed Martin\Prepar3D v5 --> Prepar3D v5.off ProgramData\Lockheed Martin\Prepar3D v5 --> Prepar3D v5.off I then booted back into Windows (11) and created symbolic links (i.e. a shortcut) for those renamed folders to point to their P3Dv6 counterparts. I use a program called Link Shell Extension for this. It can be found here. Create symbolic link called Prepar3D v5 in the same folder where the main Prepar3D v5 folder was (which is now called Prepar3D v5.off) and point it to your main Prepar3d v6 folder (link source) Create symbolic link Prepar3D v5 Add-ons in your Documents folder which points to Prepar3D v6 Add-ons Create symbolic link Prepar3D v5 in the AppData\Lockheed Martin folder which points to AppData\Lockheed Martin\Prepar3D v6 Create symbolic link Prepar3D v5 in the ProgramData\Lockheed Martin folder which points to ProgramData\Lockheed Martin\Prepar3D v6 Run the v5 EZCA Config Tool and select 'Prepar3D V5' and it will make the changes to the necessary Prepar3D v6 files (aircraft.cfg/Standard.xml/cameras.cfg) depending on what the Config Tool finds. Run the Config Tool again and select 'For advanced users' and re-select Simconnect 10.0.61259.0. Note that you may have to reselect Simconnect 10.0.61259.0 if EZCA has problems connecting to the sim - I have had to more often than not. 🤬 Another caveat - if you are using addons that still reside in the Prepar3D v5 Add-ons folder, this folder now points to the Prepar3D v6 Add-ons folder so P3Dv6 won't see them. The easiest way to solve this (in most cases) is to create a symbolic link in the Prepar3D v6 Add-ons folder to the desired add-on in the previously renamed Prepar3D v5 Add-ons.off folder. For example, I have an A2A folder in the (now) Documents\Prepar3D v5 Add-ons.off folder so I created a symbolic link in Documents\Prepar3D v6 Add-ons called A2A pointing to Documents\Prepar3D v5 Add-ons.off\A2A. I said 'most cases'.... In the case of FSUIPC6 which, in my case, is installed in (what used to be called) Documents\Prepar3D v5 Add-ons, there is an add-on.xml file in the Prepar3D v6 Add-ons\FSUIPC6 folder pointing to Documents\Prepar3D v5 Add-ons\FSUIPC6\FSUIPC6.dll. This will not find FSUIPC6.dll because we renamed the Prepar3D v5 Add-ons folder and created a new link to the Prepar3D v6 Add-ons folder. To correct this (and any like it) you need to edit the add-on.xml file in the Prepar3D v6 Add-ons\FSUIPC folder and change the </Category><Path> entry to point to the Prepar3D v5 Add-ons.off folder. Make this change in the add-on.xml file located in the Documents\Prepar3d v5 Add-ons.off\FSUIPC6 folder as well. Note: if your setup differs from mine you will have to adjust as necessary. That should do it. For those without P3Dv5 installed, it may be only necessary to create the symlinks above. Also, if P3Dv5 is not installed, FSUIPC6 should be able to be installed directly into P3Dv6. In this case do that before creating symlinks. I cannot stress enough that you can easily hose your Prepar3D v5/6 installations by making mistakes when attempting this but if you are comfortable with fixing any issues you may run into and remember not to use P3Dv5 while these edits are active, feel free to attempt it - No guarantees that these steps take into account all required changes and I could easily be forgetting/overlooking something important which could have dire repercussions. You have been warned. Randy

Hi @AllanK I wouldn't pull the trigger just yet unless you have P3Dv5 installed. I didn't test any further last night and thinking about it later I suspect it may still be using P3Dv5 files even though it is connected to P3Dv6. There might be ways around it using symlinks, etc. until a fully compatible version is released by the dev. I need to test further today. As for the earlier versions, see also this page. Randy

I'm not sure if anyone else has had success using EZCA with P3Dv6 but it initially wasn't working for me. I hadn't used P3D (v5.3) in a few months and decided to fire it up and make sure EZCA was working there as it can be very fussy with Simconnect. Turns out it wasn't working for me in P3Dv5.3 either. I remembered that I saw updates for v3.2.0.4 on the News | ezdok-camera.com website and had it installed (along with the small patch on the same page) thinking I was going to update to P3Dv5.4. I downloaded 5.4 but didn't install it. So, tonight when it wasn't working in P3Dv5.3 I ran the old installer (EZCA V3.2.0.3.exe) but still no joy. I ran the config tool twice (once for the actual config tool and next the 'Advanced Users' and selected Simconnect 10.0.61259.0. Then I fired up P3Dv6 and EZCA connected to P3D. Note that when I switched to Simconnect 10.0.61259.0 when I went back into the config tool the 11.0.61259.0 entry at the bottom was still highlighted. Not sure why or if it means anything. I haven't tried importing cameras or saving them - just wanted to get this 'discovery' out for others with EZCA since Chaseplane seems to have given up on P3D. Now, back to testing... Randy

That statement is laughable. Did you even read the FS Community survey that Navigraph conducted? Most simmers use more than one platform, and the serious study-level oriented ones will not switch fully to MSFS until their favorite aircraft are ported over. Right now, MSFS is good (not great) for GA flying but needs to mature before "99.9%" fully drop FSX/P3D. And I hope that by your saying you're stopping development on your legacy products does not mean you've stopped supporting them for your paid customers, ensuring they continue to work as long as LM continues to update P3Dv5. FSX/P3D are far from dead.

Or they made a deal with PMDG. 😉

Just to follow, the wind direction issue is not confined to FSGRW. https://forums.hifisimtech.com/threads/wind-heading-not-aligned-between-asp3d-and-p3dv5.12546/ Randy

Hopefully LM can find a cure. 😅

Interesting. For me, the wind direction is basically 180 deg from what FSGRW says (give or take magvar). I wonder if it has anything to do with the International settings? Or, is a different add-on causing issues? I'll do some more troubleshooting until ASP3D is available again. Randy