Blizzard please share source code of old Warcraft III version
)))
I remember people mentioning in this thread that using GamecacheSync natives causes a desync. I have tested this, and have come to the following conclusions:
> Whether a desync occurs seems to depend on how many Sync calls are made in a single frame.
> The "cutoff point" seems to be 345 Sync calls per frame. 344 or less are perfectly safe. 345 or more lead to desyncs in 100% of the times.
> It must be noted that this did not cause desyncs in the past, as I have a save/load system that heavily relies on these calls, and it has been tested on prior patches with no such issues.
Could this be a regression caused by the new desync detection system? It'd be great if Blizzard looked into this, as it severely limits save/load capabilities. We have no other options other than to use these natives. @Kam
Dont you have a phone? Take your time in any of those grind games while bugs are being fixed, not a big deal!Wait. 1.30.3, no bug fixes AT ALL.
What the heck?
I just created an account to ask about this. I experience crashes with a map I am editing on this new patch. It never happened on earlier patches. The map has only GUI triggers with the exception of custom code to avoid leaking triggers. The map desyncs after 00:00 seconds. I tried to have no triggers fire in the first 2 seconds but it still does not matter. I only have triggers run on map initialisation to set up forces and variables. What do you suggest I do? Thanks for reading this.I remember people mentioning in this thread that using GamecacheSync natives causes a desync. I have tested this, and have come to the following conclusions:
> Whether a desync occurs seems to depend on how many Sync calls are made in a single frame.
> The "cutoff point" seems to be 345 Sync calls per frame. 344 or less are perfectly safe. 345 or more lead to desyncs in 100% of the times.
> It must be noted that this did not cause desyncs in the past, as I have a save/load system that heavily relies on these calls, and it has been tested on prior patches with no such issues.
Could this be a regression caused by the new desync detection system? It'd be great if Blizzard looked into this, as it severely limits save/load capabilities. We have no other options other than to use these natives. @Kam
I just created an account to ask about this. I experience crashes with a map I am editing on this new patch. It never happened on earlier patches. The map has only GUI triggers with the exception of custom code to avoid leaking triggers. The map desyncs after 00:00 seconds. I tried to have no triggers fire in the first 2 seconds but it still does not matter. I only have triggers run on map initialisation to set up forces and variables. What do you suggest I do? Thanks for reading this.
And sound bugs are re-introduced! 1.30.3 is actually 1.30.1Wait. 1.30.3, no bug fixes AT ALL.
What the heck?
I have found that you must run nearly everything outside of map loading or it will desync 100% of the time.I just created an account to ask about this. I experience crashes with a map I am editing on this new patch. It never happened on earlier patches. The map has only GUI triggers with the exception of custom code to avoid leaking triggers. The map desyncs after 00:00 seconds. I tried to have no triggers fire in the first 2 seconds but it still does not matter. I only have triggers run on map initialisation to set up forces and variables. What do you suggest I do? Thanks for reading this.
This isn't the place for this, go ask for help on the forums.Where are the maps located in the new CASC Archives? They don't have the same file structure as the old mpq's, so theres no "Maps" folder anywhere that I can see.
Edit: Found Em. They're not in the war3.mpq folder where everything else is, they are in the xxxx-war3local.mpq files. (xxxx is your local region, e.g., enus, kokr, etc.)
Edit 2: Now I can't open the World Editor. Did I kill it?
??? Do you have 2 abilities with the same order ID on the same unit and wonder why it doesn't work well? FYI casting an ability actually based on the order, not ability, therefore EACH ability with the same order will be fired. Thats intentional and must-preserve state of the game as is. The only thing which has to be done about it is to allow add our custom order IDs. The behavior should stay this way.I also reported at the same time in September that with two abilities based on channel with the same orderid, a trigger with the condition 'Ability being Cast = Ability 1' also fires for Ability 2.
Again, this has not been fixed.
but you have both abils on the same unit, right? Was casted or being casted, irrelevant, we're speaking of 2 simultaneous actions, and that's normal. You should really check out older patchs.. if there are ways to downgrade tho.I don't mean casting the ability, I mean doing a check to see what ability was cast. Say you have two abilities, Ability 1 and Ability 2. They are both based on Channel and have the same orderid. If you two triggers, one with a condition that checks if the ability cast was ability 1 and one that checkes if the ability cast was ability 2, it will run the first trigger for both abilities and the second trigger for neither.
If I'm not mistaken, LAN should still be available (I'm not using it as it now requires some useless 3rd party trashware), they're just going to abandon it.So, now we must go to Battle Net even being adjacent to each other? Oh...
It's already created. Program is called CASC viewer.The question is, if Blizzard killed the mpq and changed it to .001, would something be created to open the files and a model editor that accepts this type of file?.
Oh and in the Spanish version, not only does the shaman speak in English, in the last mission of the humans at the beginning they speak in English, Furion speaks in English, and others that I do not know, but he does have those errors.
Also in the German version, furion & Shaman use many english lines since V1.30 (Casc Migration).Oh and in the Spanish version, not only does the shaman speak in English, in the last mission of the humans at the beginning they speak in English, Furion speaks in English, and others that I do not know, but he does have those errors.
It's already created. Program is called CASC viewer.
Loooooooooooooooooooooll! For real?? howzdispossible?I sought refuge from DCs by replaying the campaign until they fix b.net.
Just saw the patch notes.
— Alchemist now keeps getting nerfed. I did warn, it was a bad idea to buff Acid Bomb. Alchemist deals quite a lot of burst if he pairs it with Chemical Rage. I suppose this was meant to buff it when he pairs it with Healing Spray instead, but I haven't seen anyone using Alchemist as a healer.
— As for Mountain Giants, it seems there's the impression they're too good when massed? There's almost no game where I've been glad to get giants over bears, as they fall easily to heavy melee without dealing any viable damage.
I reinstalled WC3 that day, after which the dialog didn't pop up anymore. But now it did once again, while playing NE RoC final mission (by continuing straight from previous one). It's hard to pin down when this happens thus I can't really give steps to reproduce. I'm on latest patch.I sought refuge from DCs by replaying the campaign until they fix b.net.
Can you install the PTR version of the game?Can you please help me someone? I can not upgrade to new version. I am desperate cause I tried everything. Thanks...