DrprofLuigi

> The second picture in the chat says that no trailers were found, which shouldn't appear when disconnecting a trailer. That is some fanciness with the pallet, ignore that second...

It's something that could be approximated (take a look at the UNU Solenodon), however more accurate animation would necessitate trig function suffixes for more variables. Though, perhaps something with VMs...

Are you using that variable on a vehicle, or a part? Just like every other variable listed on the wiki, you'll need to suffix the part number if you are...

> That's the weird thing though, before this change it worked just fine! I didn't need no suffixes _and_ it could end with a number were it on an engine...

This may be related to trailer panel buttons not working consistently, as _that_ only a problem when there are multiple connection points possible. For example, my HUD trailer button does...

This may actually be due to VMs not working on trailers period. I have two gauges on my tank trailers. One simply references a part variable, and the other does...

This is solved by swapping the VM order: ``` { "variable": "p_brake", "animations": [ { "animationType": "translation", "variable": "!connection_1_1_connected", "axis": [0, 0, 1] }, { "animationType": "translation", "variable": "t_brake", "axis":...

It looks like the main issue of VMs not accepting `hookupVariables` seems to be holding true. The trailer has the following VMÖ ``` { "variable": "p_brake", "animations": [ { "animationType":...