Jim Robinson

I may be completely out in left field here, I don't have FS2Crew and I've never used it but I had a similar problem in P3D v4.5 when I once made an AI flightplan for the default Rockwell Commander 114 (Carenado). I had the Commander set up to do a local flight from/to KINF (Inverness, FL). I was flying into the area from KBHM and according to the AI flightplan the Commander would have been sitting on the ground at KINF awaiting it's next circuit, I noticed every time I'd get within about 35 nm of KINF the engines would flame out. I flew the flight multiple times in different aircraft and did eventually determine that the fuel levers had indeed been moved to the cutoff position. I removed the Commander from the flight plans and was then able to complete the KBHM flight successfully. I also noticed that if I was parked on the ramp with engine running in for example the default Maule (as a user aircraft this time around) and switched to the Commander the engine would die and I'd have to re-start. I concluded that there is something in the init part of loading that plane's gauge code apparently that causes this and even when used as AI it somehow affects the user aircraft. Is there a chance you've added a Carenado aircraft as AI recently, or has anything otherwise changed with regard to AI?

That came up a while back over at flightsim.com. In fact it was just after your freeware release and I wondered at the time if it was a ripoff of your work. https://www.flightsim.com/vbfs/content.php?21671-ContrailSim-–-Seasonal-Vegetation-for-MSFS I would get in touch with Nels Anderson since it's available on the flightsim.com store: Contact page, last link is Nel's email: https://www.flightsim.com/vbfs/content.php?20 Item for sale on flightsim store: https://store.flightsim.com/product/contrailsim-seasonal-vegetation-for-msfs/

I have a copy of that file, PM me your email address if you still want it and I'll send it to you.

I don't have Sky Force 3D but I tried it with REX Texture Direct and it killed it. Have you tried - and disproven it? Because if you have just come out and say it, I'm entirely too old to play games.

Alt+F4 will kill most programs (including Windows) as long as it's the active window.

There isn't a poll option that works for me unfortunately, if there was it'd look like: "word not allowed word not allowed word not allowed..."! From where I'm standing I see Spring, Summer, Fall, and "Loser". 🙂

They tried that 10 yrs ago, everybody complained.

I did, this one loads 5 pax by default at 175 lbs each plus 55 lbs baggage (as per SimBrief). //Weight (lbs), longitudinal(Z), lateral(X), vertical(Y) positions from datum (feet) max_number_of_stations = 14 station_load.0 = 175, 16.21, -1.15, 0 //"pilot" station_load.1 = 175, 16.21, 1.15, 0 //"copilot" station_load.2 = 175, 12.43, 1.41, 0 //"pax row 1R" station_load.3 = 0, 10.79, 1.41, 0 //"pax row 2R" station_load.4 = 175, 8.89, -1.51, 0 //"pax row 3L". station_load.5 = 0, 8.89, 1.51, 0 //"pax row 3R" station_load.6 = 0, 5.22, -1.51, 0 //"pax row 4L" station_load.7 = 175, 5.22, 1.51, 0 //"pax row 4R" station_load.8 = 0, 1.48, -1.51, 0 //"pax row 5L" station_load.9 = 0, 1.48, 1.51, 0 //"pax row 5R" station_load.10 = 275, -8.69, 0.00, 0 //"bag 804lbs" station_name.0 = "pilot" station_name.1 = "copilot" station_name.2 = "pax row 1R" station_name.3 = "pax row 2R" station_name.4 = "pax row 3L" station_name.5 = "pax row 3R" station_name.6 = "pax row 4L" station_name.7 = "pax row 4R" station_name.8 = "pax row 5L" station_name.9 = "pax row 5R" station_name.10 = "bag 804lbs"

Engine start buttons?

Yep, time to fill 'er up again! Maybe get the windshield and check the oil while you're at it. 🙂

Thanks, much appreciated. I couldn't even get a reliable connection to the google speed test, lol. it erred, "were having trouble connecting to this site, please check your connection and try again." 🙂 HughesNet just rocks, support amounts to "we have other users on the same beam that aren't reporting problems". It's the only thing available, $60 bucks a month, I'm still waiting for DSL through my landline circa 2005, I live in a 3rd world country called Idaho.

Some profiles are officially available here: https://www.littlenavmap.org/downloads/Aircraft Performance/ And here's a tutorial on using the data collection feature to make your own: https://www.littlenavmap.org/manuals/littlenavmap/release/2.4/en/TUTORIALPERF.html It's neat because you can run the data collection on every flight if you want to, then you merge (average) the new data with what you've previously collected so it gets more & more accurate the more you fly. I've had my fuel come out to within just a few pounds of what LNM predicted I'd have left over upon arrival at the destination. LNM takes wind into account of course, it automatically gets the winds from NOAA if you're doing a flight in real time, or if you're using historical wx not in real time you can input winds manually after getting them from AS.

Thanks for your helpful input, I've since deduced that the station loads are in feet (from the SDK, which I should have checked before posting this topic) and I've made the conversions. I don't see where it's adversely affected the flight model. I can now load the 560XL to max gross without piing passengers on top of passengers and that was my goal. I'll keep an eye out for those exaggerations you speak of and adjust accordingly where appropriate, If necessary I'll revert to what I originally purchased because contrary to popular belief I wasn't dumb enough to do this without a backup.

