ericbgee

I noticed the same thing earlier today. Ctrl-E to start the engine fixed it. And, yes, I usually start it up from cold-and-dark using all the proper procedure. But, ctrl-E is doing something that the switches aren't. Not a HUGE problem, but one that I hope they address in the near future.

I think this is true, and also false... aircraft.loc opens just fine in Notepad++, but it's just the aircraft description in all of the various supported languages. Aircraft Localisation File, according to the first line. However, the OP is correct that there is no aircraft.cfg file to be found. My guess is that it is encrypted in the Cfg.fsarchive found in the SimObjects folder... but I have no way of confirming that. Either way, except for their earliest offerings, Carenado has been notorious for making things difficult for repainters. You need that aircraft.cfg file. If you look in your Megapacks and at the corresponding default aircraft in the "Official" packages folder, you'll find one exactly where you'd expect it to be. Not so for the Carenado aircraft.

Well, that wasn't very helpful now was it? WD works just fine for many of us. All you have to do is go to Settings -> Updates and Security -> Windows Security -> Virus & threat protection... on that page, you can scroll down and add exclusions. Add C:\Program Files\EZCA3 (or wherever your EZCA is installed) to the excluded folders. Then re-install EZCA to make sure all the required file are in their proper places. I did this long ago with EZCA2 and haven't had any problems since.

Hi, folks.... I've opened a ticket with Alabeo to let them know, but I thought I'd share here, too. I/We seem to have found a syntax error in the aircraft.cfg. which, unlikely as it may seem, was causing a certain addon scenery module to crash. But, after sifting through install and error logs we found this entry in the aircraft.cfg to be the cause: [Views] eyepoint = -0.7 -0.7, 1.9 There is a comma missing between the first two coordinates. After discovering and replacing the missing comma, the addon scenery module stopped crashing. I've been able to reproduce this event several times in confirming the cause of the crash. FWIW the addon in question is the SODE module used by iBlueYonder (Bill Womack), among others, in his newest sceneries. If you don't have the module or scenery installed, you've probably never had a problem... but you might want to go in and replace that comma, just in case.

In Steve's DX10 Controller, on the "Legacy" button... uncheck "Legacy Aircraft Self Shadow" and "Legacy Aircraft Force Shadows". If you hover your mouse each of them it says NOT to leave checked. Don't ask me why, I don't know enough about it to answer... but this solved problems I was having with the same planes.

I couldn't disagree with Carlos more. I run PMDG's NGX and 777 (among others) along with TrackIR, OpusFSI, Plan G, FSInn... with no problems... (except for the occasional OOM around high population density areas in the 777) There's no need for a supercomputer... although, it helps if you can afford one. I can't. i5 - 3470 @ 3.2GHz 12.0 GB GeForce 730

Let me get this straight... you're here trashing 10+ year old, home-entertainment, flight simulator software because it's got some glitches such as oversized scenery and not-entirely-accurate flight physics? Welcome to 2004! We've missed you. We're so glad that we've finally got someone of your caliber to put us straight. You don't like confrontation? Then don't be so confrontational and stop whining about obsolete software...

With all due respect, I wasn't referring to you, personally, at all.... simply that there is a very vocal segment of the flight sim community that is obsessed with details and authenticity to which I did not necessarily belong. Perhaps I could have worded it a little more PC, I will agree, though, that the original wording of the post and package are definitely misleading... and that, although the additional eye and ear candy are nicely done and appreciated, more credit should be given to Sr. Lucena...

I had been toying with the idea of putting the FSND updated 737 VC into their MD83, just because I'm not a big fan of their MD83 VC... now I don't have to hassle with it. I think that doing so, then calling it a 717 is a bit of a stretch... but it works, and all of the extras you've added look and sound great in the video. Since I don't tend to be as anal as some others about details and authenticity, I'll definitely check it out and give it a go...

I hate to be Capt. Obvious, here, but unplugging any controllers that you don't want a particular game to recognize should fix your problem. The problem does not lie with your rudder pedals. If there's no setting within the game to select/calibrate/etc. individual controllers then your best bet is to unplug whatever you're not using.

I was recently having the same problem... it turns out, in my case, that the JS41 is much pickier than either the NGX or T7. I had set an add-on plane as my default flight. It is a relatively simple plane and I didn't think anything about it because both the NGX and T7 loaded perfectly. However, the JS41 just crashed FSX to the desktop every time I tried to load it. After switching the plane in my default flight back to the FSX Default C172, the JS41 loads right up without a hitch. It seems to be very sensitive to the changes in FSX that other aircraft make, and doesn't want to load properly unless it's got that blank slate...

@Scott Yes, Captain Obvious... perhaps it has, although comprehensive searches on the major websites have turned up nothing. Perhaps someone (maybe even you) has gotten it off our site from the back end. Perhaps one of our members shared it. I'm not upset, but I had hoped that you might be able to tell me where you got it, so I that I can fix that problem... especially since your signature is pushing a totally different flying club, not ours. If you can't or won't help, that's your business... although it does negatively affect your credibility, IMO. EDIT: An apology is required from me. I just discovered that, in theory, nobody should be able to download our assets without being logged in as a member. However, our old download pages will appear in the results of a google search for a specific FSX paintjob... "Carenado C337 repaints" for example... and anyone can download. We obviously need to fix this and if I hadn't seen your screenshots, Scott, we might never have noticed this. I apologize for doubting your intentions. Nice screen shots! Enjoy! :Applause:

Scott... yes I know. It's a repaint that I did for the Deer Valley Flying Club, and wasn't uploaded anywhere else but their website... so I was just curious.

I really like that C337... where can I get that paint job?... :Big Grin:

I was afraid someone would misunderstand that. I don't have FTX Vector, either. I'm referring to the FTX Global vector night lighting.... the night lights that follow vector objects such as roads, etc. FTX Vector (or UTX... or even default FSX) provide the vector data for the vector lighting in FTX Global. So... After using the UTX/FTX utility, FTX Global's vector lighting is visible when using UTX. This has also had the benefit of making this night lighting visible over my photoreal scenery, such as Megascenery Earth. I hope that explains things a little better.