Ripcord

Pretty sure it is not a compatibility issue as I never had any such anamolies in FSX, and I used all the same ORBX products. However I'm not sure enough, Kevin, that it isn't worth trying your suggested course of action. It might clear up some issues elsewhere, if nothing else, and I can always restore the files if it goes wrong. Good suggestion, thanks.

Excellent advice, thank you. I have 4 of them installed. One is ESP.Simconnect and three other versions of SimConnect. Yes I have exactly these same 3 entries installed. Again, great advice, thank you. It also occured to me earlier that I need SimConnect installed in order for FSDreamTeam Addon Manager to work. Mine works. So much have it in there somewhere. I appreciate all the helpful responses, thanks guys!

I have the same problem, since I installed P3D v2.3 and began moving my FSX addon scenery over. I was able to use ModelConverterX to convert the model libraries for the main buildings/objects at each airport but the autogen buildings being black is one that I'm not able to solve. See no other choice but to just sit and wait for the dev to get around to it, sadly.

OK, now here we might be getting somewhere. So you are saying that it is quite possible that I have, in fact, installed simconnect? How can I check this? I have run this simconnect.msi file several times already -- the one found here: Prepared v2\redist\Interface\FSX-SP2-XPACK\retail\lib\SimConnect.msi As somebody else observed, it just doesn't seem to do anything. I see now evidence anywhere, at least. Would be good to know that it is working. BTW, one addon problem is the Captain Sim 777 that is clearly suffering in P3D from not having simconnect anywhere. It runs fine in FSX legacy mode but I'm missing landing year and panel guages when I load it up in normal P3D.

SO I was running thru the steps from Rob A in the processing of doing the update to v2.4, and I realized that I had none of these simconnect files in my set up. copy file SimConnect.cfg to C:\Users\[YourUserName]\Documents\Prepar3D v2 Files copy file SimConnect.ini to C:\Users\[YourUserName]\Documents\Prepar3D v2 Files copy file SimConnect.XML to C:\Users\[YourUserName]\AppData\Roaming\Lockheed Martin\Prepar3D v2 So then I went back and did a bit of investigation and realized that P3D does not install these files. Some third party addon needs to install them. My question here is how do I go about figuring out which addons need simconnect? Sounds like A2A is one of the more common ones, but I don't have that. Active Sky Next seems to create its own connection. Maybe some AI traffic programs use this?

Not yet. Wait until ORBX gets a little bit more of their scenery compatible for P3D V2. Right now they are about 50% done, and making good progress, but I probably made the jump a few months early.

