2 hours ago, hanhamreds said:

What I’m most disappointed with 2024 is the fact we appear to have gone back several steps - to the early stages of 2020,

It's almost like they forked an early branch of 2020 to use as a base for 2024 but never fixed some of the bugs that subsequently got fixed over the past couple years in 2020.  The sepia mask is a perfect example.  The improved it quite a bit in 2020 by pushing the radius out much further but now we are back to the sepia mask being all around you.  I also think the 28/10 runways lights at KATL are back to not working (I need to double check but swear they were out when I landed there recently).  I submitted a bug for that in 2020 alpha testing and it took 3 years to fix.  I also noticed snow on the roads where there was very little if any snow on the grass beside them.  Another silly big that was fixed in 2020 and appears to be back in 2024...

14 hours ago, Bobsk8 said:

I spoke about this to a programmer last week, and he said two words " Bad programming". 

and "a programmer" knows this without ever having seen a single line of the source code?

bugs can exist undetected even in the most complex, most thoroughly tested software.

I (with limited software developer experience) have the highest respect for the MS/Asobo programming team and praise them for developing the most complex "game" I know.

Bugs? Yes. Bad programming? No.

two words: hybris & arrogance, or Dunning–Kruger effect

....................................................

Two words: bad programming: 🤪

On 4 June 1996, the maiden flight of the Ariane 5 launcher rocket ended in a failure. Only about 40 seconds after initiation of the flight sequence, at an altitude of about 3700 m, the launcher veered off its flight path, broke up and exploded.

.....Just 37 seconds after launch, the rocket had to be blown up. The much greater lateral accelerations (vs. former Ariane 4) proved to be its undoing. The acceleration measurement was passed on as a (signed) 16-bit integer. When it exceeded the magic value of 32768 and became -32767, an error message was triggered, which in ADA caused the control program to be aborted by default. The control nozzles then remained stuck in their position and the rocket rotated perpendicular to the direction of flight.

The variable was removed from the range-exceeding check for performance reasons. The part of the program in which all this happened was actually no longer needed in the Ariane 5. It was only adopted to minimize the differences in the software versions of the rockets.

..................................................................................................

The internal SRI (Inertial Reference System) software exception was caused during execution of a data conversion from 64-bit floating point to 16-bit signed integer value. The floating point number which was converted had a value greater than what could be represented by a 16-bit signed integer. This resulted in an Operand Error. The data conversion instructions (in Ada code) were not protected from causing an Operand Error, although other conversions of comparable variables in the same place in the code were protected.

......

The reason for the three remaining variables, including the one denoting horizontal bias, being unprotected was that further reasoning indicated that they were either physically limited or that there was a large margin of safety, a reasoning which in the case of the variable BH (Horizontal Bias) turned out to be faulty. It is important to note that the decision to protect certain variables but not others was taken jointly by project partners at several contractual levels.

http://sunnyday.mit.edu/accidents/Ariane5accidentreport.html

Edited January 7, 20251 yr by turbomax

I want to like it, but I’m still having enough issues that although I check in with 2024 once or twice a week, I’m sticking with 2020 for now until 2024 gets where I want it to be. On a related note, “I’m never going back” really doesn’t add anything to these threads. Just my two cents. 
 

Cheers, Pete

Regarding 'next update'...: I see movement in the steam db in the last minutes: https://steamdb.info/app/2537590/history/

5 minutes ago, MaGer1965 said:

Regarding 'next update'...: I see movement in the steam db in the last minutes: https://steamdb.info/app/2537590/history/

Doesn't mean much there was updates to that last week and right up to Xmas.

OK 🙁

Updates that aren't beta tested, LOL. seen this before. 

Latest update

https://forums.flightsimulator.com/t/2025-01-07-career-mode-server-side-update/695558

I've gotten much better results with 2024 by tempering my expectations, turning my settings down and giving the sim room to breathe - much like I do with X-Plane.

As much as I'd love to have all the bells and whistles, I'm happy with 30+ fps solid, and reasonable texturing which still looks good .. for me it's more about the flight anyway, I'm not interested in leaves on the ground on a hill 500m away - and if I were, I'd be in a smaller plane and might just turn the settings up a bit. With something like the Fenix though, the computer needs some help if I want the best it can give me.

The main problem I do have is sometimes the arrival airport textures are not loading in - Asobo need to fix that (maybe precaching the arrival airport - although they'd need some way of knowing what it is) because there's not really anything I can do about that aside from perhaps loading into the destination airport first, caching it, then hoping the cache works when I arrive during a flight. It would be nice to not have to worry about silly things like that though.

 

Edited January 7, 20251 yr by FPVSteve