5 hours ago, domkle said:

Lazy dev ? Nope, I do not agree at all,  all the great products we have had over the years show on the contrary a lot of ingenuity and dedicated work in the addon cottage industry.

That they are motivated by their business survival in tough times is not something that I would hold against them. Even if I don’t agree much with what they say about a bleak future. That they try to raise an outcry in the public is de bonne guerre even if I don’t think that it is the best path.I call it out with a grin on my face.

Who will have to pay ? I for one and ready for it if Asobo delivers truly innovative flight modeling and air dynamics in lovely landscapes. Jon might be right but Collins avionics is not the alpha and omega of simming. And I want to pay for aircraft made for Fs20, not transported from Prepar3D. Even if it means expensive.

How long ? I don’t know but high fidelity aircraft have never been available at release of a sim, so it wouldn’t be exactly a new situation

Bravo! Totally 100% agree with you!

One of the things a lot of us were asking for is no backwards compatibility. We wanted something from the ground up but asobo still went ahead and added it. Now if there was no backwards compatibility and no tools to port any code, I take it the devs would have to regroup and start over, right? Whoever doesn't want to do that will be left out in the cold.

Why is this any different? Seems like a bunch of devs who doesn't like change are the only ones complaining about not being able to do this or that. I'm sure others will fill that gap. 

If pmdg comes out and says MS is giving us bs and we are no longer bringing our aircrafts to the platform then we can put it to rest. Pmdg didn't stop all development to give us carenado type planes I just can't and won't believe that. 

For the devs whining and complaining, it's time to roll up your sleeves, put on your big boy pants and get to work. 

5 minutes ago, devgrp said:

One of the things a lot of us were asking for is no backwards compatibility. We wanted something from the ground up

Why? what's the gain?

Aside from every other sim having an extra decade to put more into their graphics engines while everything is started from scratch.

8 hours ago, domkle said:

Lazy dev ? Nope, I do not agree at all,  all the great products we have had over the years show on the contrary a lot of ingenuity and dedicated work in the addon cottage industry.

That they are motivated by their business survival in tough times is not something that I would hold against them. Even if I don’t agree much with what they say about a bleak future. That they try to raise an outcry in the public is de bonne guerre even if I don’t think that it is the best path.I call it out with a grin on my face.

I meant lazy in the sense that if they could they would just copy over their old addons into the new sim and hope it works. We all know how that could work out. Coult, ezdok etc crashing the whole sim because of some bad dll 😁. When I moved to XP from p3d I left all that behind and I'm not looking to revisit. 

21 hours ago, Lorby_SI said:

Unless things have been tried, tested and proven to be technologically impossible, I like to think that there always is a way. 

I hope you are right! I'd be happy to eat crow in this instance!

16 hours ago, Murmur said:

Surely, once established that MSFS won't interest you, you will _not_ keep hanging around here to ruin it for everybody else, right? 😉

Sorry to say I'll still be around. It's my volunteer job after all...

3 minutes ago, mSparks said:

Why? what's the gain?

Aside from every other sim having an extra decade to put more into their graphics engines while everything is started from scratch.

Now we have lazy developers complaining about not being able to do this or that because of their need to port old code. 

5 minutes ago, devgrp said:

Now we have lazy developers complaining about not being able to do this or that because of their need to port old code. 

You couldn't possibly be more wrong my friend. Forget 'porting' altogether. It's that we won't even be able to code entirely new advanced features such as synthetic vision, collimated HUDs, fully featured FMS/FMC, et cetera for any entirely built from scratch aircraft.

JSON, XML, JavaSript and Lua simply are wholly inadequate for this kind of fidelity...

Just now, n4gix said:

You couldn't possibly be more wrong my friend. Forget 'porting' altogether. It that we won't even be able to code entirely new advanced features such as synthetic vision, collimated HUDs, fully featured FMS/FMC, et cetera for any entirely built from scratch aircraft.

JSON, XML, JavaSript and Lua simply are wholly inadequate for this kind of fidelity...

Isn't the tbm using synthetic vision? If so how did asobo pull that off? 

9 minutes ago, devgrp said:

If so how did asobo pull that off?

Asobo aren't using wasm.

17 minutes ago, n4gix said:

You couldn't possibly be more wrong my friend. Forget 'porting' altogether. It's that we won't even be able to code entirely new advanced features such as synthetic vision, collimated HUDs, fully featured FMS/FMC, et cetera for any entirely built from scratch aircraft.

JSON, XML, JavaSript and Lua simply are wholly inadequate for this kind of fidelity...

Bill, are you aware of what Asobo is planning regarding WASM? The SDK roadmap? It is all there in the forum and the SDK documentation (I particularly recommend reading a certain post by Asobo from 27th of February in the developers forum). I really don't understand how you arrived at this conclusion.

Best regards

Edited April 7, 20206 yr by Lorby_SI

4 minutes ago, Lorby_SI said:

Bill, are you aware of what Asobo is planning regarding WASM? The SDK roadmap? It is all there in the forum and the SDK documentation (I particularly recommend reading a certain post by Asobo from 27th of February in the developers forum). I really don't understand how you arrived at this conclusion.

Best regards

Please share! 

Bill is not allowed to share that info as it's under NDA

 

 

12 minutes ago, Milviz said:

Bill is not allowed to share that info as it's under NDA

 

 

I am not asking anybody to share anything. But I thought it may be a good idea to point him at a bit of information that he may find useful.

Best regards

47 minutes ago, mSparks said:

Asobo aren't using wasm.

I kinda figured that. Whatever they are using I'm sure it will be available in the sdk, if not the devs will have to write their own. My point is that Asobo is doing synthetic vision something another dev says is not possible with wasm, so unless Asobo is keeping all the cool tools for themselves or the devs are complaining about nothing 

9 minutes ago, devgrp said:

I'm sure it will be available in the sdk

They are using native code signed and distributed by Microsoft so it can run on XBOX and XBOX PC.

WASM is so 3rd party developers can make addons that will run on XBOX and XBOX PC without getting the code signed by Microsoft - hence no file or system access.

Edited April 7, 20206 yr by mSparks