alexzar14

That flight I flew with no star entry till the T/D, so I don't know what helped more, the trick with the star or easing down on display settings. Can't experiment with this forever because I have a lot of stuff to do... I'm struggling with IXEG 737 v1.7, every version fixes 1 bug and adds 3 new ones... and for my next overnight flight I want to fly the a2a Strat to Honolulu.

Ok, KATL (imaginesim) to EGLL (Asoft) with AS16 cloud layers set to 3, arrived with 1050mb on approach and 950mb at the gate, which is super awesome, it shocked me!! Started with 1350MB at KATL, and then it stood at 1150mb entire flight. I gave up on some crucial settings. From: SCENERY COMPLEXITY - VERY DENSE AUTOGEN VEGI DENSITY - DENSE AUTOGEN BLDG DENCITY - DENSE I went down to: SCENERY COMPLEXITY - DENSE AUTOGEN VEGI DENCITY - NORMAL AUTOGEN BLDG DENSITY - NORMAL These don't effect fps rate performance but seems to effect VAS a lot. Well, I let it go, nuff with the ever going race to improve the look, pushing pushing and pushing... From now on it's just flying the plane - something I learned in XPlane. With FSLabs Concorde I set the settings way down still, and the only time when you have time to look outside the window is in cruise mode at 60000ft anyway ))) Bye-bye high scenery display settings. Maybe will restore the scenery complexity back to Dense (so NYC MHTN doesn't look like a farm land) but autogens will leave at Normal. Also, will go back to rock-solid 3.2, 3.35 is too VASy.

I use dome light only at the gate, and even then I use it rarely, as I normally use the panel dimmer lighting and use it to 40% brightness max. The flights I restarted were conducted at day light, didn't have to use any cockpit lights. Don't worry, you have plenty time to save, by the time it is released you'll save enough to buy 5 "queens" ))) As for 777 bugs fixed, indeed wouldn't hurt to have it fixed. With projects-in-development are in development for decade-long periods, suspending support for existing (sold) products is not a good idea.

From now on I will do it enroute starting with 777 and see if I get better VAS. I'll owe you a beer if I won't have to restart my next 777 flight when in flight! ))) Meanwhile the 777s are on hold, we have to catch on to some other 5-graded stuff - DC6, An-24, and A2A B17 are in priority now.

ok I see, done via gps and adf radios ))) It's good, this plane and the way it's made is...really somethin.

I enter approaches at the start, there have been unpleasant experiences when entering approach inflight results in CDU failing to calculate VNAV properly (mostly true for XPlane, so I took into habit to enter STARs at the start).

I can't operate non of these radios, they seem to be "fake". The manuals look over the van instruments, but I could not find any sections on the radios themselves, and the users' videos on youtube are little informative. If there are good tutorial videos (including checklists) please suggest.

I always wanted to ask, what is this and why is it coming up? Massive manual... can't find it. 3 messages appear on eicas display followed by loud warning noises. Messages and warning removed by rotating the map scale knob on efis control panel. Also, is there a way to define Cold and Dark items? Lot's of overhead functions are enabled upon C&D (selected via CDU), I would like to be able to press few more buttons on start up ))

It works so far, but the VAS usage increased in 3.3.5 - effected PMDG planes only. NGX flights still have VAS reserve at the end but the 777 is.... disaster. Having to restart 2 times to complete a flight. Haven't tried iFly 747, if that performs as it was in 3.2, then the problem confirms to PMDG.

I did 2 flights in 3.3.5, both flights had to save and restart. KDFW-EGLL, restarted once. LTBA-KJFK restarted twice (cautht it just in time before crush). Sceneries are FSDT/T2G/Asoft 737 NGX has been effected by 3.3.5 too, although a little bit. With 777, the VAS is decreasing badly in cruise flight which was not the case with 3.2 where VAS usage was steady, I could circle the globe 20 times and the VAS could stay more or less the same, dropping only at lower altitudes on approaches. In 3.2 I could land at EGLL with 650 MB remaining (done many times, never under 600 MB at the end). P3D settings were kept as they were with 3.2. Update to 3.3.5 was done via client and content reinstalls. Windows 10, 4790k, GTX 970.

ok, this time it worked, although I went back to 3.3.5, that may have fixed it. Also with two previous flights I manually inputted the route inputting airways, and today I imported the Routefinder plan straight (sids stars transitions added afterwards). Next time I'll have to try inputting the route manually again and see if that works too.

I use CH yoke, pedals and throttle, I'm not saving on my hobbies and good time ; )

