Wagz

GreetingsI've been attempting to convert textures of various payware aircraft for FSX for the VA I'm involved with. I use 32 bit 888-8 encoding on all my textures for FS9. These textures do load in FSX, but various aircraft parts are lit incorrectly (doors are dark etc...). I still primarily use FS9 but may finally make the switch to FSX soon, plus many of our pilots have been requesting FSX textures as well. The first aircraft I'm trying to tackle is the QW 757. As I said 32 bit 888-8 BMPs load fine, but the doors are dark. So, I tried re-saving them as 32 bit 888-8 .DDS textures (flipping them of course), but the same problem occurs. I've attached a screenshot to show you whats going on. I've haven't tried it myself, but some of our pilots are reporting similar issues on the FSX LDS 767. I've only converted the fuse textures to DDS, so I'm not sure if the engines would match the fuse if I converted them as well (but there is no real change from when using BMPs). What format do I need to have my textures in?ThanksJoe Wagner

I've recently built a new system and I'm experiencing a strange phenomenon in FS9 if I "Alt+Tab" back to my desktop while in flight. I'm flying on Vatsim using Squawkbox, and if I alt+tab out to do something else, my aircraft is apparently behaving erratically in my absence. I'll return to FS9 to find my aircraft 1000 feet or more below my cruise altitude descending at a good rate, and usually quite a bit slower than I left it. So far this has occurred with the PSS 757 and LDS 767. A quick glance at my MCP reveals that the autopilot is in the same state I left it, in VNAV and LNAV. The MCP altitude and speed are unchanged, so that would rule out some keystrokes or mouse movement outside FS9 having an effect on it. Immediately upon my return, the autopilot recovers the aircraft and gets it back to its assigned altitude and speed. If I stay in FS9 the entire flight everything is fine. Checking my history on vataware.com reveals porpoising of my altitude while I'm away. Luckily all these episodes have occurred while in uncontrolled airspace, so no one has had a chance to yell at me yet. This one really has me baffled and annoyed, as it never happened on my old PC. I don't really want to have to stare at my flight deck the entire trip, especially if I need to pull up a chart or something. Anyone encountered a problem like this before?For the record, I'm running Windows 7 Home Premium 64-bit.AMD 965 Black EditionNvidia 280 GTX4GB RAM

Oddly enough I installed those new drivers as well, and my aircraft preview went totally blank as well. The odd part is I was running 4X AA/AF already. I seem to recall the drivers not playing well with some other game, so I rolled back to whatever it is was on there before.

It's probably nothing to do with your video card.From time to time FS real weather will report visibilities of 10 miles or less. The problem is that any visibility of 10 miles or less is considered "fog" and the sky is painted that dull gray. Anything over 10 is "haze" and normal sky color is shown.This may have something to do with that fact that all US METARs show a maximum value of 10 miles vis no matter how much higher it may be. I beleive there is an FSUIPC option to increase the visibility generated in this case.Joe

Yep, POSKY's 777 was I think actually created for FS2000, but still worked in FS2002. There were no such things as Opening Doors and whatnot back then.Are you sure you're not using MelJet's 777?

Sure pilots can fly turning and winding aproaches in near zero conditions, but they of course would require some sort of navigational signals (VOR, ILS, NDB, DME etc) to fly by.In your case, you're flying the River Visual. Notice Visual being in the name of the approach. It requires visual contact with the river at all times. In 1/4 mile visibility, low ceilings and snow it is completely impossible to fly this approach real world or sim (which you found out through your 4 crashes obviously). In such conditions the only option you have to get that plane on the runway is an ILS, be it "boring" or not.I can understand that you were looking for a something refreshing and challenging, but I'm afriad you picked an approach that is completely impossible.That said, the River Visual is hard enough to fly in clear skies. I would try flying it at the published minimums for the approach that someone else mentioned above, I beleive 3 miles vis and ceiling 3500 feet. That way you'll be "legal" to fly it, while with the 3 mile vis you still won't be able to see much in front of you down the river. Or, you can try it at night (I have, and it was very intresting).JoeStudent Pilot - 50 hours - KPNE

Hi,I'm currently working on a scenery project of Philadelphia International Airport (KPHL) with a few other people. I'm building the model in GMax which is going well. However, I'm wondering if anyone would like to join us in the project.We need someone with experience in quality texture creation and also in creating ground polys for taxiways etc. Yes, we are "newbies" in regard to scenery design, although I have used GMax in the past, so there are no problems with the models.Anyone intrested can contact me at "wagz0627 @ comcast.net" (take out the spaces) for details.Thanks in advance,Joe Wagner

