The "optimisation" fix.. was that just for one issue?

56 minutes ago, OHN767 said:

Well there you go, the mother of all patches. someone is probabably developing a weather program that works and some live traffic that works, it wil only cost us another 100$ or so.

If only— Asobo has locked down the weather engine and no 3rd party can even touch it. 

6 minutes ago, sd_flyer said:

This actually true. Looking for a problem could take days, weeks and fix can be only few lines of code.

The first part in the andhog post is true, the second is not. The patch does not contain source code so the relation of the patch size to actual code size is almost 0. If that was source code, it would be a treasure trove for 3rd parties. 🙂 

1 minute ago, Matthias1231 said:

The first part in the andhog post is true, the second is not. The patch does not contain source code so the relation of the patch size to actual code size is almost 0. If that was source code, it would be a treasure trove for 3rd parties. 🙂 

How do you know that patch doesn't apply a source code? What do you think they patch a wrapper?

47 minutes ago, sd_flyer said:

It seems more microstutters here and there than before (subjectively) 

the patch may need a patch

15 minutes ago, FAZZ3 said:

A bit of perspective for you whiners.

While this statement is true in general (the file size of software is no method to "measure" the amount of work required), the last paragraph is... just complete non-sense, to be polite.. apologies..

Must be a new thing that you can just take the 333MB and calculate how many characters fit in text file of the given size.. But Asobo delivers a patch containing compiled binaries and most likely assets (like 3D Models for example), so how on earth is somebody able to imply how many lines of code were actually written? Phew..

I don't get why people need to sound like they have knowledge when they actually don't have any, like the second paragraph clearly shows. Just /facepalm - and 80 characters per line? Uhm, punchcards are rarely used nowadays, this was a thing some decades ago.. Yes, COBOL still exists and uses this limit, but really?

Edited September 2, 20205 yr by roesti

5 minutes ago, sd_flyer said:

How do you know that patch doesn't apply a source code? What do you think they patch a wrapper?

In terms of code, the patch will only apply compiled binaries. No company in its right mind would send their source code to a client machine and turn it into a binary locally.

General performance dropped down about 10-15 fps with the new patch 😞

Just did a 1-hour flight everything was stable and smooth, including the frames. 50+fps on a mix of High-End/Ultra@ 5K and no stutters when using SPAD.Next and FSEconomy. Great times!

Edited September 2, 20205 yr by GCBraun

20 minutes ago, FAZZ3 said:

A bit of perspective for you whiners.

I once had the misfortune of spending over a month fixing a bug in a game that I was working on, all the time being pushed for release. Turned out to be a simple array out of bounds error, but wow did it take some finding. It didnt manifest until there was exactly x amount of objects on screen. Just needed an update to one line of code and hey presto a game breaking bug was fixed.

4 minutes ago, Matthias1231 said:

In terms of code, the patch will only apply compiled binaries. No company in its right mind would send their source code to a client machine and turn it into a binary locally.

I'm aware of that! But how do you know what is being patched?

What are you saying?  It's time for me to buy this sim now??

I am a sure that I have gained 10fps on a 4 core processor.

Despite the complaints, I'm pleased with the patch. They did exactly as they said they would.

Obviously live weather needs to be fixed, and ideally they'd give SDK access to edit default airports, but I just got to experience my first MSFS flight on VATSIM and it was so awesome. I had been waiting a long time to do one because I wanted to experience this sim. 

Took out the TBM-930 from PHOG to PHJR, which was a ton of fun. Had TWR and APP online at PHOG. Flew IFR, and swapped between the GPS and using VORs for ease. Flew in a VOR-DME approach. 

The coolest part was after, I saw a SWA jet in the distance landing in Honolulu, so I grabbed the drone and sped over to watch the landing. Was very smooth, and the refresh rate was surprisingly good for VATSIM!

Edited September 2, 20205 yr by FlyingInACessna

6 minutes ago, sd_flyer said:

I'm aware of that! But how do you know what is being patched?

The discussion was about the person on the official forums who said how many charcaters of text fit in a file of 333MB size. But these patches are not text files, they're compiled source code (binaries) and assets (3D Models or textures). It is just not possible to "calculate" how many lines of code were written if you just take the file size of a patch. There is no direct relation. You can write thousands of lines of code and compile it into a file only a few kilobytes big, for example. The compiler translates the written and readable text humans create into machine code. At the same time, the compiler is able using optimization techniques and recognizes inefficient code and simplifies it. I won't go into detail here, but I hope you understand that his implication (file size = number of characters written) is just false.

Edited September 2, 20205 yr by roesti