Search the Community
Showing results for tags 'P3D v3'.
Found 7 results
-
Hi Everyone, I had to do a reinstall of P3D v3, and the picture shows how so the American midwest and heartland are covered with all of these brown farms with ORBX FTX +OpenLC North America. This wasn't like that before, everything was nice and green, and this is not a seasonal thing because the textures are the same in spring and summer. I don't remember there being so much brown everywhere, and I'm wondering if it's a problem related to the new installer and updated files. I also don't have any other landclass or mesh products installed, and as far as I know, the order in the scenery library is exactly as it was before. One thing that I thought would be the problem was installing ENVTEX grass, but the problem remained after I undid that and reinstalled everything again. So, I'm stuck. I was using v3.4 for 6 months with beautiful green until yesterday when this started showing up, and for the life of me I can't figure this out. Anyone have any ideas? And, yes, I did post this in the ORBX forum, but I thought I'd throw it in here to see if anyone else encountered this difference. This screenshot is from p3d v3, just south of Chicago...but this patchwork seems to be around the region. Thanks, John -
Hi everyone. I have some problems with SimConnect or FSUIPC. I did a flight from EHAM to my brand new scenery Flightbeam KMSP. At 50% of my flight it freeze every few seconds. After a few 10 minutes later this issue disappeared. A few hours later this issue started again. Later I saw that my memory was at 100%, and a few seconds later my sim rant into OOM. Few minutes later the sim closed itself and my RAM was at normal again. After that I start P3D again, it was loading and the same happens again. But this time my computer froze and I did a hard shutdown. Now I flying back from KMSP to EHAM. And around 50% of my flight, I have again issues. I chose to play it save and close the simulator and restarting it form my last autosave. Again a few hours later, its happening again. This time I decide to just let the sim run, and the sim ran into a fatal error. Now I did some research, and discovered this in the FSUIPC logfile: 'No SimConnect events or states being received!'. Can a single scenery airport cause this? P3D fatal error: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-07-08T16:09:36.901370500Z" /> <EventRecordID>38317</EventRecordID> <Channel>Application</Channel> <Computer>Skynet</Computer> <Security /> </System> <EventData> <Data>Prepar3D.exe</Data> <Data>3.4.9.18400</Data> <Data>57d9b14e</Data> <Data>SimConnectP3D3.dll_unloaded</Data> <Data>3.2.2.16659</Data> <Data>58f1f032</Data> <Data>c0000005</Data> <Data>00001ec0</Data> <Data>6678</Data> <Data>01d2f7eb3cac8c87</Data> <Data>F:\Program Files\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data> <Data>SimConnectP3D3.dll</Data> <Data>d6251f2f-63f7-11e7-9e4d-d8cb8a9cd07e</Data> <Data /> <Data /> </EventData> </Event>
-
Hello All, Need help - I have issues with EZdok v2 installed on P3D v3. It installed correctly and started once spawned by P3D, i.e. appeared in plugin tab. However, I keep getting this EZdok pop-up windows 'Damaged file #1' when P3D is starting. The pop-up message also appears when I tried to import EZdok cam file. I have tried many options - install, re-install, disabled anti-virus, Admin rights etc, but keep getting this error message. I also tried using the recent Beta version, by replacing the files - same errors. Hope you guys can help or give some pointers?
-
Does anyone know of a good (would be willing to pay, I want a good simulation) Pipistrel Sinus, Virus, or Alpha for FSX/P3D? Also, does anyone know of a good Air Tractor plane for FSX/P3D? Many thanks.
-
I've had v1 of Lisbon for years and finally got fed up with the grotty looking terminal textures. A month ago I bought v2 for my sim - P3D v3.4 Whilst the terminal buildings are greatly improved the lack of moving jetways is disappointing but my main problem is the disappearing PAPI lights when on final approach. Around 2-3 miles out they just go out. The problem according to Aerosoft staff is a bug in P3D and the author of Lisbon appears reluctant to fix it when his code didn't cause it. Fair comment. LM haven't released any correction as far as I know. But this leaves me with a non-functioning PAPI system on a P3D compatible airport. I don't suppose I'm alone having this problem but has anyone got any suggestions on how it can be fixed?
-
I just purchased ChasePlane and I am really enjoying it, except for one issue. On the ground, ChasePlane functions perfectly normal and what not, but right when the wheels lift off, it seems that the camera is very glitchy moving around and frequently will take a second or two to even move to a different view when I press the key for it. Moving around the camera with my hat switch produces a very laggy effect as well, yet the sim itself, is running very smoothly with no stutters. Please let me know what I can do to solve this issue, thanks!
-
Hi gents! So I finally bought P3Dv3 Pro version a couple of weeks ago, and bought PMDG 737NGX Base package today. I'm having one issue though; the installer will not run. The UAC dialogue asking permissions to run the file pops up, but that's it. Nothing happens after that. No dialogue asking for anything, no error messages. It just doesn't start up, without any messages or indications of error...apart from not starting. Thinking it might be the UAC causing problems, I've tried disabling that all together, but still no joy. I've re-downloaded the installer, both with and without any AV/Firewall (I run ESET Smart Security Premium) active, still nothing. I do have PMDG 737NGX Base Package, as well as the 600/700 expansion installed and working on FSX-SE on the same PC, and installing that went flawlessly. P3Dv3 runs flawlessly on its part. PC is running Windows 10 64-bit. So I'm a bit stumped here, I've got absolutely no idea what can be causing this. Can anyone give me some help, or even hints as to what might be going on here? Thanks in advance!
