Forum Replies Created

Viewing 8 posts - 46 through 53 (of 53 total)
  • bauerbrown
    Keymaster
    Member since: December 29, 2022

    Jeez, I need a patreon, LOL.

  • bauerbrown
    Keymaster
    Member since: December 29, 2022

    I’d say there is a very good chance that’s exactly what is happening. You can create 8 bit PNGs yourself if you want, but it will not create them automatically for you. You can copy them from the base game, but they will be a fixed size .grle and will need to be converted to a PNG. You will probably also need to copy fieldGround.xml from base game. All of these steps are only usually required with maps bigger than 2km, but I suspect something is off with your map.

  • bauerbrown
    Keymaster
    Member since: December 29, 2022

    The Elmcreek files are specific to the Elmcreek map. Something got missed or overlooked during creation this time around. Read the other post where I mention “fieldground.xml” – start there.

  • bauerbrown
    Keymaster
    Member since: December 29, 2022

    Now we’re back to infoLayer resolution, LOL! The PDA relies on it, and so does the visible plow state. Have a look in your map.xml and find the file path for “fieldground.xml” – verify where it’s pointing to (probably $data). There are several png listed in that file that I think are causing your issue. Track them down (they can be found in the base game if they are not in your data folder) and host them locally. Change all the file paths to point toward your local copy. Check the resolution on them and try adjusting them one step up. ie. 2048 -> 4096.

  • bauerbrown
    Keymaster
    Member since: December 29, 2022

    Weird, so now I’m thinking the issue is with the field itself. If I ever have an issue with one particular field, one thing I try is to erase the field, and by that I mean erase it from fieldDimensions infoLayer or delete the “blue squares.” Then I re-create the fields with that one missing, save the map, and then draw the field back in and repeat the process of re-creating the fields and saving. This is not a guarantee, but I have had some success with this method in the past.

    The only other thing that comes to mind is that perhaps there is something wrong the density map “fruits” itself.

  • bauerbrown
    Keymaster
    Member since: December 29, 2022

    I’ve never personally done it if there is. I want to say that it can’t be done but I don’t want to give you a definitive answer until I check it out. I vaguely remember seeing something about stone size, but I can’t recall what that was about. It really seems to me that it is a bigger issue because ALL fields should have stones. The same with your other issue, the lime thing …. these are all common symptoms of a bigger issue like resolution or such. Resolution issues present themselves in such a way that things will work in some fields, but not others, because the associated infoLayer or density map is not the correct size and does not correctly align or overlap your fields.

    If I had to go out on a limb and take a guess, I would say that these are likely not your only two issues. At some point or another you may have issues with rolling, spraying, or stubble levels.

    Did you build this map from scratch, and by that I mean the blank you started with, or did you download a blank from the internet?

  • bauerbrown
    Keymaster
    Member since: December 29, 2022

    This is just off the top of my head and not tested in any way, but my first thought would be that the resolution is off on the plowLevel.grle. Lime level is ok, but not the plow. Does this happen on all fields, or just this one? Actually, I should have asked … is this 2km or bigger?

  • bauerbrown
    Keymaster
    Member since: December 29, 2022

    Is this a map you created, or RMR? I ask because I’m working on an identical issue with RMR – I think it is resolution related, but I’m not certain of that.

Viewing 8 posts - 46 through 53 (of 53 total)