Результатов найдено: 397
37
Загрузка...
Загрузка...
18.09.2021 в RIP Unleashed Rages
That's really dumb. It was the funniest atWar video I'd ever seen.

Do you still have a copy of it? Would love to see it on some non-YT platform where we could still share it in forums. (Or I could even just upload a copy to the AW site directly...)
Загрузка...
Загрузка...
17.09.2021 в What the hell
Написано Kaska, 17.09.2021 at 15:35

Seriously, in a single game i had like 7 bugs

https://prnt.sc/1slqvt4

https://prnt.sc/1slppj7

https://prnt.sc/1slnppv

https://prnt.sc/1slt6g5

https://prnt.sc/1sloqy8

I had some other bugs that i didn't even ss.


Thanks man for following the proper bug report format

It probably has to do with the shit way atWar saves games. The code that saves/restores the game's state whenever you refresh the page is not reliable, which ties in to what WD said. I've been working on replacing this with a new saving system, but it's a big project, will take a while.

As for right now I'm sorry there's nothing I can do.... I think it would be impossible for me to reproduce the exact bug from the screenshots.
Загрузка...
Загрузка...
17.09.2021 в Best food?
Написано f boomers bye, 17.09.2021 at 15:51

your a god damn discrage


Nice spelling
Загрузка...
Загрузка...
29
Загрузка...
Загрузка...
17.09.2021 в Game host!
Yes I'm sure a few people will abuse it that way. I think it's worth the risk though, so that people who spend time waiting for a game to fill can be sure to start even if the host disconnects... it's a better user experience for everyone else.
Загрузка...
Загрузка...
19
Загрузка...
Загрузка...
Написано brianwl, 14.09.2021 at 10:08

Sure, Potato and Waffel gave their dissenting opinions a lot, and both were eventually hammered by the big man himself. But they deserve respect for their contributions, and for challenging authority when most of us would have backed down. Please excuse me while I get back to watching porn my real job.


