AJZip2

I don't think for one single moment that I will be able to repeat this but: After multiple attempts to get an FPS flight of the E-170 happening at all...and that is after uninstalling everything to instruction, including the WASM clearing app, and re-installing to instruction now 6 times (!!)... I have repeated all the same steps to attempt to get this thing to fly properly at least once in 7 times of trying. But this time, it was with a vow that if/when I got an inevitable 7th failure, I would delete the E-170/175 from my system and absolutely not try to reinstall for at least another 2 years. Well, maybe it was the white heat of anger that warmed up the hot PC even more; maybe it was the multiple blows of fist against keyboard; maybe it was the increase in blood-pressure medication to the maximum allowable for an adult male; maybe it was the threat by MrsAJZip of the consequences of "one more ridiculous outburst from a grown man that ought to know better!". And, as we all know, Einstein is quoted as saying that repeating exactly the same steps and expecting a different result is the mark of insanity (or something along those lines)... Anyway - I DID repeat those same steps for a 7th time... and I DID get a different result! This time I DID complete an AP flight from EGPD to EGPH, climbing to 14000', then descending - all in line with the altitude profile - down to a perfect ILS approach, only needing to switch back to manual when at the threshold. Everything worked!! And because I wasn't looking through a red mist, and because the autopilot had everything in control, I could actually spend time switching to external view - and this aircraft is indeed a thing of beauty!!! As I said at the beginning, I don't think for one single moment that I will be able to repeat this - but it does, maybe, make the years of waiting worth it... 😁

I'm afraid I'm abandoning this for a while until there are some up to date videos of how to get the data link communicating, etc.. Can't waste any more time on it at the moment.

Re-deleted the package and purged the WASM and then did a full reload after wasting a few hours this morning with the E-170 not responding to anything. Hey presto, when I reloaded it, I spotted it was now Version 1.0+Patch1, which is what I presume @longhaul747 also refers to above. And yes - that version seems to work... I'll try another proper flight this evening...

Ah - of course. I should have thought of that. Many thanks - I'll have a look next time I'm on. 👍

Can someone remind me how I activate or brighten the Autopilot button/commands LEDs? I activate the various buttons and it shows on the main screen but the LEDs don't light up, even dimly. I'm pretty sure I've been here before and that there is a twist knob or switch to activate or brighten the LEDs. Anyone know/remember? Just did a quick flight and most everything else seemed to work OK other than poor/offset cursor focus in VR of the MCDU buttons resulting in multiple incorrect letters and numbers being chosen. I'll re-read the full procedures and systems and in the coming days will try to repeat a pretty decent flight I did in the previous incarnation and see if the odd quirks I came across then are now resolved.

Vauable information - thanks for posting. Might be worth dropping a line to the FSUIPC developers (they maybe on Discord or have a direct help line ?).

Have just remembered why I need it. I have a number of Flight Panels configs to use on my Elgato Stream Deck+ so that I can more easily adjust twist switch alt, speed, rate of climb, etc by 'feel' when I'm using VR. Flight Panels' configs all use FSUIPC as far as I know. Might be a good excuse to get a MOZA!! 😉

I'm away from my main computer at the moment and can't think why any of my peripherals need fsuipc. When I'm back on I'll delete it and see what stops. It would be good if I can do away it...

