• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

B-25J INBOUND

The one that crashed in Stockton used to fly over my house a few times a year, then it got sold. Ran out of fuel.
It is being restored to flying condition.N7946C-1831737143.jpg
B-25-Old-Glory-2799331691.jpg



 
Last edited:
Ugh, I can't believe they ran out of gas in a plane that important. Glad nobody died for the error and the plane is in a restorable condition, at least.

I really miss the fly days they used to have at KPAE before the airport commission, Covid, Alaska Airlines, and Paul Allen's mortality ruined everything.

1763579560699.png

1763579615017.png

1763579641840.png

1763579679519.png
 
We can't promise but very much hope it will be before Christmas. Currently we have a "stopgap" sound pack authored by Echo19 but the plan is to do a full recording session of the real thing early in the new year when a suitable aircraft becomes available. That would then be released in an upgrade when completed.
 
We can't promise but very much hope it will be before Christmas. Currently we have a "stopgap" sound pack authored by Echo19 but the plan is to do a full recording session of the real thing early in the new year when a suitable aircraft becomes available. That would then be released in an upgrade when completed.
Appreciate you all at AH, thanks for the reply, Bazzar
 
Ugh, I can't believe they ran out of gas in a plane that important.

Unfortunately, it happens more often than you would think, the list goes on and on. Just read the NTSB website, monthly accidents, and you will be surprised.
 
We can't promise but very much hope it will be before Christmas. Currently we have a "stopgap" sound pack authored by Echo19 but the plan is to do a full recording session of the real thing early in the new year when a suitable aircraft becomes available. That would then be released in an upgrade when completed.
Thanks for posting info on the update here. I must admit this looks pretty awesome from the screenshots so far. However I’d like to ask if there is a plan for a 2024 version at some point? I totally respect AH have their reasons to stick with 2020 aircraft; but personally I’ve decided to only purchase native 2024 aircraft moving forwards, which puts the B25, Lancaster and upcoming Mosquito off limits for me. All of those would be slam dunk purchases otherwise!

I’m not looking for a free 2020 to 2024 upgrade since I think that’s not sustainable for devs due to the work involved - I’m talking about separate 2024 products; can we expect them eventually?
 
We need to see more comprehensive and compelling figures on 2024 useage. Currently most and as we move forward with more compatibility resolves, of our products work well in 2024. Our research is showing that careers and squashy tyres are not strong enough reasons to make dedicated add-ons for 2024. The specifications to make models 2024 native represent a LOT of work. For example the need by the sim to stream content requires models to be modularised to make them easier to download. On a product like Lancaster this requires a complete rebuild of the models. At the end of it all, the resulting product is not backwards compatible so it will not work in 2020.

This means that unless we make two of everything we develop we run the risk of losing what 2020 market we have built.

Currently we prefer to make for 2020 and spend smaller amounts of time ensuring that they will run well in 2024. With XBox and now PlayStation entering the mix the workload could increase even more we just don't know yet.

Lancaster's performance in 2020 Marketplace exceeded all our expectations by a significant margin. We see no reason to rock that boat right now. Once 2024 is stable and error free and we can see significant numbers "crossing the floor" we will most certainly commence building for it. But with our limited resources, building the same subject for two simulators is just not economic sense.
 
We need to see more comprehensive and compelling figures on 2024 useage. Currently most and as we move forward with more compatibility resolves, of our products work well in 2024. Our research is showing that careers and squashy tyres are not strong enough reasons to make dedicated add-ons for 2024. The specifications to make models 2024 native represent a LOT of work. For example the need by the sim to stream content requires models to be modularised to make them easier to download. On a product like Lancaster this requires a complete rebuild of the models. At the end of it all, the resulting product is not backwards compatible so it will not work in 2020.

This means that unless we make two of everything we develop we run the risk of losing what 2020 market we have built.

Currently we prefer to make for 2020 and spend smaller amounts of time ensuring that they will run well in 2024. With XBox and now PlayStation entering the mix the workload could increase even more we just don't know yet.

Lancaster's performance in 2020 Marketplace exceeded all our expectations by a significant margin. We see no reason to rock that boat right now. Once 2024 is stable and error free and we can see significant numbers "crossing the floor" we will most certainly commence building for it. But with our limited resources, building the same subject for two simulators is just not economic sense.
Completely fair enough, and I’ve seen the effort involved in fighting the LOD system on modular 2024 aircraft, it looks like it can be a big drain on a dev team's resources getting that right. But I’m glad to read that there is an intent to move to 2024 at some point. I’m hoping SU4 might be the tipping point for many users, but let’s wait and see.
 
As a warbird nut, I can say that I am glad you do. I haven't crossed the floor yet (although I tried) and am not planning to in the near future, but if you guys start developing exclusively for 2024, I just might. Glad I don't have to though...
 
Development time issues caused by the two versions of MSFS also affect freeware production.

As far as I’m concerned, I am carefully watching the progress of the latest SU on FS24 but the potential number of people who are still on FS20 is very important.

On the other hand, Asobo/Microsoft have broken (why? ...) in FS24 the function that allowed in the DEV Mod to recharge an aircraft after making a simple modification to the configuration files. The solution they proposed is to go through a recompilation of the Projects files ...
Besides since SU16, this function also seems to have been slightly modified in FS20, it seems logical because there must be a lot of common code between the two simulators.

To conclude, I hope that the release of SU4 will greatly improve things and will undoubtedly allow me to switch my development to FS24.
 
