Connor Anderson

v3.4.14 is not working. It loads with the sim but doesn't load any camera presets. It simply prompts me to launch my sim.

I am in the same boat. Any update?

I am under the assumption nurbs aren't rendered in FSX or Prepar3D.

Hello, A bit of an odd question... Is it possible for hardware today to produce round 3D object without the use of polygons or triangles? I read somewhere the calculations needed to produce a rounded 3D object would be unlimited. Thank you for answering to my curiosity.

I spoke with a gentleman who was experiencing the exact same issue with the 717. On the other hand another user was experiencing it only upon night flights. I can't find the consistency, but they claim to be working on it.

An update: I found the nvwgf2um CTD was being caused by the TFDi 717. They've listed it as something they are working on fixing here: http://forums.tfdidesign.com/index.php?/topic/436-the-immediate-to-do-list/ Thanks for the helpful responses. Connor

In that case, I will install it and give it a shot both installed and uninstalled. Thanks!

After giving Windows 10 some time, and watching for the kinks to get worked out, I made the switch. Running both P3D v3 and X-Plane 10 flawlessly on Windows 10 at the moment.

Jim, Thank you. I know I don't have GeForce Experience installed. I will remove my old driver and install the latest. Thanks again! Connor

Hello, I am experiencing Fatal Errors within P3D v3 running Windows 10 and while connected to VATSIM via VPilot. I don't know how to interpret this error which is listed under .NET Runtime: Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 6035D500 Any help would be appreciated. Thanks, Connor Additionally here is some more info: Faulting application name: Prepar3D.exe, version: 3.4.14.18870, time stamp: 0x581239e2 Faulting module name: nvwgf2um.dll, version: 21.21.13.7595, time stamp: 0x582cfb8f Exception code: 0xc0000005 Fault offset: 0x00c3d500 Faulting process id: 0x1ef4 Faulting application start time: 0x01d25ef90bddfb0e Faulting application path: C:\Prepar3D\Prepar3D.exe Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_410e5247be0e5f00\nvwgf2um.dll Report Id: 5290046b-2a82-42f4-bd05-b3913a730ddc Faulting package full name: Faulting package-relative application ID: And a little more: Fault bucket 108646278503, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Prepar3D.exe P2: 3.4.14.18870 P3: 581239e2 P4: nvwgf2um.dll P5: 21.21.13.7595 P6: 582cfb8f P7: c0000005 P8: 00c3d500 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREA93.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_b1455b4185bea9b844f8f536251db5799657ab1_b7731188_14cec00f Analysis symbol: Rechecking for solution: 0 Report Id: 5290046b-2a82-42f4-bd05-b3913a730ddc Report Status: 0 Hashed bucket: 56d75acb6a9f2578ea048c7b1c24b651 I apologize, I simply don't know how to interpret any of this.

Hi Jorge, I was able to solve it by removing the FSUIPC.ini file. Thanks for the reply!

Very good, I haven't touched the manual in a while.

I'm in the same boat. It's really frustrating when you can't use something you paid good money for.

Good to know, and will do. The only reason I purchased FSUIPC is because I was interested in utilizing an old joystick as a steering tiller. Is this still an option?

Thanks gents. After moving FSUIPC's .ini file into the P3D directory the issue was solved.