Yes, I do retrim downwards after takeoff, as I accelerate the takeoff trim is too much and needs to be trimmed down (especially on MD-80 both Coolsky and Rotate for XP need a lot of retrimming work in manual flight), that we understand.

I set trim per value calculated by CDU, usually it needs a lot of trim but within green sector. Take off and manual climbs are nice and smooth. But I will paly with trim per suggestion if the AP doesn't engage. Yesterday I flew a 777 and it did ok. Tonight will fly the NGX.

I did cycle the FD, I tried engaging AP with LNAV/VNAV - on, off, and with VS/HDG modes on, it did not engage until high altitudes. Will try a third flight, if the AP doesn't engage on 3rd flight I think I will have to reinstall. 2 years flying this plane with no problems, well understanding the AP, CDU functions, FD bars etc. Tonight will fly a 777 for the first time since I went back to 3.2 and see how that one does, may be the same thing...

Bizarre problem, but it exists and it is irritatish. AP doesn't engage after take off. Everything (electrics, generators, hydraulic pumps etc) is ON, IRS aligned, LNAV and VNAV do engage and AT works, but Autopilot does not engage. This started happening after I upgraded to P3D v3.3 and back to 3.2 (it was ok with 3.3) - that's all that I did in the sim. First flight in downgraded 3.2, AP could not engage until 30,000 ft. Now second flight, again, was able to engage at 28,000 ft. Please see how to get out of it.

Saab 340 is good, it is the same era as 733, similar tech, they make a good pair. Also, lovely and well done plane is a Jetstream 32, really love it and it was one of my 2 favorites with FF 767 before IXEG came out.

These two don't compare, it is like comparing a bicycle with a motorcycle. JAR airbuses (and so is Aerosoft's FSX one) are generic addons, far, far, far inferior to some famous developments including IXEG 737. If you want to fly Airbus then you buy JAR/Asoft, but if the choice between JAR and IXEG... there shouldn't be any choice, motorcycle is better than bicycle. Desperately wanting the FSLabs Airbus...

good hints will check, 777200lrf. But this is both in P3D and XPlane, with identical rather behavior. Could XPlane have double assignments as well? As for the hardware, don't mind buying the new pedal set, but just in time I found out it is not the hardware's fault. Read same subject on Flightsim.com hardware forum, the guy had same problem with 2 CH pedal sets and 1 Saitek set. Solution however is not known.

ok done some flying in both P3D and XP, the problem traced to hardware. I uninstalled the drivers, it helped little. There is a workaround: every session I must calibrate the CH Pedals, XP or P3D, and I can fly ok. Often however I must calibrate it after landing again, and sometimes more then twice, so obviously it is annoying. What do you think, I have to buy new pedals or what?

Ok I uninstalled drivers, it helped but not entirely, the problem was returning. Then, I unplugged the yoke/pedals from PC USB ports and plugged it into the powered USB receiving power from the wall outlet (I heard the trick before concerning the other issue but it may be one chain of events I thought). Now it seems to be ok finally.

Thanks I will try that tonight! The pedals are old, about 10 years (I didn't sim all this time, I had long breaks and was putting together my life plus the hardware on the market wasn't sufficient anyway, but now I am simming a lot). I would say the pedals were used for a period of 3-4 years equivalent to average use although aging is always aging even when idling. The yoke I replaced just a year ago, but the pedals I kept original. I believe the problem will be solved this time and I won't have to replace the pedals, I will report.

ok I traced the problem. First of all it's not PMDG. Second, it's not even a P3D, I started getting the same in XPlane - the left pedal is pushing itself in. In P3D I calibrate the pedals every time I start the sim and it does the work. But after landing I must repeat the calibration process again. I guess I must take this problem elsewhere because it is the hardware (CH pedals) electric signal or the CH drivers problem, yet if anyone has suggestions please advise.

No, happens at different airports and with ASN off.

Both 737 and 777 are pulling to the left during taxi, and severe left on take off, this just started happening now, all of a sudden. So while taxiing, I started to look at my pedals inside VC and what happens is that the left pedal is slowly but progressively pushing itself - in! (the right pedal does the opposite of course). I corrected this by pushing the right pedal on my CH pedal set, it does return the pedals to neutral position, but then the left pedal inside VC starts to push itself - in again. The old problem of throttles not retarding on landing is gone and it seems to retard so far, but now I have the new problem of pedals living their own life. Note, this doesn't happen in the air, only on the ground, so joystick calibration isn't the issue. pleaaassseee..... Besides these two, I flew only the Dash-8 and that one was ok, I guess I gotta try other aircraft to see if the problem is in PMDG or P3D. Right now in the air with 777, won't be able to try other aircraft for couple hours.