thibodba57

I'm having a rather frustrating issue. About 1/2 the time the Interface fails to launch. Another 1/4 the time it launches but it doesn't connect to the sim. The last quarter it connects to FSX SE (I'm running P3Dv5). Sometimes I'm able to get my table to connect other times not. Even if it doesn connect it doesn't do anything except say its connected as the Profile is set to Default. Regardless. After 1 min the Status of the Intervace changes to Inactive and FS goes to Not Connected. Any input? Tons of Event Errors Faulting application name: VAInterface.exe, version: 2.28.1.21684, time stamp: 0x5e24ef45 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x4b90 Faulting application start time: 0x01d62e275d3ebeaa Faulting application path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe Faulting module path: unknown Report Id: bfa586a0-018c-42e0-89ca-1cd9f2f06ed6 Faulting package full name: Faulting package-relative application ID: Faulting application name: VAInterface.exe, version: 2.28.1.21684, time stamp: 0x5e24ef45 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x3908 Faulting application start time: 0x01d62e27a7347314 Faulting application path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe Faulting module path: unknown Report Id: 2506ae88-bc0c-40dd-a6b5-19f892df14c1 Faulting package full name: Faulting package-relative application ID: Faulting application name: VAInterface.exe, version: 2.28.1.21684, time stamp: 0x5e24ef45 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x2fe0 Faulting application start time: 0x01d62e27bb79d4cf Faulting application path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe Faulting module path: unknown Report Id: b381d36d-3c87-440b-bb28-3d2c7e32de68 Faulting package full name: Faulting package-relative application ID: Faulting application name: VAInterface.exe, version: 2.28.1.21684, time stamp: 0x5e24ef45 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x4e60 Faulting application start time: 0x01d62e27d879c694 Faulting application path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe Faulting module path: unknown Report Id: bec3d7a5-9b9d-4765-b4da-e38cd7ea75a9 Faulting package full name: Faulting package-relative application ID: Faulting application name: VAInterface.exe, version: 2.28.1.21684, time stamp: 0x5e24ef45 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x1f58 Faulting application start time: 0x01d62e27f0d1610a Faulting application path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe Faulting module path: unknown Report Id: 2829e98e-e7f5-4034-aff6-905e88bce905 Faulting package full name: Faulting package-relative application ID: Faulting application name: VAInterface.exe, version: 2.28.1.21684, time stamp: 0x5e24ef45 Faulting module name: VAInterface.exe, version: 2.28.1.21684, time stamp: 0x5e24ef45 Exception code: 0xc0000005 Fault offset: 0x000286db Faulting process id: 0x4de0 Faulting application start time: 0x01d62e28142cb9d1 Faulting application path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe Faulting module path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe Report Id: 475daec3-e6e4-4104-8631-e28ceedd7535 Faulting package full name: Faulting package-relative application ID: Faulting application name: VAInterface.exe, version: 2.28.1.21684, time stamp: 0x5e24ef45 Faulting module name: VAInterface.exe, version: 2.28.1.21684, time stamp: 0x5e24ef45 Exception code: 0xc0000005 Fault offset: 0x000286db Faulting process id: 0x12a8 Faulting application start time: 0x01d62e283e0baf72 Faulting application path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe Faulting module path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe Report Id: a4273a06-e7e9-4b56-bcc9-67aff5995c6d Faulting package full name: Faulting package-relative application ID: Faulting application name: VAInterface.exe, version: 2.27.0.66, time stamp: 0x5b8972fa Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000 Faulting process id: 0x3cac Faulting application start time: 0x01d62e291aceabdc Faulting application path: C:\Program Files (x86)\Virtual Avionics\VAInterface\VAInterface.exe Faulting module path: unknown Report Id: 02a972c5-a72e-46f4-b6a0-f07edee4a17c Faulting package full name: Faulting package-relative application ID: I got about 6 more than this. Each one has different Data. Further Edit: I checked with P3Dv4 on the 777 still works as advertised only issue I see right now is P3Dv5.

https://www.fs-flightcontrol.com/en/

@P_7878 Southeast Alaska isn’t so bad actually. Usually temperate so in the winter 20s. Chicago is by far colder than most of Alaska. It’s got that bone chilling wet and windy cold. I’ll take Anchorage or possibly even Fairbanks over it any day in the winter.

Nice shots! I have probably 2500-3000 hours flying Anchorage to southeast Alaska with generally a stop every morning in Yak to drop the mail off. Even got stuck there for a full day due to freezing rain with Alaska’s de-ice equipment inop. Had to wait for it all to melt enough.

Good to know, it’s been a long ignored niche that should have been done with the NGX with atleast the -700 variant.

There’s also a 30 day refund policy with the iFly (Flight1) product that PMDG doesn’t offer. If that product doesn’t do it for you return it and spend the extra cash on the NGXu. @rmeierwhen did RSR state there was going to be a freighter variant? I don’t remember seeing any post in that regard.

A lot of work has been done already in regards to a metal PK for the 777. I’ll just need PMDGs red channel for the rest of the parts to really kinda wrap it up. Im really looking forward to seeing the Flying Tigers paint in it. Maybe I’ll do a Northwest and Atlas. I really liked how the Atlas Air baremedal came out.

It’s done in the legs page and is extensively covered in the manual. Far more depth than I can provide in a forum post.

I haven’t used imgur but I use Flickr and it will give you a coded format for imbed images to export easily. Easy to use lots of storage and free.

Not an actual freighter no. Steve covered the windows and drew the cargo door. I painted it. Check my signature for my livery list.

I painted a Aerosoft UPS A330P2F if thats might peak your interest.

Please reference my earlier post. https://captainsim.com/purchase/index.html No refund. But it would be great if enough people contacted their CC holders and had the charged declined as it wasn't the advertised product.

I'm sure Steve isn't trying to imply you can maybe get a refund from CS. But just in case anyone thinks you CAN get a refund so they'll just give it shot. There are no refunds at CS. https://captainsim.com/purchase/index.html

Same reason they want to release the -200ER with an Engine variant no one got. The RR. They have to PUSH people to purchase an expansion they would never have bothered with. It would be like PMDG releasing the 777-200ER and offer you the LR only on the basis if you purchase the 777-300ER to get access to the engine variant. Even though you have no desire for the -300ER you have to get it to get that engine. Except this is actually worse than that example because 1. I doubt they'll truly model the engine performance variations. 2. There actually a lot more differences in the 777-200ER vs 777-200LR.