NO-Error on cultivations on all scenery addon's after Nov 20th update

  • I have AFS2 running in steam sofar without any issues. By starting up this night(Nov 20th) a got a small update(If update is available it installs it automaticaly).

    When starting up the sim and choosing a random location, I was unhappely surprised by spikes on every autogen(cultivation) made on the additional sceneries,

    hereby screenshots of 3 random choosen locations, also screenshot of my system as info:

  • wow ...looks like you`re now on another planet ... Pandorra ?

    Its not a bug...its a feature :) new DLC `;) Freeware ?

  • Forget the beta!.

    Cheers, Ed

    Windows 10 Home x64 | i7-8086K | MoBo ASUS Maximus XI Hero Z390 | 32GB RAM | 2xSSD Crucial 1TB + 1xSSD Samsung 1TB + 1xSSD Crucial 2TB | MSI GTX 1080Ti Gaming X 11GB | LG 29UC97C UW Curved | Oculus Rift VR | TM FCS HOTAS // Gaming Laptop ASUS ROG Strix Scar II GL704GW | Windows 10 Home | i7-8750H | 32GB RAM | 2TB SSD + 2TB HDD | Nvidia RTX 2070 | TM FCS HOTAS // P3Dv4.5hf2 + AFS2

  • ikbenik

    Changed the title of the thread from “Error on cultivations on all scenery addon's after Nov 20th update” to “NO-Error on cultivations on all scenery addon's after Nov 20th update”.
  • FAKE NEWS !!!


    The error I had has nothing to do with updates and now for shure not after latest update of Nov 20th.


    I punished my brain and especially my short-time memory !!! The errors are caused by installing Taburet's Italy-19m Mesh yesterday before doing a restart of the sim later on and by coincidence choosed 3 locations in and around Italy and saw these spikes tinking it was this last updated that could

    have been the reason...Wrong, it's the 19m Mesh that covers not only Italy itself but also a large part of the surroundings, like Corsica, Sardegna and Croatia. So sorry for the caused misunderstanding and maybe hereby the hint: the 19m Mesh from Taburet(3GB) isn't compatible with autogen-adds.

  • @TomSimMuc: We added a new feature for cultivation buildings to use the z value of the position as an optional height offset. Unfortunately all z values in some add-on sceneries have this set to the absolute height even though auto_height true is used. We fixed this in the latest beta to only use the z value if an optional bool value in the tsc file is set to true:


    Code
    <[bool][use_height_offset][true]>


    In the tmsimulator_scenery_cultivation block of a tsc file.

  • Fortunately it was Free!:D

    Cheers,

    Pascal


    Intel I7-4930MX - 3,90 GHz - 32 Go - GTX 880M - 8 Go - Samsung SSD M.2 250 Go + Samsung SSD M.2 750 Go - Win10 Pro

  • We fixed this in the latest beta to only use the z value if an optional bool value in the tsc file is set to true:

    This is a good idea and solved the Lukla problems since 2.04.07.55 (20191121).

    Thank you for the fast resolution.


    Can you please update the Wiki, so that all elevation related commands are contained?