I'm not gonna tell any (commercial) developer how to run their business. That's their prerogative. But we've seen with every new iteration of FS that it takes a while for the audience to shift to the newer sim. Heck, there are some people who are still on FS9. It is also true that the launch of MSFS2024 was a mess. However, the sim is at least for the kind of flying I do stable and has been for a long time. And I hear pretty good thing about SU4. In hindsight, MSFS2024 would have benefitted from one more year in development before release. This would probably have expedited the acceptance of and shift to the new sim. For devs, this may of course be a different proposition. I will say this however: Microsoft will not change their approach (streaming the sim). Not with the potential extra market of X-box and Playstation-users. So IMHO any commercial developer who is unwilling to learn the new tricks of the trade will eventually be left in the dust commercially. Now I don't know how long AH intends to keep developing for FS and maybe (most likely) they don't care one iota about my views on the matter, but I'll stand by my statement. Having said that, I do wish them and any dev (whether commercial or freeware) all the best. Thank you all for enriching our hobby.
 
Last edited:
I'm not gonna tell any (commercial) developer how to run their business. That's their prerogative. But we've seen with every new iteration of FS that it takes a while for the audience to shift to the newer sim. Heck, there are some people who are still on FS9. It is also true that the launch of MSFS2024 was a mess. However, the sim is at least for the kind of flying I do stable and has been for a long time. And I hear pretty good thing about SU4. In hindsight, MSFS2024 would have benefitted from one more year in development before release. This would probably have expedited the acceptance of and shift to the new sim. For devs, this may of course be a different proposition. I will say this however: Microsoft will not change their approach (streaming the sim). Not with the potential extra market of X-box and Playstation-users. So IMHO any commercial developer who is unwilling to learn the new tricks of the trade will eventually be left in the dust commercially. Now I don't know how long AH intends to keep developing for FS and maybe (most likely) they don't care one iota about my views on the matter, but I'll stand by my statement. Having said that, I do wish them and any dev (whether commercial or freeware) all the best. Thank you all for enriching our hobby.
I only switched to 2020 from P3d Version 3 a year ago. Keep releasing 2020 stuff!
 

Unfortunately, it happens more often than you would think, the list goes on and on. Just read the NTSB website, monthly accidents, and you will be surprised.
Yeah, but on a 26 mile flight you don't even need to retract the gear. Heck - you should be asking for landing clearance before you even take off!
 
We need to see more comprehensive and compelling figures on 2024 useage. Currently most and as we move forward with more compatibility resolves, of our products work well in 2024. Our research is showing that careers and squashy tyres are not strong enough reasons to make dedicated add-ons for 2024. The specifications to make models 2024 native represent a LOT of work. For example the need by the sim to stream content requires models to be modularised to make them easier to download. On a product like Lancaster this requires a complete rebuild of the models. At the end of it all, the resulting product is not backwards compatible so it will not work in 2020.

This means that unless we make two of everything we develop we run the risk of losing what 2020 market we have built.

Currently we prefer to make for 2020 and spend smaller amounts of time ensuring that they will run well in 2024. With XBox and now PlayStation entering the mix the workload could increase even more we just don't know yet.

Lancaster's performance in 2020 Marketplace exceeded all our expectations by a significant margin. We see no reason to rock that boat right now. Once 2024 is stable and error free and we can see significant numbers "crossing the floor" we will most certainly commence building for it. But with our limited resources, building the same subject for two simulators is just not economic sense.
Right now I'm of the opinion that MS2024 was not a net success, being beset by the plan to stream content to thin client users in real time. A plan that curtailed if not derailed every other advantage it may have derived from improved programming.
I plan to stay with MS2020 until either the next MS flight sim is created or support for MS2020 is dropped (if MS decides to 'push' us across the floor to 2024) If the latter occurs it will be time (for me anyway) to leave MS flight sims for a different developer..
I'm really pleased to hear that AH has the stance it has WRT development for either MS sim. All of the salient points made by Bazzar seem to reflect what I had surmised, though I really wish 2024 could have been all we hoped it would be. Probably in another 5 years there will be
the necessary improvements to production PC and console hardware and AI assisted programming that would make the streaming model work easily - such changes will likely lead to better ATC, weather, and terrain rendering than we have ever seen - the familiar challenges flight sim is still plagued with today. Let's hope so
 
We need to see more comprehensive and compelling figures on 2024 useage. Currently most and as we move forward with more compatibility resolves, of our products work well in 2024. Our research is showing that careers and squashy tyres are not strong enough reasons to make dedicated add-ons for 2024. The specifications to make models 2024 native represent a LOT of work. For example the need by the sim to stream content requires models to be modularised to make them easier to download. On a product like Lancaster this requires a complete rebuild of the models. At the end of it all, the resulting product is not backwards compatible so it will not work in 2020.

This means that unless we make two of everything we develop we run the risk of losing what 2020 market we have built.

Currently we prefer to make for 2020 and spend smaller amounts of time ensuring that they will run well in 2024. With XBox and now PlayStation entering the mix the workload could increase even more we just don't know yet.

Lancaster's performance in 2020 Marketplace exceeded all our expectations by a significant margin. We see no reason to rock that boat right now. Once 2024 is stable and error free and we can see significant numbers "crossing the floor" we will most certainly commence building for it. But with our limited resources, building the same subject for two simulators is just not economic sense.
I totally agree with the result of your marketing research. I can't stand the UI for FS2024 so much I can't even get past starting it up and getting into a flight, and therefore still use 2020. And I also agree that the benefits of being native 2024 are far outweighed by the negatives for developers. The 2020 market is still too big to ignore, especially given the fact that it's possible to get 2020 aircraft to run reliably in 2024 with very few negatives. Having to create two completely different models for the two sims just isn't worth it at this time.

If career mode ever becomes stable and expanded so that it's easier to use whatever plane you want for a career, and they develop tools for allowing vendors to develop new detailed career paths, I could see that becoming a tipping point. But, until then, I don't see don't see the benefit of developing for native 2024 assuming 2020 planes are well developed and work well in both sims.
 
Back
Top