[3.1408] Crop Water bug

[Jalzm]

I've recently encountered a bug that never happened to me before. When selecting Crop Water small squares are taken out of the water chunks. This happens on both Blizzard and custom maps. Custom mpq's don't seem to be the cause (I've tried removing them from the data folder, doesn't solve the problem)

[Amaroth]

Was that ADT edited before by Noggit, or is this the first touch you have given it in Noggit? I suppose the former, still, just asking.

[Jalzm]

Was that ADT edited before by Noggit, or is this the first touch you have given it in Noggit? I suppose the former, still, just asking.

First touch. The ADT in the screenshot is Westfall, specifically. I've never edited it before.
This bug occurs in any ADT or map regardless of whether it's been edited before or not.

[Adspartan]

I tried with both version 3.1222 and the current build but and I couldn't reproduce this so idk what's the cause.
Try to use the 3.1222

[Jalzm]

I've done some testing and found that Noggit 3.1408 has stopped cropping water. The tiny chunks of missing water in Noggit's client don't carry over to the game.
I've tried a fresh install of 3.1408 and it still happens. It doesn't happen with previous versions of Noggit.
Here's a zip of my Noggit folder if no one else (devs) can reproduce it.

[Gratural [Харгард]]

This bug its a one reason (after giantic stupid dildo-cursor circle) why i gone from 3.1408 to using both older and newest Noggit version.
Just dont touch water in 3.1408 - use any another version of Noggit for water editing.

Place another version exe file (like 3.1222) into your noggit directory for water cropping.

[schlumpf]

This bug its a one reason (after giantic stupid dildo-cursor circle) why i gone from 3.1408 to using both older and newest Noggit version.
Just dont touch water in 3.1408 - use any another version of Noggit for water editing.

Place another version exe file (like 3.1222) into your noggit directory for water cropping.

Why don't you only use the latest version for everything?!

[Amaroth]

I have explained this to many people many times schlumpf.
A) Its not easily accessble nor publicly released, which makes it hard to find, or even sometimes get working.
B) I was actually asked by Adspartan to NOT share the newest versions, to prevent people from having incomplete untested development versions short time before actual public release is made, which could result in people not moving to the newest version.
C) Many people in general do not want to use software which is not publicly released, as they fear that its unsafe or unstable (and are perfectly right to assume so).

So here's why. Apart from point B its something I'm saying over and over again. And before you ask why don't we just compile it on our own, here's D:
D) Its not that easy or doable for everyone - compiling Noggit. I have attempted to compile Noggit on my own multiple times and always failed due to all kinds of issues (even Steff wasn't able to help me with one of them). I've got so sick of that, that I just gave up in trying. And while not being C++ programmer or real programmer in general, I know a thing or two about .NET and VS, and am definitely not a complete noob, so I'm kind of person who probably should be able to get this working. Guess what, I was not.

[Steff]

I just had a chat with adspartan today. He works towards a release version and we will test it in a closed team if he is ready. If this tests went all good it will get a qt release version. After this we will try to release new versions with new features more often.

[Amaroth]

E) You guys are actually the ones who have multiple times told users to not use unreleased versions of Noggit for any serious work, as work can be lost. I don't just repeat point C, I want to highlight the fact that you actually are even reminding us of content of C. Its weird to wonder why are users not using versions of Noggit you have actually told them to not use in the past, at least not for anything other than testing.

I know Steff, but you were not the one who was asking . I just get feeling that schlumpf isn't asking similiar kind of question for the first time and wanted to answer it, thats all.

[Adspartan]

E) You guys are actually the ones who have multiple times told users to not use unreleased versions of Noggit for any serious work, as work can be lost. I don't just repeat point C, I want to highlight the fact that you actually are even reminding us of content of C. Its weird to wonder why are users not using versions of Noggit you have actually told them to not use in the past, at least not for anything other than testing.

I know Steff, but you were not the one who was asking . I just get feeling that schlumpf isn't asking similiar kind of question for the first time and wanted to answer it, thats all.

I think schlumpf was just asking why gratural was using a newer AND and older version and not just a the newer version he has :x

[Gratural [Харгард]]

E) You guys are actually the ones who have multiple times told users to not use unreleased versions of Noggit for any serious work, as work can be lost. I don't just repeat point C, I want to highlight the fact that you actually are even reminding us of content of C. Its weird to wonder why are users not using versions of Noggit you have actually told them to not use in the past, at least not for anything other than testing.

I know Steff, but you were not the one who was asking . I just get feeling that schlumpf isn't asking similiar kind of question for the first time and wanted to answer it, thats all.

I think schlumpf was just asking why gratural was using a newer AND and older version and not just a the newer version he has :x

Its simple. as Amaroth says, QT Noggit sources cant be build by medium map developer. He works unstable and unpredictable. And  also,
F) QT Noggit builds has are veeeery increased hardware requirements))

[schlumpf]

I think schlumpf was just asking why gratural was using a newer AND and older version and not just a the newer version he has :x

EDIT: I was made aware that both versions are SDL versions. While "latest should be better and if not, please bug report" still stands, disregard everything I said, because I don't care a bit about SDL versions.

---------

Exactly this. As far as I remember, 3.1222 and 3.1408 are both Qt versions. If there is an issue that prevents you from always using 3.1408, please report that issue to the bug tracker to make us aware, instead of weirdly switching versions based on what feature you need. Doing that is absurd.


A) I am aware, there is no release for good reason, e.g. F).

B) Yes, and I'm also against the Nightly builds some people have suggested doing. It will fuck shit up, and that's not helping anyone.

C) And that's good, see A) and B).

D) While it is obviously not intended that users compile their own versions, you should report issues you have with compiling to the bug tracker. I surely don't expect every user to compile it theirselves.

E) See A, B and C. Yes, it is pre-release and it should be treated as such, and serious users should not use it.

F) Adspartan is working on performance optimisations currently.


And again, I was at no point asking for you to compile your own version, but was asking why you prefer to use _two different pre-release versions while there is no bug in the bug tracker about either of them_. It _should_ work better with the latest one, whatever that is, be it the actual current repository latest, or the latest pre release version you got from god knows where. If there is _any_ reason to _not_ use the latest and _only_ the latest version, that's a bug and _should_ be reported.

[Amaroth]

A) I am aware, there is no release for good reason, e.g. F).

B) Yes, and I'm also against the Nightly builds some people have suggested doing. It will fuck shit up, and that's not helping anyone.

C) And that's good, see A) and B).

D) While it is obviously not intended that users compile their own versions, you should report issues you have with compiling to the bug tracker. I surely don't expect every user to compile it theirselves.

E) See A, B and C. Yes, it is pre-release and it should be treated as such, and serious users should not use it.

F) Adspartan is working on performance optimisations currently.

I am aware of all of these, and agree with them, don't worry.

[Steff]

3.1222 is SDL a version and I think the other also.
I know no one till now using the qt version productive.