I don’t think they think the issue doesn’t exist. It can be very very hard to recreate a bug. Give them time, information and videos. Eventually they will find it.
Sure they said maybe you’re doing something wrong with live time instead of weather. 1) They saw it happen and 2) it would be a nice and easy ‘aha’ moment. But that doesn’t mean they don’t believe you. Hey Seb tried to recreate it for 5 hours straight.
Being one among others documenting the exact problems with LOD and Trees for months, I was indeed quite puzzled they were answering as if they were just discovering there could be an issue with LOD and Trees. It is especially even more troubling to me that IIRC, in a previous Q&A the same topic was brought to their attention with the same reaction.
For those wondering, here are a few of the LOD and Trees reports I’m talking about:
First I’m glad they’re making it a 1st class citizen because I didn’t think the mere 44 votes would do ( [VR] Dev Q&A and Feedback Snapshot: please make a VR only category ) given the 265 votes for Trees are not even sufficient to make in the radar in 4 months. But on the other hand I can’t help thinking there is something wrong with it, like the LOD and Trees topics.
TL;DR: The entire chain of IPD/ICD projection matrices must be cross checked with at least WMR OpenXR and SteamVR OpenXR drivers (the 2 most used) in addition to offering a user adjustable override (scale + bias factors).
But I don’t understand Martial’s answer about the “Brightness Slider”. I’m not certain he was joking or seriously not considering this an “important” feature. In my opinion (biased opinion being a developer too), what we really need in VR is not a “brightness” slider but something different:
TL;DR: solutions for rendering EFIS screens with high resolution even if you don’t have a G2 and a 3090.
PS: These VR topics I’ve listed above are prefixed with [BUG/FEATURE] because they are not only reporting a problem but they are also offering solutions which are readily implementable with minimal effort and time (all things considered of course).
AI Traffic and Liveries
I believe there is a disconnection again between language and facts. Jorg is telling us it is a simulator for simmers, yet, Microsoft is trying to control and shape everything for us, like the AI traffic liveries. Of course it will be hard for Microsoft getting all airline companies licensing, because it has always been. Long time developers like me having worked with ACE studio back in the day do know airlines are reluctant, do remember the American Airlines threats, do know the PT fiasco in trying to impose the community paying royalties for a famous airline livery…
This is not new, and this is why there is no commercial offering for this but a great choice of freeware libs of liveries and models for all other simulator but FS2020. Why wanting to control this (in addition to sandboxing 3rd party devs) instead of just creating what is necessary in the SDK for just helping these freeware authors doing the same libraries for FS2020?
I have no doubt there is some value in the actual FS2020 SDK approach for the XBox version, and this might suits well the need for some airliner developers on the PC version as well, but to me, and I’ve been working nearly 20 years in this industry, I believe what makes a simulator for simmers is 3rd party developer add-ons, not just the simulator itself.
Bugs and Repro
I’m glad to hear they are trying to repro some of the reported bugs, but wouldn’t it be just easier to get started with a proper logging system?
I might have wrongly understood but didn’t Sebastian told in the Q&A they do have a replay system already but it is only used for their Video capture needs where it can help them producing videos without any stutter?
This begs a question: we were told in previous Q&A the screenshots and videos they are presenting are always from the simulator version we also have, not a future version. However it has been brought a few times: some were wondering how do the official videos are showing stuff we can’t repro with our versions, such as building/terrain draw distance in ULTRA without stutters. The answer has been so far they’re running it on high end machines, but isn’t it just because the videos are recorded from a replay system designed to eliminating stutters instead? I’m puzzled with this one?!
I’m glad you’re mentioning the dedication of the simmers and our involvement with FS2020 and the forums. You seemed genuinely surprised by this and this is not the first time. This is why it is important to also see all I’ve written above not as a rant at all either.
With your strong commitment to a “simulator for simmers” it is also expected you get feedback and demands with a high degree of quality and detail. This is a driver and what also defines to me what is the simmers community and why I’m glad working in this industry for the last 20 years!
I believe you’re doing a great job in trying to not only assemble the most prevalent questions, but also with your ability to pick some niche questions sometimes buried in the chat or in these forums.
However it seems to me, in every single Dev Q&A, they’re spending maybe 1/3 of the time talking about the same things they’ve already said before, 1/3 telling us how great it is working with 3rd party devs, and 1/3 telling us about new things (actually I enjoy a lot Sebastian’s talks, please don’t stop doing!!). This is most likely what the Q&A is all about, maybe, but I can’t help on the other hand also having the feeling there is a complete disconnection between the decisions making process about resolving the issues, and the daily work you’re doing here with the community with the addition of the thousand of hours spent by the community reporting the problems and making suggestions.
All this (and more) makes me feel like the Zendesk reports and the topics we are creating for reporting and documenting bugs are not worth a dime at all and we’re just loosing our time, and I’d like some reassurance about this.
Not sure that they talked about it or if it was in on a list they put up, but one thing many users have been asking for is some sort Sim Rate indicator. You know when on a long flight over water and we use CTRL+R++ to increase the rate to get to land faster.
In Flight Sim Features | Asobo Studio in one or two of those video, they accelerate the sim rate and on the top right of the screen it shows something big >>5 indicating that they are at five time normal rate.
Was that superimpose with video editing, or will that be added soon? Hopefully added soon.
I know that many people say to press CTRL+R± many times and then CTRL+R++ twice and that will put you back to normal rate, but that’s a pain and it would be nice to know how much you have accelerated the Sim Rate.
Sometimes, that’s what it is. It’s harder when you’re on the dev team. You know EXACTLY what to do. You know the beaten path through an application and you follow it. Users, on the other hand, will do all kinds of messed up things that you would never even think of doing and trigger a bug that only occurs in that very set of circumstances that you could never have planned for.
I don’t really think this is necessarily the case here though. It’s happened at various times for various reasons for different folks. My live weather was working fine. I restarted the sim after a flight to get the new update (the last update in November). The live weather bug started at that moment for me. It never worked again after that update, aside from using the workaround.
I feel his pain, because I’ve been in that situation a few times over the last 27 years as a dev trying my hardest to reproduce a bug some user was seeing but not being able to reproduce it myself. Every time, it ended up being some obscure bug buried in the code that caused an error under a very specific set of circumstances that couldn’t have been forseen. Sometimes it’s user error / input that triggers it, sometimes it was an external event. But in all cases, it was ultimately due to a bug in the code.
I said it before and I’ll say it again; what I love most about this sim is the devs’ willingness to co-operate with the community, interact with them, and continuously make improvements in this sim.
It’s such a breath of fresh air compared to previous “take it or leave it” types of software development projects. The fact that we can call out an issue instead of having to live with it or work around it is such a relief.
Agreed with all points. And that logbook popup should have no place in a flight simulator, be it a home desktop, commercial, or Level D. I am more than willing to trade it for the Press Any Key feature .
One take away I had from that Q&A session concerns bug reporting. I am not claiming the following is never done, however it is not always done.
If the purpose of filing a bug report is to have the bug fixed, then, I suspect as much relevant information as possible would be of great use. In particular a detailed description of exactly what the issue is and the necessary steps to reproduce it. I see many posts concerning bugs that, while no doubt accurate and real for the person experiencing them, are not as clear as they could be for someone who was trying to troubleshoot the bug- through lack of detail given as to how to reproduce the bug.
I am not trying to cover for the devs here, nor do I want to diminish any case where this has been clearly done, yet there still seems to be confusion about the bug’s existence. However I suspect it may speed up the whole bug fixing timeline if every bug report was as detailed as possible.
It did seem as though one of the devs had created the code for the popup at the end of a landing challenge, which is a more appropriate place for it, and then someone has decided that it would be a good idea, perhaps in the spirit of recycling, for part of that code to be re-used for every flight.
I’m with you, this type of screen would be more appropriate at the end of a level of a computer game and there should at least be an option to suppress it.