Invisible Interior Faulty in TRS2019

Steamlocomotiveworks had a lot of steam-locomotives from Germany and Poland.
Many of them are useing an invisible interior, <kuid:484026:16797507>. This is only a config.txt file.

In T:ANE the file is faultless.

Imported in TRS2019 build 97271 the file is faulty (in bold):

; <kuid:484026:16797507> Validating <kuid:484026:16797507>
! <kuid:484026:16797507> VE48: This asset uses an obsolete trainz-build number. Trainz-build numbers below 3.5 are no longer supported.
! <kuid:484026:16797507> VE61: Required tag 'interior-controls-type' was missing and has been set to default.
; <NULL> Performing asset precache
; <kuid:484026:16797507> Loading asset <kuid:484026:16797507>
- <kuid:484026:16797507> MeshTableSpecMixin:rivateOpenResources> empty mesh name at index 0 of asset <kuid:484026:16797507> "invisible interior"
; <kuid:484026:16797507> PrecacheManager:recacheNow> <kuid:484026:16797507>
; <NULL> PrecacheManager:recacheNow> <kuid:484026:16797507>
; <NULL> MeshObject::LockMeshes> <kuid:484026:16797507> "invisible interior"
! <kuid:484026:16797507> MeshTableSpecMixin::CreateMeshParticle> Unable to create mesh index 0 for asset <kuid:484026:16797507> "invisible interior"
! <kuid:484026:16797507> VE200: Unable to load mesh default for <kuid:484026:16797507> "invisible interior"
! <kuid:484026:16797507> TrainzMeshCollisionData::GetRawData> No PhysX actor.
; <kuid:484026:16797507> MeshObjectSpec:recache> Failed to get collision data for invisible interior - <kuid:484026:16797507>

What can I do?

Thank you very much in advance for your help

Regards
Swordfish

I've sent your info to the team to review, but the likely answer is "create a version that has a mesh" or "remove the parts that refer to a non-existent mesh".

I had the same in TANE, I just removed the invisible interior from the config and have not encountered any problems.

I can't get my head around the concept of an invisible interior though, who's going to see it? LOL!.
I am sure there is a techy reason

euromodeller said:

I had the same in TANE, I just removed the invisible interior from the config and have not encountered any problems.

I can't get my head around the concept of an invisible interior though, who's going to see it? LOL!.
I am sure there is a techy reason

Click to expand...

From memory there are one or two 'drivable signal boxes' with invisible interiors on the Download Station - they are designed as vantage points from memory.

Shane

Thanks shane, come to think of it, I have one of those signal boxes, was a bit of fun driving it

euromodeller said:

I had the same in TANE, I just removed the invisible interior from the config and have not encountered any problems.

I can't get my head around the concept of an invisible interior though, who's going to see it? LOL!.
I am sure there is a techy reason

Click to expand...

It enables those creators who can't make working interiors, I can't yet, to have working controls in real mode using the on screen hud and use the non functioning interior of the main mesh and have cab view, which works with invisible cabs. It's not actually invisible, just a small mesh hidden away to enable the cab view to work.

Interiors with only viewpoints (no mesh faces) did work up to TS2009 at least - I accidentally created one, and only discovered the problem when users converted the asset to T:ANE.

All this is very interesting

The SLW invisible interiors that were faulty for me were actually in the tenders of the locos, the locos are perfect!
They were fine in TANE SP2 but broke in SP3.

A few days ago, edh6's WHR Castell Caernarfon suddenly went faulty for me in TANE SP3. The actual culprit was the cab (<kuid:404575:100090>) by author cj187. The reported errors there also refer to 'empty mesh name at index....' so it looks like something, somewhere might have had a far reaching effect throughout TANE and TRS2019.