GIANTS Software - Forum

This is the proper bug report of viewtopic.php?f=936&t=119225
We are aware that this bug came with the 1.51 update and is accepted in the German forum but as nobody from Giants commented in the English forum I wanted to open this proper bug report thread so that hopefully we can be able to see the progress in English.

- PC/Mac/PS4/XB1: PS4
- Vehicle/Tool/Model/Object: Any cultivator, any fertilizer
- Issue: If you have fertilized the field befor cultivating you can't fertilize again after cultivating.
- Single- or Multiplayer: Single
- Steps to reproduce: Fertilize --> Cultivate --> Fertilize
- Does it happen on a standard map without mods yes/no: Yes / Came with update 1.51

Why would something this simple not be caught? This is a base process of the game.

Testing is quite a difficult job to do.
It is way too easy to miss things.
Especially if they are this usual and routine.

Something I have remembered recently.
My last game save on the golden days of farming was on october 30th. 2 days before the release of 1.51 on november 2nd. In that last game I cultivated oil seed radish into the ground. Something I had already done a lot times in the who dat who der ranch. After cultivating I sow the field with a fertilizing seeder and it just didn't work although it had always worked in the wdwdr map. It seemed extremely weird but I thought i had done something wrong. Now it seems this bug dates 2 days earlier than the release of 1.51
How is that as a coincidence?

Showdizzle wrote:Why would something this simple not be caught? This is a base process of the game.

Totally agree with you. This is basic testing very easy to be caught. It's caught regress testing, meaning you test not only the new features, but also all the old ones to make sure they work.

I see now it this bug is labeled "known issue" does that mean giants recognize the issue and are working on it, or is this just the way it will be from now on.

They recognize the issue as a bug and it is know on their fixing list.
"When" is another question though.

BrettDavid wrote:I see now it this bug is labeled "known issue" does that mean giants recognize the issue and are working on it, or is this just the way it will be from now on.

Good observation. What exactly does "known issue" mean to Giants and more importantly what should it mean to the customer? Perhaps therein lies the root of the problem. Communication.

Many on this forum will quickly point to the fact that Giants is a small company. With a very loyal fan base which is a great strength for this company. The one thing it lacks is great communication.

Lisertan relegates communication to "mods currently in testing." Which should be labeled "what is not coming to console." During update 1.4 and 1.5 an honest, straightforward communication effort with the community would bolster what is already a strong relationship. The company which is not making strides in innovation and lacks in quality assurance surely would at a minimum want to help customers understand.

You have PC users rolling back the update, numerous threads concerning bugs, etc.


edit by guil. Leave out the insults please.

BrettDavid wrote:I see now it this bug is labeled "known issue" does that mean giants recognize the issue and are working on it, or is this just the way it will be from now on.

It`s confirmed from Pfreek in the german forum

viewtopic.php?f=934&t=119143#p933566

Showdizzle wrote:
Good observation. What exactly does "known issue" mean to Giants and more importantly what should it mean to the customer? Perhaps therein lies the root of the problem. Communication.

Many on this forum will quickly point to the fact that Giants is a small company. With a very loyal fan base which is a great strength for this company. The one thing it lacks is great communication.

Lisertan relegates communication to "mods currently in testing." Which should be labeled "what is not coming to console." During update 1.4 and 1.5 an honest, straightforward communication effort with the community would bolster what is already a strong relationship. The company which is not making strides in innovation and lacks in quality assurance surely would at a minimum want to help customers understand.

You have PC users rolling back the update, numerous threads concerning bugs, etc.

I'm afraid I have to agree with you. "Giants is a small company" is an excuse for everything, apparently including releasing a patch with a bug so serious, that there are players like me, who are unable to play the game at all.

Showdizzle wrote: Good observation. What exactly does "known issue" mean to Giants and more importantly what should it mean to the customer? Perhaps therein lies the root of the problem. Communication.

The meaning of "known issue" and other states is described in the following post: viewtopic.php?f=936&t=110383

Thank you for posting that link. That clears up a lot of questions. Is there a time line on when this bug will be fixed? I won't go as far as to say it makes the game unplayable now (which it clearly doesnt) but it does make the game less enjoyable for me, personally.

I think its related to this:

Also when using 3 stage fertilizing. Spreading slurry with zunidisc to ploughed field doesn't work.

To reproduce:
-Harvest grain.
-Spread fertilizer
-Plough
-Try to spread 2nd fertilizer stage with slurry using Zunidisc (and obv. cultivating at the same time), DOESN'T WORK.

However spreading fertilizer or slurry without Zunidisc works at this point. But this is already known I guess. The problem is in cultivator somehow aplying the "dark" fertilized layer?

Showdizzle wrote: Lisertan relegates communication to "mods currently in testing." Which should be labeled "what is not coming to console."

There's a "PC" section and a "PS4/XBOX" category, so no, it shouldn't be called "what's by coming to consoles" they do it so that players know what mods they MIGHT get soon

Edit don_apple: fixed quoting