FS25 unitsPerPixel bug report submitted

[Snake Man]

I have just submitted bug report about unitsPerPixel being broken in Farming Simulator 25 (FS25) using Giants Software Feedback Tracker website.

This bug has been extensively discussed in Dev Diary Large Terrain Studies Farming Simulator 25 and Terrain Editing daily updates while waiting for Giants Editor v10 release.

Its now done, not that I have high hopes of it getting fixed but at least I did my part, you cannot complain and whine about state of Giants Engine v10 unless you at least submitted bug report of everything you see broken in there. If YOU have not submitted unitsPerPixel being broken or any of the other issues you're experiencing with FS25, register account now and get it done.

It might feel silly to submit bug reports to giants feedback tracker, especially as giants do now show any bug reports publicly, makes no sense to me, everybody in the community has to report the same bugs over and over again, guess giants can judge the "popularity" of a bug/issue by seeing how many times its been reported, but overall its a mess as people report the same bug with different terminology descriptions etc, I feel bad for the feedback tracker admin guy/team who has to wade through what I can only assume thousands if not TENS OF THOUSANDS of bug reports.

Anyways, if you haven't reported bugs, do it today, don't wait. Its the only way there is even a chance of fixing FS25.

[ARG_Afb]

glad that you submitted the UPP error snake, hope giants fixes it!

[Snake Man]

Moments ago received email notification:

The following issue has been RESOLVED.

To recap: unitsPerPixel feature was broken in FS25 giants engine v10 up to today's version (I assume they didn't release patch today heh). Now according to that feedback tracker bug report reply, its been resolved. I'm very interested to see next game and giants editor update if it shows up there and if its actually fixed in terrains.

Of course I'm happy if this has been fixed, but I have been so burnt to a black rock by giants with their FS25 release that I highly doubt my opinions are changed just by fixing unitsPerPixel feature, there is still the remaining issue that even 8.1km terrains are unusable. But anyways, I don't want to even think about that FS25 trash right now, just wanted to keep you guys updated that there has been progress at least on this bug report.

[Snake Man]

Just read the FS25 v1.6 update changelog, no mentioning of unitsPerPixel fix. Perhaps they left it out just from the changelog, or perhaps changelog is correct and that fix didn't make it into this update.

Not that it matters much, it doesn't really fix anything for terrain developers, sure you could make more little girlie men terrains now but who the hell would want to do dumb stuff like that.

[jdunn1019]

So i have seen MAP With UNITSPERPIXEL AT 1... at 4km MAP.. but my map is at 2 unitsperpixel should i change it to 1 and fix evertything or should i leave everything to 2 unitperpixel?

HELP!

[Snake Man]

Heightmap pixel resolution 4096 and unitsPerPixel 1 is more heavier for the CPU/GPU (not sure which, mostly GPU I think) than heightmap pixel resolution 2048 and unitsPerPixel 2.

Poorer performance and better details or better performance and poorer details. The age old question.

I'm personally editing a game instead of a slide slow generator, so I always go for the game-play and performance first, details come always the second. I much rather play rock solid 60FPS overall nice lower detail mod than some highly detailed with barely 24FPS stuttering performance mod.

[jdunn1019]

If i add unit per pixel "1" its make everything smaller and all my roads and building and everything off the map ? idk what to do? idk if its playable with unit per pixel at 2