I have included a full set of resources to re-produce this issue here: https://we.tl/t-HlJbF46XIy
Drop each resource in your resources folder, start in this order → test_objects
, test_dui
, test_usage
test_dui
and test_usage
should be started after connecting since it triggers on resource start.
Alternative / simpler download: GitHub - mikeemoo/fivem-texture-bug
Coords for test location: x=“269.76640000” y="-320.84060000" z=“46.33287000”
–
To put the issue simply, when you want to create multiple DUI objects with multiple texture replaces and multiple texture dictionaries / names, you get a weird bug where some of them don’t render. Its inconsistent behavior is very consistent in that some may show, and some may not.
Here are some example screenshots of what happens when you run the above resources:
Blank canvas: https://i.imgur.com/tg3FNVZ.jpg
First run: https://i.imgur.com/GtX89mO.jpeg
Second run: https://i.imgur.com/8IhDHJh.png
As you can see above, what is supposed to happen is each texture is replaced with its corresponding number in order. So each individual square would have 1
through 8
on it. What actually happens is some do not render whatsoever. On occasion, you can get lucky, and they will all render. Other times, none of them will render.
–
Additionally, unrelated, there seems to be a hard limit on DUI objects of 128. If you exceed this, your game will freeze up (not crash, freeze, and have to be stopped via task manager.)