What is up with these station loads on the 560XL? reference_datum_position = 0.0, 0, 0 station_load.0 = 190, 5, 0, 0 station_load.1 = 190, 5, 0, 0 station_load.2 = 0, 4, 0, 0 station_load.3 = 0, 3, 0, 0 station_load.4 = 0, 1, 0, 0 station_load.5 = 0, 1, 0, 0 station_load.6 = 0, -1, 0, 0 station_load.7 = 0, -1, 0, 0 station_load.8 = 0, -2, 0, 0 OK, and so then I looked at the C90 GTX and it has this (the comments are what I'm referring to, which the XLS doesn't have): station_load.0 = 175, 2, 0, 1 //Weight (lbs), longitudinal, lateral, vertical positions from datum (feet) . . station_load.9 = 110, -5, 0, -1 //Weight (lbs), longitudinal, lateral, vertical positions from datum (feet) If these distances are in fact feet that would mean the 560XL's "station_load.0" which is the pilot's seat and "station_load.8" (the aft baggage compartment) are separated by only 7 feet longitudinally (5 feet ahead of the datum and -2 feet behind the datum = 7 ft). According to some specs I found on the web the XLS' overall length is 52.5 ft so I'm having a hard time with the 7 foot distance. If these XYZ station_load coordinates are actually in meters that would make the pilot's seat about 25 feet forward of the rear baggage compartment and that I could probably swallow. So what is it, are they in feet or meters? For that matter the GTX looks completely messed up too, same thing, 7 feet between the pilot's seat and the aft baggage compartment. I was trying to make the 560's station loads a little more accurate, for one thing the last two seats in the back are completely missing so if you want to load the plane to it's max capacity of pilot & copilot + 8 passengers you have to add the last two passengers sitting on someone else's lap to get the weight where you want it and the moment arm is screwy because the last two occupants should be further back. Also laterally all the weights are exactly on the aircraft's centerline at "0" which makes for a nice laterally balanced flight model but it isn't accurate. I zeroed the eyepoint temporarily in the aircraft.cfg and then moved the VC viewpoint around to each seat (visually) one at a time and saved the flight for each position. Then I got the InitialXyz for each station from the .fxml which I'm told is in meters and tried to adapt that to the station_loads. They were fairly close to what Carenado had for the seats that existed, but then when I see the comments in the GTX [WEIGHT_AND_BALANCE] section that these distances are supposedly in feet the discrepancy became apparent. It's not a big deal to convert meters to feet of course, I just don't know which is correct. Any FDE experts reading that have done this before? Station loads in feet or meters?

There's a freeware tool called FS9 Data Utility in the file libraries that will log you position every [specified number of seconds] to a .txt file through FSUIPC. It comes with a .kml template that you can paste the coordinates into from the txt file. I use it to log all my flights (when I remember to start it first) and then I add another <LineString> section to a master .kml and paste the coords from the log.txt. This keeps a running log of all my flights and I can open that in either GE or Little NavMap to see the mess I've made. I thought this one was pretty cool, a huge DME arc arrival into KEGE: ...they look like this in GE:

I think you may need to hit Ctrl+Shift+F4 ("fuel on" in turbines, "full rich" in recips) before you do anything else, your default flight is probably saved in fuel cutoff mode (Ctrl+Shift+F1). Next time you hear it spool down press Ctrl+Shift+F4 and see if it takes off. Jim

It seems deleting my previous Nvidia Inspector profile for P3D fixed the problem. I've started the sim a couple times and ALT+Entered back & forth between fullscreen and windowed mode a dozen times without the eyepoint/view going wonky so I'm calling that one sorted. I have no idea what was in that profile that caused the problem, TBH I barely remember making the profile and I'd basically copied what was suggested for FSX using the DX10 fixer pretty much just as an experiment. That took place back in the P3D v2 days, but Prepar3D.exe is Prepar3D.exe to the driver so it treated P3D v4 the same as it treated P3D v2. I had to reinstall Nvidia Inspector to even get rid of it, lol. Anyway, on to the next hurdle! Jim

I've been out of simming for a couple years and I just installed P3D v4, I'm having problems whenever I try to go between fullscreen and windowed mode where the eyepoint seems to get messed up and the zoom changes making everything blurry. It's hard to explain, in VC I end up looking upwards to the left at the headliner and when I mouse-look it seems like I'm using a fish-eye lens or something. Reloading the user aircraft fixes it but that's not something I really want to do at FL330 every time I try to look at a chart or something in another window. I'm running Win7 still @ 1920x1080 and most likely a very outdated driver for my GTX770, I'm working on that. I did some searching, read some threads not really related to the problem I'm having and tried to find Disablefullscreen optimizations thinking "hey it's worth a try" but apparently that's a Win10 thing and I couldn't find anything like it in Win7. I tried all the different compatibility settings available in Win7 anyway and nothing made any difference. It did this the first time I started v4 on the first flight I loaded with the Maule. Any words of wisdom from the v4 veterans? Thanks, Jim

It'll probably be the Carenado C25A somewhere between KMTJ (Montrose, CO) and KPVU (Provo, UT) if I last that long which I probably wont. lol.

I do Ctrl+E, sometimes I even slew 🙂 !

Those are awesome, thank you!

Just put it in there a 3rd time then and select the last occurrence on the DTO page.

Thanks to all who helped out, I'm using this too and I'd never figured it out without all the detailed instructions! Jim

I managed a few, maybe one of these will work? More screens on the way! Those are what I had of the crew. Jim

Pssstttt, hint, hint - N390GM just came out of the paint shop IRL