Oddly enough I set up a windy flight the other day (25 gusts to 35, moderate turb and moderate shear), and the C172 was bobbing up and down just sitting on the runway. Nothing severe though. I'll have to try more.Joe

I'll give that a shot, but I just noticed someone else showing some screen shots of a non textured structure he was testing in the sim. Everything was still very brightly pastel colored as GMax does.EDIT: Nevermind, I've got it fixed, sort of. Apparently the XML file generated had a comment section encompassing the plpacement lines. I'm not completely familiar with XML so I didn;t catch it at first.In any event, the BGL now appears, however the default scenery is still there, so mine is appearing half inside the default. Did I forget something?Joe

Hello,I and a few other people are currently working on a KPHL scenery for FS9. I'm working on the main terminal strcuture now in GMax. I decided to compile the current model (no textures yet) and test it in sim.I exported the mdl file, opened the XML file and placed the coords of the structure. For the record they are N39

Here's an idea:Did you try testing the system out in a more "normal" situation? Every system in existance will struggle with 3D thunderstorms, 100% AI, high detail VCs and high detail scenery areas all thrown at it simaltaneously. You may be expecting too much. All of that is one killer workload on the system.Try a test in fair weather, with perhaps a slightly less detailed aircraft. I don't know if your old system is still hooked up, but if you could compare the same flight/aircarft against both systems, then I am tempted to think you'll see a good increase in performnace. I recently upgraded as well from a Athlon 1900+/768 MG Ram/Ti440 128MB to a Athlon 3200+ 64bit/1 Gig RAM(PC3200)/5700LE 256 MB. I'm running the sim at 1280 X 960 with 4X AA and AF (There's really no point in high res and high AA, one or the other will work well enough) and fps are generally in the 20s (locked at 24) in fair skies with most any aircraft. 100% AI at most airports won't bring me down to less than 10 fps. However, overcast cumulus clouds will bring me crashing down to 6 fps, which is the same as my old system. I haven't tried Thunderstorms out yet, but I'm sure they'll be just as bad. It seems then Cumulus/T-Storm clouds are the biggest killers. Overcast stratus clouds aren't that bad though.So, in conclusion: Clouds are the biggest killers (in my opinion). The new system should let you run most everything else with better performance however.Joe Wagner

While there is no GPS on Eric's panel, you should get the green line for your filed flight plan on the HSI. His panel can also optionally display Airports, VORs, NDBs etc as purple dots on the display. The right hand knob of the two I mentioned before changes the range on the display, from 10 up to 80 nm I think. Pretty much does the same thing as the default GPS without the performance hit.As for Ken's panel, I haven't used it, but I see he has the same two knobs I mentioned on Eric's panel. I don't know if they do anything or not, but you may have to also switch the left kbob to "LS" for the ILS to display. The same applies on PMDG's 737NG panels: If you switch to VOR mode with an ILS tuned a message appears stating that this is not an active VOR signal. Joe

Actually that circle button will switch the HDG to CRS and vice versa. To track the GPS flight plan, right click the HDG Knob (the equivelant of pulling it out, as opposed to pushing it). The HDG display will change to dashes and the aircraft will track the flight plan.As for the descent speed issue, at light weights these suckers will accelerate on descent. Leave the VS at somewhere around -2000 to -2500 fpm. You'll have to deploy the spoilers to some extent during the descent. I was on a BA A319 heading in to ZRH last summer and we had the spoilers deployed until we were on final for runway 14. In fact they kept the spoilers open until the flaps were set to the second notch. It was a fun ride :).EDIT: Oh, and if you can't display the ILS on the HSI, look for the two knobs above the HSI. Switch the Left hand knob to "LS" (Landing System).Joe Wagner

Yep.When the patch/upgrade/bugfix or whatever was announced for FS9, they said in that announcement that the next version of FS would be announced in something like 6 to 10 months time. If my brain is still functioning, that was late August (I think). 6 to 10 months from say Sept 1 is somewhere between March 1 and July 1 2005, which would be roughly on "schedule" with how past releases have been announced and released.

This sounds like your joystick/yoke/other control device is malfunctioning big time. It sounds like a severe case of noise in the cable, sending erroneous commands to the sim. If the flight controls of the aircraft are not affected, it could be a number of bad buttons on the stick (hat switch sending of commands to cycle views, button for flaps repeatedly sending command etc).There's nothing in the panel that could cause anything remotely similar to this. Further proof that your control device is at fault is that you mention the problem continues when you switch to a differant aircraft (I'm assuming one that doesn't use Eric's panel).Joe Wagner