gtjoha

I have the same problem, SP1b, latest ASE build and FSUIPC 4.7. I use DWC, and have disabled turbulence and gust effects through FSUIPC.On climb I normally do policy of 280 (VNAV), and for small wind changes of only 1 or 2 knots - giving and IAS of say 282, autopilot pitches aircraft up suddenlyseveral degrees to return to 280. On descend I have a more slow "bobbing" motion, where I get "stuck" 40-50 ft either above orbelow profile in this bobbing motion. Engage V/S, put myself perfectly back on profile and re-engang VNAV, and a/c leaves profile with40-50 ft and stays here bobbing it's way down. Can't see how it could be weather related either. Winds are not changing.Geir.

I see this is an old topic, but as I stumbled over a "solution" today, I though I'd answer. Been having thesame problem myself for some time, and when thinking back I remember it started after making someconfig. changes in windows. Today I turned back the resolution settings in windows, to what I used tohave when I installed the NGX (1440x900). Lately I've been running on 1920x1080, so I'd avoid the"shift" when going from fullscreen to windowed mode.Well gues what, suddenly the rotating knobs work with the mouse wheel again... I have no idea why.Let me hear from you guys if you read this and try the sameGeirNorway

Thanks for you answer, m8 :)I was guessing for an average, but would be nice to know for sure.. Doesn't say specificly in the manuals.

Hi guys,just a small question here I'm trying to work out some good snapshots for future flying. Its a great concept, so I amexcited to try it out. However, I have failed to understand wether it load a single snapshot for an entire flight, based onsome sort of "average" for that flight, or does it load from several snapshots depending on how the weather isunderway? For instance if weather is clear on departure and stormy where you arrive, will ASE load a stormysnapshot for your arrival and a clear for the departure?RegardsGeir JNorway

Hi guys,My ND often gives weird readings after loading a saved flight, not in line with what's on the flightplanin the FMC. Track goes out past the range of the display and back, from a direction neither flown or planned..SP1b..Others with the same problem ,or know what's causing it?See screenshots attachedGeir J..Edit: For some reason track is not shown as magenta on the screenshot, but it is supposed to be...

Normal LOC intercept speed is about 220kt at 10nm, to my knowledge..Otherwise I maintain 180 to about 4-5 miles, and there is no trouble slowing down in reasonable time when going to F15 and then F25, or even straightto 25. Of course gear must be out, and engines at idle. Start configuring 1 mile early, so at 5-6 miles.OM is normally at 3-4 miles, so 170 shouldn't be a problem as I can see it? Just drop out your flaps, you don't even need to use the speedbrakes. In factthey shouldn't be used, they should be ready and armed for landing.That's my approach. Following a schedule might not work when ATC gives explicit instructions.

This sounds like something that can be very useful for training purposes. I will definitively try out the demo :)Thank you for the informative post.Geir J.

You're abseloutely right, don't know how I missed that one :)

FD is on and speed is set. FD bars are not showing as no modes are selected on the MCP and A/T has not been armed. V-speeds are not programmed and confirmed in the FMS either.Speed should however be set to V2 on the MCP and not 250.Geir J.

Autopilot won't engange as long as gear is down. Pull up your gear straight after takeoff, as one normally does and make sure trim is correct on takeoff. Then you should be ableto engange just fine.Also; there is no need to engage any other mode prior to engaging autopilot. A/P goes straight into HDG and LVL CHG mode automaticallyand so keeps the attitude of your aircraft at time of engagement. I never engage VNAV or LNAV until I am in an established climb and aboveacceleration alt.

Would be nice to hear from you what you find out.No, I'm pretty sure I first noticed this problem after SP1b too.