Yes - one of my addons or bits of hardware also requires FSUIPC (can't remember offhand which) and that is the only reason I still run it. If you do need it, it's certainly worth trying the updated version - I don't think it updates automatically. I don't know, but it is entirely possible that the update went in because of a change in MSFS which has caused a clash. You can always delete it again if it screws things up again.

I think you might be onto something with FSUIPC. Last week I had some unusual issues relating to differential braking. Although I was never sure what the core problem was, now I think back I ended up with having to do an unexpected FSUIPC version update amongst the other stuff. Try first turning off FSUIPC and if that solves your issue. If it does, iit would be worth uninstalling FSUIPC and loading up the latest version before trying it on again.

I have no problem participating in early releases, and have willingly and happily done so with this and a number of other products. Being pragmatic, I suppose my only concerns are: whether MSFS 2020 support ceases before a native MSFS 2024 version of the E170/175 is introduced whether even the present MSFS 2020 version comes out of Early Release before I reach my statistical full life expectancy Other than those ponderings, I look forward to 1.0 release - I found the last update quite encouraging.

OK - that's an important result. Did you try the flying the F28 itself again using the same controllers and is that still running OK?

I fly the F70 and F100 quite a bit at the moment and haven't noticed anything unusual about the controls assignments. Just to eliminate a few of the possibilities, have you tried flying the F70 but using your OK F28 profile? If so, did that work broadly OK?

All good again. In the end, I reinstalled the Just Flight F70 and F100 as I'd messed them up when originally trying to solve the issue and it was easier than more tinkering about. Quite why you can run the sim and addons perfectly happily for months and, with no apparent changes or updates to either, it all goes crazy, I don't know. I suppose that's a bit like life in general...maybe it's the darker side of us pushing for more and more realism in the sim! 😄

I'm clearly not alone...this is what Google returns with a query about possible conflicts between MSFS2024 and FSRealistic: "Known Impacts on Cockpit Views Zoom and Height Overrides: FSRealistic has its own internal camera telemetry. If you adjust your default pilot height or zoom settings within the MSFS 2024 options menu, FSRealistic will often override them or cause the camera to "jump back" to a zoom level of 50 upon certain keystrokes. [1, 2, 3] Broken "Reset View" Command: Running FSRealistic can break the native MSFS "Reset Cockpit View" function. Attempting to center your view can cause the camera to lock into an incorrect, offset, or bugged physical coordinate. [1] Eratic First-Person Movements: In certain complex or third-party aircraft, FSRealistic's logic can conflict with the sim's bounding boxes, causing the camera to drift into bulkheads, ceilings, or glitch out during tight turns." Clearly, this doesn't happen all the time to all the users (and didn't for me until just), but worth knowing that they are possible clashes in some circumstances...

Yes - as you say 'the usual suspects'! I'd covered most of those - and ref all of the peripheral checks, yes I'd done those too. I'd checked all the updates - but I what I HAD forgotten about were the program addons. I turned all of those off one at a time...and when I turned off FSRealistic, all of a sudden I could see the runways again!! I've tried a number of aircraft types (GA; Tubeliners; Military) and all of the ones I have tried are now OK . The only one where I still have a problem is the Justflight Fokker F70/100...but those were the aircraft I was flying when I first had the issue and I made a number of settings changes that I now have to reverse. So I think it's basically sorted - I can live without FSRealistic for now and will do a bit more research to see if it's an issue other folk have had or whether it is just me. That said, why it should work just fine all last week and then not beats me! Then again... 🙂 Many thanks @Kristofski for your prompt reply and wisdom 👍

This is driving me crazy. I am a long time user of MSFS2024 both in 2D and VR and, for all types of aircraft, it has started to drop to the instrument panel view within a few seconds of booting up in the normal take-off pilot view. I boot up, start a new flight, it shows me the normal default pilot view and then drops down to where I can see the instruments but not the runway - it's as if the seat's dropped 5-6 inches. I've searched all of my settings to make sure there is not a spurious 'IFR' view setting or similar attached to any of my Hotas controls; I have tried different aircraft - from a 737 to a Cessna 172; I have tried different hotas profiles; I have disabled the Hotas controls one at a time to see if that makes a difference...it doesn't. I've done a 'Repair' of MSFS and that made no difference. Any ideas?

Definitely this ^^^ I had two cables in my bits drawer and first try picked the wrong one The VD info panel in the headset reported it as USB2 and the results were poor. I swapped the cables and the VD panel now reported USB 3 and the resulting visuals and smoothness were very good.

My go-to headset is the Pimax Crystal Light - but I do have also a Quest 3 that I use for no-cable stuff and as an emergency MSFS2024 backup in the event of the Crystal Light failure (although nowadays this rarely happens 👍 ). I've always run the Quest 3 through the splendid wireless Virtual Desktop. In terms of running the Quest 3 through VD in MSFS2024, it has always seemed a decent fall back if ever I had to sort a repair or replacement for the Crystal Light. However, in a straight A/B comparison, I would always put the Crystal Light back on after using the Quest in MSFS and immediately go 'Wow!!' So I thought it worth a try with the new Beta version of Virtual Desktop, linked with a decent USB3 cable. It took a bit of messing around - and Norton Antivirus REALLY doesn't like it...had to disable that to get the Quest boot up - but eventually achieved a pretty reliable and repeatable boot up of the Quest through the VD Beta link-cable. I then started doing A/B comparisons with various tweaks of the VD Beta settings (especially resolution and sharpness enhancement). This evening, I found my ideal settings - the resolution up from default 100% to 125%; sharpness enhancement OFF (at first I tried that too and, yes, it does indeed add sharpening with little impact, at my relatively modest settings, on performance. However, visually, the artificial sharpness and associated increased colour saturation looked less natural than having that setting simply turned off). I did a take-off and short flight in the Crystal Light back-to-back with the VD Beta Quest 3 in the Fenix A320, early dusk, medium cloud. I have to say - there was such a small difference in the two visuals in that particular test that if it had been a blindfold test I don't think I would have known which was which. And the Quest was just a teeny bit smoother!! Remarkable... Now, clearly, it needs much, much more comparison testing with different aircraft and conditions but, so far, count me impressed!! Oh - and one time on boot up, I inadvertently booted up Meta's own Link facility (the cable arrangement is the same). Stutter-fest and unusable at my normal MSFS settings...

It is well worth trying the Virtual Desktop Beta and the Quest 3 with a series 3 link cable. There's another thread here covering some of this: https://www.avsim.com/forums/topic/701081-meta-quest-freeze-rendering-still-running-on-the-monitor/

I agree with the above. My go-to is generally the Pimax Crystal Light but I use the Quest 3 for other stuff and dip into MSFS2024 with it every now and again. And my most recent dip in was trying the Beta version of Virtual Desktop with a decent (Series 3) link cable. It was useful while I was setting up because I kept accidentally booting up the Meta Link in error. Results: Meta Link using S3 cable: Surprisingly poor. Basically not usable at my preferred settings with poor rendering and unusable stutters Virtual Desktop, wireless - no cable: Good. Compared with the Crystal Light, a medium but noticeable, drop in sharpness for, say, instruments and small cockpit text but just as smooth in terms of overall visuals Virtual Desktop Beta with a S3 Cable: Very Good. I was able to increase both the Sharpness and Render % in the VD Beta settings a touch which brought most of the instrument and cockpit text to a very good sharpness and with only one or two displays showing a slight fuzziness (generally red LED displays). Given the choice, I would stick with the Crystal Light - but if that went kaput, I would now use the Quest 3 quite happily while the various makers carry on introducing and de-bugging their new products 🙂

Yup - we do all of the 'Do's' and don't do any of the 'Don't's' in terms of 12v battery health but the clue is, as said above, the actual expectation of 12v battery life. It is notable that the standard guarantee for a 12v replacement was only 4 Years with an option for a more expensive make at 5 years guarantee (and that's the one we got 😉). So yes - they really aren't expecting them to last very long. (And that makes you think...so why don't they warn you the dramatic things that might happen without warning after 4 years - or include a routine battery replacement at the 4-year service, remembering we get all our servicing through the Toyota main dealer??)

Quote from @martin-w post: "On a Honda Civic Hybrid, a flat 12V auxiliary battery makes the vehicle completely inoperable. Even though the car has a large hybrid traction battery, the small 12V battery is required to power the onboard computers and close the main high-voltage contactors. Without it, the car cannot enter "Ready" mode." Also the Toyota hybrid...as I recently found out myself. 5-year old Toyota Corolla hybrid - runs smoothly like a sewing machine; key fob batteries replaced in past 6 months; serviced by Toyota to their schedule, etc etc. I unlocked car as normal with the fob button and WOW!!...pretty much every warning light and alert on the dash intermittently flashing; boot locked and wouldn't open; back doors and passenger door locked. Key fob wouldn't lock or unlock the doors or shut down the system. Only way of stopping it all was holding dashboard start button. This shut down the system but still couldn't lock the door. Basically, full hybrid failure. It was Sunday before a long and important journey - Toyota closed; local garage closed; my car breakdown service didn't cover 'at home'; user manual checked but makes no reference to this. So I Googled it. One post talked about a flat 12v battery doing this. I got the emergency 12v jump lead pack out and connected to the 12v car battery - and the car behaved completely normally. I disconnected the booster pack and shut down the system. I tried to open the car with the fob - but was back to total illuminations and random car locks once more. So I started the car with the booster pack and drove straight to a tyre/battery outlet and got a new 12v battery fitted - and it's been all normal since. There is NOTHING in the manual about this. The thought of this happening at, say, a motorway services with kids now locked in the back of the car gives me the shivers...

Yes - MSFS2024 Repair, of course 😀 Keyboard aim malfunction on my part... 🤣

Go onto the XBox App, choose MSFS2020 and do choose their 'Repair' facility?