marsman2020

1 hour ago, jarmstro said:

This sim taxes your hardware like nothing else. If you have CTDs with a vanilla instal and a clean Windows install it's likely your hardware isn't up to the job. Cheap PSUs, blown caps and cheap ram are  likely candidates.

Victim blaming BS.

There have been multiple CTD issues acknowledged by the developers (the VFR map bug, the SimConnect bug, the time they broke all 3rd party airports sold on the official MSFS Marketplace, the bug that was introduced with Marketplace aircraft for 8 weeks in the fall, among many others).

Users have found geographic locations that cause a CTD every time they fly there.

There are likely many more that haven't been acknowledged or fixed which is why CTD are so high on the bugs & issues list and continue to accumulate more votes.

I noticed a terrain defect near KMHV last night that I could have sworn was fixed in WU3.

Need more data to draw a conclusion though.

10 minutes ago, kaosfere said:

A hotfix is usually meant to address breaking issues only.  They do not come without risk, as they are necessarily done outside the usual development process (though a developer should have a documented hotfix protocol too).   The more you change in a hotfix, the greater the risk of inadvertently breaking something but, more importantly than that, the extra time it takes to fix non-breaking bugs means breaking bugs go even longer unfixed.

The escape issue is annoying, but it's not a game-breaking bug.   CTDs using WASM modules -- which are not exactly an obscure part of the sim, they're one of the two ways of delivering the code for a plane, and the one that the commercial developers are favoring -- are indeed game-breaking.

Hopefully that will help you see the logic behind what was fixed here and what wasn't. 🙂

Personally I would consider not being able to go to a menu and change a setting without messing up your flight afterward to be game-breaking, but I can see where that definition might vary.

I think it's a little unfair to criticize the developer of the GTN750 for charging for some advanced features that none of the stock Asobo Garmins have.  Especially since there is a free version, and it's the first new ground-up Garmin in the sim.  They have also done us all a great service with the awesome free GNS530/430 mod, which many people have commented favorably on.  And it's clearly labeled as a Beta at this point, without final features or pricing. 

I really appreciate JF adding the integration as the first third party aircraft maker to do so.  I think the easy-to-use touch interface is a great companion for the also easy-to-use steam gauges.  Best of both worlds. 

34 minutes ago, Twenty6 said:

What is RTC?

"Real Time Cinematic", the cinematic showing your aircraft taxing to the runway which shows when you choose to start hot. 

I really enjoyed the updates to the turboprop behavior that they showed in the Q&A this week, as well as the flight testing of the C172, which is fulfilling something that was promised in a prior Q&A in response to the long thread on the official forums about the flight model.

Some of these regressions like the tree draw distance, water climbing up hills, etc are particularly frustrating when it's clear these aspects were better at launch. 

I appreciate that Sebastian and Martial are busy and any time they spend on Q&As is time taking away from managing/overseeing things like arranging flight testing or fixing turboprop logic. 

It might not be the most effective use of their time to spend a lot of additional time prepping for the Q&A vs doing other things to move the sim along.

I guess the one suggestion I might have (and I should probably find an appropriate venue to voice this vs just here on AVSIM) might be to create an Asobo "counterpart" position to Jayne.  Someone who could dig into some of these technical things and provide details, read the forum threads where needed and make sure everyone is on the same page, spend more time reviewing the Q&A questions and marshaling the technical answers ahead of time, without taking the leadership away from doing their roles.  Call it the Community Technical Liaison or something.

Every.  Single.  Update.

Thanks WT team for the prompt update!

On 4/13/2021 at 3:16 PM, EvidencePlz said:

In MSFS 2020 The only way you can have a point A to B flight reliably is if you hand-fly the plane, and this is valid for not only the default but the third parties as well.

I'm the first one to point out many issues I perceive with the sim but... I've flown 1/3rd of the way around the world so far, much of it with the Asobo AP on, with only a few instances of issues. 

There are certainly situations where you can get the AP messed up to where it won't work anymore (mostly if you put it in an off-nominal situation where it pegs the trim for some reason) but it you fly at sensible airspeeds it will climb, follow a magenta line, and descend OK on the GA aircraft.

This is not to say that there are not issues with the AP, but in many situations it will work fine.  I do think it has improved since launch in it's general stability.

29 minutes ago, Bobsk8 said:

The setting is visual only, I believe. But that isn't true at least in 3 different aircraft I have flown. As the ice builds up, airspeed goes down, and finally with full power, you stall. Go up to Canada or Alaska, and see for yourself on a cold day. 

Agree the setting is likely broken, many people have reported aerodynamic effects on "visual only".  This is why I am suspect of any 3rd party aircraft that don't show the visual effects of icing (since the aerodynamic effects may be present even on the "visual only" setting when no visuals are shown!)

Just now, RW1 said:

Again this thread is about the MSFS and Kaspersky AV. Most comments here are pointing out the obvious and providing useless information irrelevant to the problem.

I provided a solution and independent test data to back it up.  Last I checked you're not a moderator, thanks.

4 minutes ago, RW1 said:

Don't think this thread is about whether people need AV or not?