I seem to have researched my way in to a "fix". Hopefully this helps someone else than just me: I build my flightplans with FSBuild, and when it seemed the problem wassomehow connected to the .rte files I did some searching on fsbuild related problems. Seems when I build my flightplans without SID/STAR and without departing and arrivalRWY, loading of a saved flight works just fine. I have no idea why though, but as I read something on another thread about the NGX FMC disregarding all SID/STAR and RWYin .rte files I figured it was worth an attempt. And it worked.Appreciate any feedback on whether this solutions works for anyone else.Geir

+1

I think I may have found something... I noticed at a couple of occations I got a green message when loading, that said: "Destination airport not found in .rte file, import aborted"So I tried making a simple flightplan in default FSX planner instead, punching manually into the FMS after and now the plane loaded just fine.. So perhapsit is something about the .rte files when trying to load a savegame in the NGX..

Ok, good to know it's not only me. Maybe I should try installing simply SP1, and drop SP1b for starters..

In addition: Tried a clean install, followed by Sp1b - but that did not help.

Thanks for your reply guys. However, it seems that it happens for me now on every flight. Currently I am flying the Westjet 737-800WL.Also, nothing is responsive, neither stick or throttle. All is dead. Autopilot is also "reset", reading just 0 on CRS and HDG, and 100 speed, 10000ft.The countdown from 20 sec. to initialize the airplane doesn't happen either. So currently I am unable to save during flight..Geir.

Hi guys,Now and then I experience that when loading a savegame which is saved in the air (have never tested it on ground)the airplane is totally dead. Cockpit is cold and dark, no response when moving the stick, and when pressingto get the FMS up the SELCAL comes up instead. The NGX slowly starts to dip, and drops nose downto the ground. Battery- and standyby power is on, but panel is dark.This happen both when loading through RC and in FSX directly.Anyone else experience this, or know a fix?Geir J.

Hi guys,When trying to change the cruise altitude on the FMC, on the CRZ page, FSX / NGX always freezes, andI have to crtl-alt-del, and shut it down. Did not happen before I installed SP1b..Anyone else have this? Could not find it mentioned before..Geir

Have to ask you, what visibility stuff are you referring to? Just got FSUIPC, but can't see anyvisibility options..?Geir

I seem to remember from the days I was flying FSX only, no RC, ASE or FSUIPC installed, that I would get "run over" by AI from time to timethen as well.FS simply do not freeze all AI's when on collision course. This was not a problem with FS9..

Have to agree with you there :) At least, the option to choose from which effects one prefers would be nice :)HUD on could f.instance automatically turn off windshield rain? Or one could choose in the FMC menu..

Thanks :) I assume that is the payware version then of FSUIPC?

Hi folks,I appreciate any feedback on this, and also I've seen Pete around here so great if I can get youropinion on this :)I've been using ASE (647 now) and an old version (4.152) of FSUIPC for some time, as this versioncame with RCV.4. I never had any s-turn problems which I read about others experiencing withthe PMDG MD-11 (and other). However I did have the annoying problem of "lagging" in RC,causing such delay on approach that airplanes were on the RWY when I was supposed to land.I updated to version 4.530 some time ago, and noticed that my MD-11 suddenly started withS-turns on cruise.. Bad ones! I also had strange wind-shifts. After testing to for some time, I revertedto 4.152 version, and the problem was gone. As RC was still slow, this was fine.Some days ago I read about version 4.7 being out, and the lagging problem should befixed now. I tested it, and the difference seemed remarkable! I was happy as a fish on arainy day, but moodswings appeared as soon as I was on cruise. The S-turns were back...Testing a little more, and returning to 4.152 definitivly removed the S-turn problem.The lagging is back however. So now I am at flying with 4.152, and turning of DWC beforelanding... Well, it could be worse :) Pete, you may already know of this, but in case notI finally found I should take the time and post it. It actually seems that the old 4.152 versionI have either supresses the S-turn problem, or the newer versions have some role in them.Any thoughts?Regards,Geir J, Norway

Great, thanks a lot Christian :)I searched the forum before posting, to see if there already was a thread on this, but didn't find anything.. Geir