If you follow the SDK contributions, there are always new problems that are not easy to work on, so I wish that Asobo immediately stops all work that is not important, such as innovations that are desired by the community, and uses the resulting manpower for this to correct it to make it easier for the makers to implement their work wid mods, traffic scenery etc. in the sim. A lot is set up by the people of the community, which ultimately works poorly or not at all because there is no support from Asobo or microsoft. I have no idea how big such an Asobo development department is, but I am convinced that everything that has been straightened out by the members of the community so far would not have been managed by Asobo department in 3 weeks. Thatâs why I think itâs important that things like reasonable usable folder structures for the community folder or the possibility to use several mods for one thing with possible installation routines are very important because the community is able to do a lot more than Asobo ever could, which the time shows so far! And thatâs why Asobo should take on the whole topic and support here in order to get things off the ground faster, because ultimately Asobo also benefits from the fact that the community is concerned with things like the AP ben G1000 and 3000 the A320 Mod the Beachcraft Mod the Dreamliner Mod that takes care of tall trees etc. I would like if we started here with a wish list of those who have problems with their work for the community because Asobo / Microsoft is missing basic things and this wish list is processed in our favor so that results can be achieved quickly! It doesnât matter to me whether one uses google images or something absurd, but maybe simple things that Asobo would have to do to advance the work of the masses. Maybe a moderator can help to implement such a wish list here, which is also accepted by Asobo and the responsible parties.
Yes, I agree with you, you should get nice weather, but it is a question of the use of resources and profit that I am based on here, I prefer to let 5 employees work on basic things to enable 100th community people to implement mods and fix bugs, which then happens relatively quickly is now as 5 people to set something to change what actually represents the situation of individual users. The basic things in this Sim are more important to me than the almost perfect weather.
generally they need improve (they know exactly what need to improve) things that can affect next development. I mean that basic things like aircraft performance, functionality, instruments functionality, Flight and FPL handling and weather system need to be solved first. Of course, Sim problems with CTD as mandatory but if I see history of users problems, we see clearly that some users donât have basically CTDs or install problems, I expect users do some problems with Overclocking, performance updates his HW. Then they can build on this base next system - better improvement of SDK, new things to it. I see this as long history development steps. Simply if basic things will not work as expected, update of other things can be build over errors and this can be never ending story.
I also didnât talk about the basic things, the effects have, I mean rather the things that are on the wish list but are not important for the smooth operation of what is now available
if i were them i would mainly work on stability and hardware compatibility first. Those can include not only debugging but also dx12, ray tracing, dlss implementation etc.
Then focus on core game components like scenery, deluxe & premium planes, weather etc.
Third may be changes or improvements or revamps to the game itself.
While i can accept a Steel suspension bridge looks like a normal bridge (viaduct) i cannot accept the INOP. stuff on 787 etc. (do not misunderstand me, i am happy with it and i know they are going to fix it in the future). New Xbox coming and i am sure if not ASOBO, Microsoft wants to see MSFS2020 on new Xbox consoles as fast as possible. (I still believe Microsoft is behind August release, since early news showed MSFS supposed to be released in december)
Just the opinion tho, i am highly satisfied with the work done so far knowing ASOBO as a company behind this and that it will be miles ahead of other sims in 2-3 years.
Resources need to be assigned to get the product that the customers were promised and this is why the highest prio votes are for fixing issues that should not have been in a polished product at all.
Nobodyâs talking about ânice weatherâ, people are talking about not working weather, broken FMS, Autopilot issues etc.
Also I donât understand how people can be so confident to think they know best how a big company should do software development.
Itâs not like you have 100 equal monkeys that can do any job that you assign them just because someone in the forum wants to have this priority. Each developer has a different skill set and knowledge of the product.
Please donât assume that I pretend I know how big software companies work. I only expressed that it makes sense to support hundreds of members to improve a product in a relatively short time frame than with probably much less staff at Asobo to do everything alone and to work off one after the other and nothing else.
Perhaps youâve heard of a win-win situation before
Everything the members of the community do, and they do it very well! Asobo has not need to do it, so a way should be found as soon as possible to implement the good of the community sensibly!
This is where I donât agree.
I want to have a polished product at some point since I donât want to pay third parties (even donationware/freeware should be paid if itâs good work) to do the work I paid initially for the product already. Also there are plenty people who donât bother searching forums, downloading freeware/payware etc. and still deserve to have a complete product they paid for.
Sure, extending the SDK is one of the priorities. But nobody said theyâd stop working on the SDK just because there are highly ranked QOL requests that the community wishes.
Usually people working on the SDK are not the ones that are able to fix your weather, port it to DX12 etc. As I said, developers are assigned tasks based on their area of competence.
Alright doc, letâs make some assumptions then. Letâs assume that they spend their time and energy working on the things you think have more value, for the reasons youâve established. Letâs say they put everything aside and work on the SDK (as an example), enhance it as much as possible, document it fully, etc⊠Good. Now we have a documented, âfaultlessâ SDK that everybody can use if theyâre into modding stuff. So people start writing a ton of mods to make the game âbetterâ. Then, 3-4 months down the road, after all these people have spent THEIR time and energy making things better, Asobo finds that there are some thing inherently wrong right at the base of the code. They could fix this, but it will break 90% of the mods, because by fixing those things, it screws up the SDK. Whoâs gonna be in a win-win situation then ?
But thatâs exactly the current situation! and if nothing is improved and standardized here that is usable for everyone, sooner or later it will come down to it!
Who knows now whether the mods and things that have been done so far will still be running in 3 months because something has to be fundamentally changed?
Nobody. But whatever Asobo builds into the vanilla product, theyâll be updating whenever something structurally changes.
Making everything moddable (with long-term support to avoid community backlash when deprecating/changing SDK features) is a vastly bigger job than, letâs say, the most important 50% of a game.
Also weâre not even a month after release. Everybody expects the first mods to break soon or be simply (hopefully) made useless since Asobo already includes the modded features into the product themselves.
Currently most mods (apart of addons like liveries and scenery) are rather workarounds based on the existing issues and not intended as long-term improvements.
We all hope we donât need a light fix, an fps fix, ten mesh-fixes, etc. forever. They are just buying time until Asobo comes to these issues.
That is why the way for the future must be prepared now. e.g. At the moment I donât see the need to remove the âstart buttonâ at the beginning or to install an aircraft de-icing system in the SIM. Other things are more important! Of course you can vote, but you are surprised when removing the start button gets ca1500 votes and basic things that do not work get no votes! Something is not going right! I suspect that it depends on who the user is here. The people who bought a sim here for the first time probably donât care whether the AP works or that people who work on mods think how they can always get an even more realistic aircraft - these are the people who want de-icing systems, cars with taillights, or the like the tower of Pisa is crooked again.
@coppersens I donât know what you used before FS2020, maybe Xplane like me. Maybe you know the Zibo Mod from there that is a prime example of how it should work for me! and to your statement that Asobo is already working on integrating the things that are currently still being implemented via mods, I can say with confidence that Asobo will never manage to implement something like this in the sim on its own! That didnât work with Xplane either and the Zibo mod is still as popular as on day one
I donât think this is a binary situation. Iâm assuming Asobo is split into teams, each doing their own part. Itâs also not easy to just grab say an âautopilotâ developer and put him (or her) on the SDK and expect miracles.
Besides⊠isnât this all kinda pointless? Theyâre gonna do it their way anyway.
You are making an assumption that the Asobo team all work on the same thing. They donât. Some maybe focus on weather , some maybe SDK. Itâs like building a house. You have carpenters , framers , Finnish carpenter, plumbers or house inspectors.
All these people work on building the house and focus on one type of job.
Sim is less than 30 days since release.