I didn't say anyone should go without AV.  I said that the AV Windows comes with for free (which doesn't break MSFS) is just as good as any 3rd party AV, such that there is no reason to run resource-hogging 3rd party AV anymore.  This has been demonstrated through independent testing since before Windows 10 even came out.

So if the Exceptions in Kaspersky aren't working, just uninstall it and turn on Windows Defender, problem solved.

I wonder if MS will "subsidize" the ATR as an "Official MSFS Plane" so it's like $9.99, or if it will have the full Aerosoft type price?

(Personally I think they should make it cheap as a partial compensation for everything we will have endured as unpaid Betas testers of the overall sim by the time it comes out)

Windows Defender offers just as much protection as Kaspersky or any of the 3rd party AVs.  There is no reason to clog up your PC with any 3rd party stuff these days.

https://www.av-test.org/en/antivirus/home-windows/windows-10/february-2021/microsoft-defender-4.18-211115/

1 minute ago, fogboundturtle said:

because the issue is that we are not GPU bound but CPU bound. You wouldn't get more FPS using DLSS.

I'm GPU bound in many situations, but I don't think my AMD card will get DLSS anytime soon ;).  Hopefully by the end of 2022 we'll be able to actually buy GPUs again....

Not all default planes are bad.  The ones with community mods to fix them are pretty good! 

2 minutes ago, HiFlyer said:

From the Working Title Discord:

@everyone Unfortunately a change made in today's update seems to break a key part of our file loading for the G1000.   This is causing a broken MFD, and it may affect other bits of the Garmins, too.  I've sent a query off to our friends at Asobo for some more information/guidance and we'll get things straight as soon as we can, if we can.  But there won't be a release for these tonight.   We'll keep you posted.

🤣

1 hour ago, Noel said:

addressing a multitude of issues for example mesh spikes, graphic artifacts in clouds

Ah yes, they addressed the issues that they created in prior updates in the updates... Great job Asobo.

Reminds of some coworkers I have had who make a bunch of dumb decisions, create a giant problem, solve the problem, and get all kinds of accolades because people somehow forgot that the problem was their creation in the first place...

Updating the packages doesn't actually solve this, people have received this message even after updating them.

This is likely tied to server updates ahead of the world update tomorrow and will probably go away then.

Recommend choosing "no" to this prompt (which turns off your data settings in the menus) or your logbook might be deleted.

2 hours ago, bobcat999 said:

Hey!  I missed the latest official response from Asobo on this in the really long thread over at the official forum.  It was a few hours ago though.  Response number 613....
 

  Taleboules2146       Community Support         12h

We’re sorry to hear that you’re having trouble issues with the logbook.

We are currently investigating this issue.

So, I am glad they are on to it so quickly.

Meanwhile, in other news on the Asobo Facebook page, Selmar has won the internal Asobo chess championship after they played a tournament of more than 30 games.  Well done Selmar!  👍

Sorry if I am repeating old news here - I am just making sure we have preserved this information somewhere in case it gets wiped-out, like things accidentally do sometimes.

 

This is what will happen:

The community will keep asking about this problem, which has existed since around last Thursday.

The MSFS forum community managers will say "the team is looking into it".

There will be no response from the team.

The update will come out on Tuesday and the error message will stop.

The MSFS forum moderators will close/lock the topic as "solved".

There will never be any way to recover the lost log book data.

If we upvote a QA topic on how this can be addressed/avoided in the future to avoid people loosing progress, the question will be totally ignored by Jorg et al.

This will happen again at another world update, just like it happened back in February and was never replied to/addressed.

22 minutes ago, ryanbatcund said:

Looks like the turbo arrow would win above 14K ft or so.  Just looking at the airspeed indicators- they look very similar.

The non-turbo JF Arrow barely makes it far enough on the airpeed indicator for the needle to make it to the TAS compensated section. Manifold pressure starts to drop as soon as you're above sea level.

I don't see how the Turbo would be the same speed. 

1 hour ago, Dominique_K said:

They have done some work on a Texan 2 if am not mistaken for the USAF but didn't release it to the public.

I suspect releasing to the public anything related to an aircraft that was modeled for an official military simulation customer might be very difficult based on comments MilViz made in their Twitch stream a few months back.

There are issues related to export control and intellectual property, so once a given team has seen that restricted information I would imagine it becomes difficult to get "the powers that be" to sign off on a public version of the same aircraft.

I did the community endurance race across Australia last weekend which required that we all empty our Community folders and I had 2 CTDs despite restarting the entire sim at every refuel stop to try and keep it stable.

In the SW121, which has the portrait mode version of the G3X (non-touch).

A number of the Garmin 'bugs' have their own keyboard definitions (in the autopilot and NAV radio section of the keyboard bindings). The heading, altitude, radio tuning, and VOR CRSes. 

But there is no way to enter ICAO codes with the keyboard or anything like that.

If you just want to zoom around in something with a Garmin, join GotGravel's Discord server and participate in the open beta of his new Vertigo mod.  VL-3 airframe with a PT6 turbine, loosely inspired by Mike Petay's Turbulace.  0 to the flight levels faster then you can spill your cup of coffee in your lap.  And it's free.  No need to pay $20.