All the above responses regarind ADE and SbuilderX are correct, HOWEVER -- before you do that, first go look for an elevation adjustment file in your scenery/world/scenery folder. Usually it will contain the ICAO code in the name and you can just search for files containing that. For instance, if you have trances at ENVA Trondheim, then you should go run a search for 'ENVA' in your scenery/world/scenery folder first. If you find something like CVX_EVNA or AEC_EVNA then try removing it (don't delete it, just place it somewhere else). Often times that solves the problem where simply creating yet another flatten or elevation adjustment file will only get in the way.

Hmmm, OK thanks. Appreciate it. Almost bought it.

Is anybody running this in P3D v2? Any issues?

Having this same problem with ENVA and I hate it. Has anybody found a good workaround solution for this?

Brett there are profiles in there already -- no addon specific templates for the AEROSOFT 318/319 Extended, as of yet, but they say that the profiles are pretty accurate.

I note that this add-on uses all bmp files for textures, which is apparently a no-no in P3D v2. They need to be converted to DDS textures. Also, I note in Appcrashview that in my three CTD experiences attempting to run this DC-10, it was the panels.dll that crashed. So that might be the place to focus our attention in finding a fix or work-around solution.

So far I have two consecutive CTD events trying to launch this aircraft in P3D v2.3, which for me is rock solid. It is not DX10 compaitible, we all know, but I had no problems running it in FSX with DX10 fixer in DX10 preview mode. So I was hoping it would still work in P3D v2. Looks like this one will be a casualty of the transition from FSX, which is sad. If anybody is aware of a fix or a work around solution, I would love to be wrong about this.

OK, Rob, thank you. I removed the most recent sceneries that I had added, all of which had large photoreal backdrops included. I think also that part of my problem was also that it was trying to verify some Aerosoft sceneries that I had installed just manually, and not by use of the EMT. Might be that it was looking for some kind of registration and wasn't finding it. So that a shortcut that might have been part of my problem, if not all of it. Anyway, all fixed, thanks all.

I do have it on a SSD. Maybe the photoscenery aspect here is part of the problem, as I recently added some of the Aerosoft US Cities packages (all but one), and those were among the most recent changes that I made. Thank you, guys, for the input. I will try first to just wait it out and hour or so and see what that brings. Then I'll remove the recent scenery additions and see if that helps.

Well, I remember this problem from FSX and for whatever reason, where it is again in P3D v2.3 -- terrain loading stuck at 6%. I have added every possible folder exclusion imagineable for Nortons Internet Security and even have put it into slient mode. Still stuck. I should note that it was working fine just recently. Today I got up and turned it on, and this! Going to try to undo all my recent changes to see if that helps. Anything I'm missing?

I had a few where the building objects, terminals, etc, did not appear. I had to recompile the library files using the latest version of ModelConverterX by Arno. Now I got my buildings back. Still a bit iffy on the frame rates, but it works.

Well, it might sound like that, but until yesterday it was working fine. Made these changes quite some time ago, and had no issues.

Rolled the NVIDIA driver back to -- Driver version 9.18.13.3788 Driver Date 5/19/2014 The newest one I had was 7/2/2014. Removed KTVL from my scenery config list and testing that now. I also failed to mention in my OP that I ran a registry cleaner tool and I had hundreds of bad registry entries -- probably this was a result of changing around/upgrading SSD drives, where FSX resides.

OK what on earth did I do here? On Saturday I was flying around just as happy as could be. Installed a couple sceneries. Then installed KTVL. And at some point in the process I updated my video drivers. Now this. Been searching internet threads looking for solutions. 1. Rolled back the NVIDIA drivers -- no change. 2. Logbook.bin was not the culprit. 3. Used old scenery config files -- didn't fix it. 4. Installed SceneryConfigEditor v1.12 and it found no errors. Renumbered all the layers and entries, still no change. 5. I even found one guy whom I know from these forums who had a similar issue which was resolved by reinstalling ORBX libraries. So I even tried that, to no avail. Of course I removed the scenery additions from yesterday (the one exception being KTVL, I left that one alone). Still no luck. Anything else that I might be overlooking?

Downloaded this the other day, Ron, thanks for putting in all the time and effort and tender-loving "zabota".

Remember -- Vector requires FTX Global, and FTX Global provides the land class modules called OpenLC, which are still on the way (Europe coming in a month or two). Give this thing 6 months to a year to soak and mature. By then we'll have the landclass updates, most of them anyway, and Vector will have a service pack or two to fix/adjust some shortcomings. It isn't bad now, but I think this thing will really shine by the end of 2014.

I will say this -- they at least returned my money promptly, so at the end of the day, they made it right. They deserve credit for that.

I did at least get a response. Their email was not getting thru to my Comcast account. Strange but OK, I get that stuff happens like that. However, all they are able to provide in terms of support is 'please just follow the instructions carefully'. That's it. Seriously, have others had a good experience with this group? Based on what I read here, they seemed reputable. They damn sure are not demonstrating it in my case.

Has anybody else had any issues getting their product registered/activated? I've gotten zero response in the 36 hours since I emailed these guys. Just tried a second time. Hoping I haven't wasted my 24 euro on this. I am slowly starting to seriously detest developers that are just too good to sell their stuff through any of the main flight sim sites.