Why do certain Assets not render/disappear at close angles?

Willkommen in der Transport Fever Community

Wir begrüßen euch in der Fan-Community zu den Spielen Transport Fever und Train Fever, den Wirtschaftssimulatoren von Urban Games. Die Community steht euch kostenlos zur Verfügung damit ihr euch über das Spiel austauschen und informieren könnt. Wir pflegen hier einen freundlichen und sachlichen Umgang untereinander und unser Team steht euch in allen Fragen gerne beiseite.

 

Die Registrierung und Nutzung ist selbstverständlich kostenlos.

 

Wir wünschen euch viel Spaß und hoffen auf rege Beteiligung.

Das Team der Transport-Fever Community


    There are a few Mods where if you are angled close to them in a forward or backward motion they disappear from view prematurely. Why does this happen and how can this be resolved?


    It is very difficult to attach a .gif so I have to just attach two pictures.


    Here



    Gone  ||




    Imagine yourself moving toward the house structure and it just disappears on you. If you back away, it is rendered again. I'm sure the original Modder will have to adjust something, but I would like to know what is happening here for my own knowledge and so that I may assist them with troubleshooting this issue as it is an annoying occurrence.


    Any help would be appreciated!


    Thank You

    This may be an issue with LoD distances. In general, a model consists of multiple submodels of decreasing detail level that are shown depending on distance from the camera.


    The most detailed model is shown from distance 0 to x, a slightly thinned out from x to y, an even more thinned from y to z, and from z to a final distance, it will be a mere box. Obviously, there should be no gap between those LoDs, but if these are badly defined, it may happen that within a small range of camera distances, there is no model at all defined and it will consequently disappear. If so, it will be shown from some distance, then disappear when approaching it and pop back up when approaching even further.


    If this fits Your problem, look at the .mdls. They contain a heap of parts, each LoD has two lines at its very end. The figures in them will differ between individual models, but the general idea is the same:


    Code
                visibleFrom = 0,
            visibleTo = 50,

    This is a low (highly detailed) LoD that is shown from 0m to 50m.


    The next higher (so slightly less detailed) LoD will then show something like:

    Code
                visibleFrom = 50,
            visibleTo = 150,

    ...so there will be no gap between the two LoDs.


    If instead, it reads in the second LoD

    Code
                visibleFrom = 80,
            visibleTo = 150,

    the model would be undefined between 50 and 80m and consequently gone from sight.


    To adjust this, check those entries in the .mdl and arrange them so they come in an uninterrupted sequence.

    Thanks for your input DH-106; when I return home I shall test this in notepad++ to see if there is a visibility gap in the LODs.


    I also spoke with User Adie Gibbs elsewhere and they suggested that it may be incorrect Bounding Box Code! In either case both are easy fixes for me to make on my end, however it would be best if the original Modder could update this for everyone's experience.


    I'll be sure to inform them once it's determined which one is the culprit when I test later. I'll also return here so that the solution is immortalized on the forums :) .

    -----

    Edit: Alright I double checked this stuff. The LoD visibility ranges were set correctly without any gaps fortunately. The culprit was indeed the collider Box information.


    The Solution 8o

    • Open your .mdl files in Model Editor while simultaneously opening them in notepad++.
    • Delete the Collider Box code in notepad++ and save the file. Model Editor will now generate a new Collider box for you that matches your Bounding Box.
    • Save the .mdl in Model Editor. When you return to NotePad++ you will be prompted to reload and will now see the Collider Box Code is magically fixed.
    • Do this for all of your asset .mdl files and you are good to go!