[edit] Apologies in advance if it sounds like I'm ranting...I just had a crappy day and typing stuff with my knuckles makes me feel better.
-How in the world is it possible to turn a Distance() function into a twisted mess of broken dreams and urine? I'm still not sure, but at least now I know that human ape-like creatues can do it given about 5000 years or so of practice...
I don't know how it could achieve a result that is dramatically different. The present distance function accepts irrational values when it tries to do Sqrt(). It was not meant to be included in this release anyway, as all of the revised std.h stuff is still on the table for discussion, not for inclusion.
-The debug console can drop your FPS by consuming so many cycles doing io. Also the allegro4.4 is slightly slower than the allegro4.2 library (probably due to bugfixes), but it shouldn't make that much of a difference.
Aye. The process of writing to disc is slow as hell, for some reason. I don't think that using an SSD makes any difference either, but I believe that if it was display/terminal-only, it would be faster. Allegro writing to disc is dreadful.
A 60fps difference doesn't tell me anything. I do not know the total numbers, to comprehend what percentage of a drop this is for him. If his normal frames are 700 and he is seeing 640, that is a 9% drop. If his total frames are 3000, and he is losing 60, then it is a 0.5% drop. I need relative values to understand why this is a problem. For all I know, it is a Windows 8/10 thing and is related to his allegro settings, as I believe he had the same issue with 2.50.3RC1, and the main difference there was in the basic allegro configuration for ZELDA-DX.
-@Avataro: Can you compare a non-scripted quest in this to the same quest in 2.50.whatever and see if the FPS are still way off?
-And the same thing again with a scripted quest? I'll look into it. (I have a hunch)
Care to relay this one?
-I still have no idea how this naming convention works. Is 2.53 before or after 2.54?
Before. In theory, 2.53 in August/September, as the last in the line of versions that are 2.50 compatible--meaning that 2.53 quests still run in 2.50. 2.54 to follow in Dec/Jan, pulling only stable features that are in master and that will not change. Mostly some ZScript stuff, such as itemdata, DrawBitmapEx, and similar stuff that we know that we will retain.
That one will produce quests that only run in 2.54 and later, and this should be the trend thereafter. Stop letting everyone run hackish quests that play in older/ancient player versions that we need to support indefinitely.
Releases with only critical bugfixes would be another matter, but if the bugfix introduces a change that could affect how quests run in old players, it may as well be a new version to prevent massive issues with backported quests. COMBOSM should be a lesson here.
I've started using 2.60 for the present 'master'. The changes are so radical at this point, that it is bearing far less of a resemblance to 2.50.x than to a wholly new animal. The changes are so damned drastic, that I expect it to takes months of testing to fully resolve it into a Gamma, and I see us taking months just to finish implementation. DD is rewriting all of the classes and structs, and probably Link too; plus the revised script system, the nearly entirely rewritten parser, and all of my changes. It's going to be a bunch of hell.
You listed the fixes and all but I kinda want to know what new features can we expect in this build as opposed to what features already exist in 2.50.2
This is not a 'new feature' release. 2.53.0 exists to stabilise 2.50.2 and 2.50.3 into one unified body, as a final stable 2.50.x version. it is the end of the 2.50 era, and I intentionally left out all of the new ZScript stuff, engine changes, parser changes, and such, that were not bugfixes.
A final, stable 2.50.x base is mandated, before adding new stuff into the mix.
I can probably put the new favourite commands in there, as those do not affect compatibility.
New features will probably first appear around the new year.
Edited by ZoriaRPG, 12 July 2017 - 06:29 AM.