known Grass is clipping through the airframe bottom in both cockpits

rogorogo · January 16, 2022

When landed on a random terrain surface or a terrain pad area, grass will clip through the airframe in both cockpits (the rear passenger compartemt has no position and only a blurry inner render model, so no assumption can be made for this compartment).

While I do not know if this is intended or not, the grass does react to rotary module in some way (movement, proximity trigger of a "dust blowout"), so this should be paid attention to by collision or other means (down the line, low priority as purely cosmetic).

random example (Caucasus terrain), pilot-cmdr cockpit with cyclic and seat hidden for better visibility of the clip-through:

no trackfile needed, as reproducable with any grass surface and occurrence is permanent, for any systems (unless grass removed via DCS settings)

Boosterdog · January 16, 2022

Grass will clip into the models. Trees To. Drive an F16 slowly into a tree an an airfied and tree will end up in the middle of an undamaged wing as well. Just he way stuff works (if you flew the aircraft into the tree at speed the effect would be what you'd expect).

The grass in DCS is simply just too tall all round but its a greater problem in the Caucauses map. Its been reported as a bug but is apparently low priority. Its height could possibly be a result of a trade in performance as shorter grass may need to be denser but noone from ED has come forward and said that to my knowledge.

AeriaGloria · January 16, 2022

Yeah happens in Mi-8 also. Not a Mi-24P specific problwmc

i defiantly think the grass is so tall all around to make up for performance. I wish our clutter options were larger, both farther clutter generation and complete ground clutter removal

rogorogo · January 17, 2022

This a bug report for a specific module as noted with this module.
In the absence of a standard bug reporting tool most products in this industry and this segment of the industry and even 3rd party providers within this very franchise with the most meager of resources mangage to offer this bug report was placed in the correct place as defined by the module provider in question.

If there were similar issues with other modules of the same or different asset-categorization the corresponding reports could be cross-referenced in front-office or merged in backoffice.
The same goes if there were fundamental or foundation level bugs for the underlying suite.

Unfortunately this is not the case - to the contrary the product provider has even actively dismissed more systemic reports up to re-enacting events normally found in an Ian M. Banks novel and quite aggressively decreed beyond any ambiguity to only report strictly within the scope of a module and limited to whatever is on-the-nose.

How... confusing. Or maybe quod erat demonstrandum in expectuu sine qua non est casu exemplii pars pro toto.

Edited January 17, 2022 by rogorogo