I've always liked Waffel... I don't understand why he quit. I never ban hammered him if that's what you mean. I teased him about his Dutch-iness, but that's just to be expected. (The Dutch are weird after all, it's an objective fact.)

It's true Laochra and I got off to a bad start, but we made our peace about it. I imagine he's still not a fan of me, but I harbor no ill feelings against him. I haven't interacted with him in a very long time. I assume he just got bored of AW and moved on.
Загрузка...
Загрузка...
12
Загрузка...
Загрузка...
Написано GI-Jew, 09.05.2019 at 09:44



This should be fixed now. I've released a patch to prevent this particular JS error from happening.

I tested starting a game in the British Isles map, and it worked correctly for me now, although I did not play a full game on it. There could certainly be other/different errors out there we haven't found yet, so if you run into any more problems with it just let me know.
Загрузка...
Загрузка...
Загрузка...
Загрузка...
Написано Monte, 22.08.2021 at 05:09



This is *probably* fixed. Since you couldn't tell me exactly which map the error occurred on, I couldn't test to confirm if this applies to you or not. However, I've released a patch to prevent some similar JS errors (i.e. the red text errors), according to the following bug reports:
https://atwar-game.com/forum/topic.php?topic_id=47074
https://atwar-game.com/forum/topic.php?topic_id=44331
https://atwar-game.com/forum/topic.php?topic_id=41897
https://atwar-game.com/forum/topic.php?topic_id=44989

The root cause of the error is actually due to glitched borders on the map. These would still need to be fixed by the map maker, for whichever particular map it is. Even though I've fixed these red text errors in general, as long as those glitched borders remain it's possible to encounter other problems. If that happens, take a look at this bug report, which explains that open borders (i.e. gaps in the borders) are one cause of it, and how to fix it (specifically, see the reply from Mesopotamia).

Hope that helps!
Загрузка...
Загрузка...
Написано Zephyrusu, 30.05.2020 at 11:56



This should be fixed now. I've released a patch to prevent this particular JS error (i.e. the red text errors) from happening.

However, the root cause of the error is glitched borders on the map, so its still possible you might run into other problems because of that. If so, take a look at this similar bug report, which explains that open borders (i.e. gaps in the borders) are one cause of it, and how to fix it.

Beyond that, if you run into any more errors with it, just let me know.
Загрузка...
Загрузка...
Написано ZEDO, 07.08.2019 at 03:38



This should be fixed now. I've released a patch to prevent this particular JS error from happening.

However, the root cause of the error is glitched borders on the map, so its still possible you might run into other problems because of that. If so, take a look at this similar bug report, which explains that open borders (i.e. gaps in the borders) are one cause of it. @Mesopotamia explains how to fix it on that bug report.

Beyond that, if you run into any more errors with it, just let me know

Написано Sascha, 10.08.2019 at 06:52



Thanks Sascha for providing the detailed info, that was what I needed to solve this
Загрузка...
Загрузка...
Написано SoggyHerman, 06.04.2020 at 15:26

This error shows up when i start the game
Error: Uncaught InvalidStateError: Failed to execute 'drawImage' on 'CanvasRenderingContext2D': The image argument is a canvas element with a width or height of 0., Script: https://atwar-game.com/java/atwar.core.min.201908040611.js, Line: 1, Column: 86558, StackTrace: InvalidStateError: Failed to execute 'drawImage' on 'CanvasRenderingContext2D': The image argument is a canvas element with a width or height of 0.


This should be fixed now. I've released a patch to prevent this particular error from happening.

As @Estus pointed out, it is related to glitched borders, so its still possible you might run into other problems because of that. If so, take a look at this similar bug report, which explains that open borders (i.e. gaps in the borders) are one cause of it. @Mesopotamia explains how to fix it on that bug report.

Beyond that, if you run into any more errors with it, just let me know
Загрузка...
Загрузка...
Написано Noir Brillant, 28.03.2021 at 18:56



This should be fixed now. I've released a patch which should prevent this particular error from happening. I tested started a game with your map and it was okay, but I didn't actually play beyond that, so if you run into any more errors with it, let me know please
Загрузка...
Загрузка...
Probably there is some bug with the translation system.... I have not looked into that area of the code before. I'll check it out.
Загрузка...
Загрузка...
03.09.2021 в Longest winstreak ?
Написано Sphinx, 02.09.2021 at 03:15

4. I think Dave's cool and respect his political opinions, need more people like him out there, it's a breath of fresh air and I wish nothing but success for him.


Upvoted for this part, thanks for the kind words. As for the rest I'm staying out of it...
Загрузка...
Загрузка...
Написано Mobster, 18.08.2021 at 00:53



Thanks man for upvoting my reply, but you didn't answer me which map it is

If you tell me I can probably fix it....
Загрузка...
Загрузка...
Написано Mobster, 30.08.2021 at 19:46

This coming from a guest account... Who is this, the CIA after the statistics?


Hmm, poster's IP address traces back to Langley, Virigina.... that's not sus at all
Загрузка...
Загрузка...
Написано BrnoLeopard, 30.08.2021 at 22:22

Https://ibb.co/XjPmJk5
https://ibb.co/b1mHqKF

Any idea what I should do with this?


There's nothing to do there. The first screenshot is just showing that Zip.js is loaded, which is expected. The 2nd screenshot shows its failing, as I described to you. The problem is somewhere else.
Загрузка...
Загрузка...
Написано BrnoLeopard, 30.08.2021 at 19:17

I thought I had seen something to do with JSZip on my side... I'll see if I can do something with it.


Oops I misspoke slightly.... we use Zip.js, not JSZip. (Both are JavaScript libraries that do the same thing.... I got them backwards when I wrote this.... not that it changes anything)
Загрузка...
Загрузка...
Написано Monte, 22.08.2021 at 05:09

Bug Report


Expected behavior
I have a mistake in the map and can´t join.

Actual behavior:
i delete the cache in firefox -> dont work.
i try it with mircosoft Edge Browser -> the same bug.
i try it with old Internet Explorer -> the same problem.

Steps to reproduce the behavior:
not known

Information:
Browser: Mozilla Firefox
Browser version: Firefox 91.0.1
OS: Windows 10 Pro / Build 18363.1556

Any other relevant information:
i work to 95 % with firefox
I had this problem often with a few cards I played

Attachments:
https://ibb.co/ZNh9qq7

Does anyone have an idea how to solve this mistake and I can join the map?


The "steps to reproduce the behavior" is the most important part of the bug report, I really do need this information. It's very simple -- what do I have to do to see the error for myself? For example, lets start with the map -- which map is this, exactly? You might say something like this (for example):

Steps to reproduce the behavior:
1. Go to map "XYZ map" (whatever the name of the map is)
2. Start a game with these settings (whatever game settings you chose)
3. Click "start game"
4. Error message appears while game is loading.
Загрузка...
Загрузка...
Написано Mobster, 18.08.2021 at 00:53

Bug Report
Expected behavior
When I save the current world map(Idk if it's the only one) with a different background and leave the editor, I should be able to edit it again

Actual behavior
When I join back to the editor with that map I saved, it gives Error: Loading Paths.

Steps to reproduce the behavior
1. Clone the world map
2. Upload a different background
3. Save it, return to maps lobby
4. Return to editing it, you'll get the error (flat.zip 404)

Information:
Browser: Firefox

Browser version: Latest

OS: Windows 10

Any other relevant information:
Roma Invicta explained that he started getting this error in this topic: https://atwar-game.com/forum/topic.php?topic_id=47855
So I looked into it for a while, then I realized I'm getting the same bug too!

This didn't use to happen until the last month(I had a problem about it in the past but I found a way around lately, and that doesn't work now too). So Dave, sadly, I'm believing this fix might have caused it:
https://atwar-game.com/forum/topic.php?topic_id=47720

Attachments:
https://cdn.discordapp.com/attachments/812877919981535247/877429814758371368/Screenshot_24.jpg


This is probably another of what I call the "DB/Filesystem version mismatch" error. Basically there is a versioning system that was put in by the atWar original developers. It consists of a version number stored in the database, which is supposed to match with the map files on disk. The problem comes when you save the map -- lets say something goes wrong and the saving process fails -- the DB version gets updated anyway, even though the matching files don't exist. Now the map is broken.

Probably we need to make sure the DB version does not update unless the save was successful (I think Clovis may have already worked on this possibility a long time ago, I'll check)... that would prevent the map from becoming broken. However there would still be the issue of why you were unable to save, and we would have to deal with that later.

The good news though is that if you tell me exactly which map it is, I can *most likely* fix it. If I can fix it, the map will go back to however it was before the last time you tried to save it.
Загрузка...
Загрузка...
Написано BrnoLeopard, 16.08.2021 at 19:47

Not to be mean, but do you know when the fix will be done?


I really have no idea. It could be weeks, months, or years. It's a complex problem (I'll explain why in a minute), and of course the time I can dedicate to atWar is somewhat limited.

Написано geyeluvu, 18.08.2021 at 11:59

Maybe we're the only players with difficulty accessing maps.


You're the only 2 who have reported this specific issue to me. In programming there's a rule of thumb -- for every 1 user who reports a bug, there are probably 10 others who say nothing about it. So certainly there could be others effected by this issue, but in any case, with approx. 7K active users at the moment, it must be a pretty tiny percentage. I still consider it to be important, but its not super-urgent either, since the vast majority of people are not effected.

(Yes, there are tons of other bugs out there that lead to "error loading paths", but they are caused by unrelated problems, so not relevant to this discussion.)




Okay, so why is this a complex issue?

The problem you are experiencing is that, for you, Zip.js is failing. Zip.js is a JavaScript library for compressing/decompressing .zip files. AtWar uses this because the borders (or "paths") of any given map are stored somewhere on the server as a .zip file. When you load a map, a bunch of stuff is loaded by your browser, including the .zip files containing the paths, which are then decompressed by Zip.js.

Why is Zip.js failing for you, but not for everyone else? That's the mystery. For me, Zip.js always works... I've tried multiple devices, multiple locations, and multiple browsers (Chrome, Firefox, and Edge). I've never gotten it to fail on my side. The fact that it doesn't work for you means that something *must* be interfering on your side, but I don't know what it is.

If I were to guess, I'd say most likely you have some browser extension that is blocking or causing a conflict with Zip.js. If you use an incognito tab (Chrome) or private tab (Firefox), that would bypass all your browser extensions and probably be able to load atWar like normal. However if that doesn't work, then it must be something even more unusual. Maybe you have a firewall that blocks certain scripts, and for some reason is blocking Zip.js. Or maybe your internet service provider is interfering in some way. I know some ISPs will do funny things to compress data and therefore reduce bandwidth usage... perhaps they are compressing our (already compressed) .zip files in a way that makes them unreadable by Zip.js. (That's just a wild guess on my part, but it would be interesting if you could try loading atWar from a different location, maybe a coffee shop or something, and see if it makes any difference... just for sake of solving the mystery of why this is happening...)

Anyway, regardless of what's causing Zip.js to fail for you, I've already been thinking for a long time about getting rid of Zip.js. I assume the original developers of atWar used it to save space on the server. However the drawback is that it makes games take longer to load, and uses more CPU resources on the client side (i.e. on your side). It's one more thing that contributes to atWar feeling slow or clunky, especially if you happen to have a computer that's maybe a little older. In my opinion, it should be removed.

What needs to be done to completely remove Zip.js from atWar?

The first problem is that all maps' borders are currently saved as zip files on the server. If we get rid of Zip.js, then the borders need to be saved in a format your browser can understand without having to unzip them. Basically, we need to unzip the borders of every map on the server and use the original uncompressed files instead. Unfortunately, there are currently over 17K maps (17,759 as of right now) on atWar -- far too many to go through manually. So my first task would be to write a script that can automatically go through them all and unzip the stuff. But actually that leads to another problem -- unzipping all those files would exceed the amount of storage space we have available.

We're very tight on available space as it is -- in fact, I'm continually having to move stuff off to other servers to make room. The maps however would be difficult to move because pretty much all of the atWar code expects them to be right there on the main server, where they are now. So that leads me to another task that would need to be done first -- we need to free up some space.

I think a big percentage of our 17K maps can be considered "junk" -- either broken maps, or maps that people cloned and then never did anything with. I know a lot of people have asked for the ability to delete broken maps. So maybe the first thing I'll need to do is add a "delete map" feature. Of course I'll have to do this very carefully to prevent abuse, because there are plenty of people out there who would love to maliciously delete popular maps if they could. I've been thinking about this for a long time -- probably I'll build in a requirement that the map can only be deleted if it has less than 10 plays (or something like that), so the more popular maps can't just disappear overnight.

After that, I could even do a big "purge" of junk maps. Maybe I could write a script to delete all maps where there are less than 10 plays AND the mapmaker who owns it has been inactive for, say, 2 years. That would free up a lot of space! Then we could go back and unzip the maps that remain, and we'd probably have enough space to do it.

A little side note: the "temporary fix" I did for the World Map was to first unzip the World Map's borders on the server, and then I added some code that basically says "if Zip.js failed for any reason, grab the uncompressed borders instead". That was enough to make things work again for you guys... but to do this for other maps, I would have to manually go and unzip each specific map that you wanted to play, one at a time. As you could imagine, that would end up being a lot of manual work, which I'd rather not have to do. I'd rather wait until I can automate it, and do them all at once.

Anyway... back to what I was saying. Lets say we've purged a bunch of maps, we've made space, and we've unzipped all the remaining maps' borders... now we're finally ready to remove Zip.js. This involves a couple of things. First, we need to remove it from the Map Editor -- Zip.js is used to create the .zip files that get uploaded to the server in the first place. We need to make sure that when you save a map in the editor, it saves the borders in their uncompressed format instead. This shouldn't be too difficult, but dealing with the Map Editor code is always a bit of a nightmare so I have to allow more time than I would otherwise expect. After that, we can (finally) remove Zip.js from the game. And then we can finally say, "problem solved".

So to summarize, I guess the biggest problem at the moment is storage space and the fact that we have 17K maps to process. The first thing I'll do is add the "delete maps" feature so we can start making space, so keep your eyes open for that. When you see an announcement about a new "delete map" button, you'll know I'm making some progress on this issue as well.
Загрузка...
Загрузка...
Присоединяйтесь к нам на

Передай слово