I’m german, I’m doing the same ^^ However we had the same last year, an important update missing due to the summer break when nobody was at work. Delaying such an important update into August AGAIN will likely lead to the same problems… again.
No no no…we aren’t just gonna deflect put this on “quality of beta testers”.![]()
You are still dealing with PAYING CUSTOMERS of this sim after all, but ok.![]()
Sometimes it’s not a bad idea to look in a mirror, sit back, take a deep breath and repeat
I’m a customer!
MSFS is a product!
I’m a customer!
MSFS is a product!
https://leadership-outfitters.com/wp-content/uploads/2016/06/Man-looking-in-mirror.jpg
Maybe you should say “Paid” customers. Millions of us have already paid for the GAME and like other games, the manufacturer will add free updates whenever it fits the marketing plan. Like other GAME manufacturers, it is a product for profit, period.
As a Swiss working a lot with French collègues, I must say there is some truth in this (don’t forget their 35h week)
. But I still love their culture!
Whatever makes you feel better at the end of the day …
Very disappointing that MS/Asobo listened to those people on these forums that requested fewer sim updates. This will slow down progress to a trickle. I mean I understand pushing a particular sim-update back to allow for a longer beta period, but reducing the frequency of sim updates will do nothing but slow down progress. If they kept the same pace of progress, bigger gaps between updates simply means that there will be more to test, so the time for testing per code change will remain the same.
Exactly.
Personally, I’m disappointed. I know PMDG and Asobo have ID’d the sim rendering issue that causes the PFDs to flicker occasionally in the 737, and the fix is supposed to come with SU10, which now isn’t expected for almost 3 months.
Similarly, PDMG (and Fenix and anyone else making modern planes …) has been waiting for the weather radar API implementation so we can get working WX Radars in our planes. Summer time is a very active weather season in North America, especially in the late afternoons and evenings as the heat of the day powers up the atmosphere, and those of us who like to fly with live weather sure could use some in-cockpit weather imagery. But that now gets pushed back to late August as well.
And while my sim has personally been stable, I have very definitely lost performance - 10-15 fps in most circumstances. It’s fine to go from 70+ fps to 58-60 fps in the air at 10,000 feet, but it’s NOT good to go from 45-50 fps to barely 30 fps at standard, non hand-crafted airports on the ground.
Personal Comments
This earlier post explains why I believe regression is part of the operational reality for what is effectively a Software-as-a-Service model; what Jorg referred to in the last Q&A as Gaming-as-a-Service.
With that being said, I prefer to see the sim move forward with the latest features as soon as possible, that’s absolutely in alignment with Agile Development - increment, fix, increment, fix. 80/20 wherever possible.
I think so many FS players are suffering from culture shock - waking up to find T-shirts in their wardrobe that MMORPG players have worn down to threadbare for years. Understandable, but part of the new reality.
I don’t believe anyone said officially that there wont be fixes released independent of the updates - all I see there is the assumption that fixes will continue to only be released as part of updates. How do we know that’s going to continue?
Isn’t it possible that with the extended update schedule certain fixes might now be released in the interim? Provided they meet certain criteria…such as a developer product that is useless without said fix? I think we need to find out ‘officially’ how this is going to go and not assume the worst. Catastrophizing all the time is so tiring. I don’t know how folks can just live that way
I do feel bad for the MSFS users with constant problems that have to wait longer for updates and fixes.
Besides the VR window resize bug I’m having a smooth stable sim experience. I didn’t expect the issue to actually be addressed anytime soon or if at all anyway, so August isn’t a big deal for me.
Personal Comments
Jorg and to a lesser extent, Martial’s comments in the last Q&A don’t point to hotfixes. Jorg extended the Flighting window specifically in the hope of exposing game-disrupting bugs just like the last one that caused a whole bunch of CTDs for XBox players. Martial pointed out that even with detailed reports from end-users - if the internal test team can’t repro(duce) the bug, they can’t begin to address it.
First - It would help to see that, to some, Sim Update means fixing what is already there but to others it means both fixing what is already there as well as adding new things. Asobo is doing the second and that’s basically good but the new/updated feature set can create havoc.
I think its good they take more time to get things right but hotfixes for major issues should always be part of the solution (and I believe they will be).
What would help is if Asobo spent some time explaining exactly what they are changing as well as what each option does. I just discovered that those small '3D Photogrammetry Cities" files that come with each World Update are actually there to mask the default install so the PG can show. People do things to their systems (like delete those files) and then make complaints about bugs that are not bugs at all and if Asobo were clear about what does what and how information travels in this sim then maybe there would be fewer bug reports that shouldn’t exist in the first place. The camera system alone should have a one hour instructional video… it would probably stop many bug reports.
If they would test correctly in the 1st place, it would help a lot (im not talking about CTDs, those are harder to track)
How many Times did we got new bugs that were cought by a bunch of testers in the 1st hours of the betas?
Each time, there are very simple things that are screwed, that are obvious after a 5min flight ![]()
I’d like to see a very frequent bug fix cycle and then feature updates split by the main module. Is should be every week or two for small fixes.
These monolithic realeases are tough on developers and QA.
Why does an airplane fix need to go with a weather fix or new weather updates? Why are the menus tied to flight dynamics? Etc.
Actually they aren’t always tied so tight. The menu changes for Top Gun was small. World updates are also independent.
I’m quite happy with this, the sim is running really well for me at the moment. But I appreciate that it isn’t for many. This should, realistically be addressed by hotfixes, rather than having to wait months.
I don’t understand this, either.
The aircraft are independent modules and, presumably, developed by aircraft-specific programming teams. Why can’t their small fixes just be done ad-hoc and released whenever they are ready as an independent update download?
I was frustrated by the number of cold & dark fixes to the default PC-6 variants that the patch notes, quite literally, said “Attempted to fix…” — attempted?! Anyhow, I’d reported in SU8 Beta they were not fixed and/or had changed, but those issues were neither acknowledged or addressed before SU8 final. They weren’t addressed in SU9, either.
Why can’t these just get handled by whomever developed the aircraft and pushed when they have been fixed independent of an overall SU?
Do anybody know if we will get beta testing for su 10?
Yes it was called SU9 … Bwhahahaha .. sorry just injecting a little levity into the fray. ;p
This might be the case for a lot of users who join the beta but it’s certainly not true for everybody.
Personally every BETA I’ve participated in as well as a bunch of my friends thoroughly test aspects of the release notes where we feel we can contribute and unfortunately the past couple of betas the points we have tested and reported on very thoroughly as well as steps to repeat and reproduce the bug/regression (be where the release note testing point is either not fixed as it says, or has regressed) were sadly ignored and released into the final build.
The BETA could be 4 weeks or 4 months but if Asobo carry on their trend of not taking feedback on board and acting upon it then it really doesn’t matter how long it is.
I posted so many bugs on the release day of SU8, that I used up my allotment of daily new topics.
I had more bugs to post, too. That irritated me so much, I lost interest in the whole affair.