st RMM trees and other items showing textel error

D

dangavel

Well-known member
To be brief, a textel error in many trees ,st rmm, roys trees , SAM broadleaf seasonal, I patched up to 126273 and it fixed the issue, I uploaded the timber ridge route thinking the issue had been solved, now, i open up again and the error is back, and another user who uploaded it has the same issue . Has anyone got the faintest idea what is going on here ? How in merry hell can an issue be fixed by a patch and then revert to excacly the same problem a week or so later ?
 
Hey Dan I know exactly what you are asking here. I wish that they would repair those textel errors due to the fact when I made some animated speedtree Grass it became thirdparty due to those errors. That is why a lot of the weeds & Trees flicker and look electrified.
I wonder where the creator of those st mm trees went to? I tried to edit the config file, and the textures to no avail of fixing them.
The error must be in the .srt file and there is no way to open it for editing.
I guess my question would be what is a texel error and how to patch it?
 
Not everyone is having problems with these trees, none are faulty on my install. Maybe try an extended database rebuild as a starting point. I am using TRS22PE 126273. I would suspect it is something other than the trees causing the problem. Maybe if you could post the error message that would help diagnose the issue.
 
All it is it textel errors , no other issue the issue for me is, why were these an issue before I patched up, then ok after the patch for a while and now , the error message has returned . I haven’t even used 2022 since I uploaded the route , now it’s textel issues again . Complete database extended repair did nothing to fix this for me or Heinrich ....who has the same issue.
 
Dave, I think you mean texel, not textel. Texel means "texture element", which is a fancy way of saying a pixel in a texture map.

It would help the discussion if you could paste the actual text of the error message into your forum post, and the kuid of a tree that has that error. It might give someone a hint of what's going on, maybe even a clue as to how it behaves as it does.
 
Another Homer Simpson moment on my part. I was away from my computer when I did the earlier posts and was going by memory, at my age , a bad decision .
It is indeed TEXEL,not textel . it affects 379 st rmms in total, but not the built in or packaged st rmms
This is the error message , some of the st rmm assets ( such as the berezas , dts ,ivas ,dubs ,some sosnas, NOT ALL OF THEM, kashtans and buks ) show no error faults at all, even though they labelled faulty, altho I suspect its the same issue
; <NULL> : Performing asset precache
; <kuid2:211025:21345:1> : Loading asset <kuid2:211025:21345:1>
; <kuid2:211025:21345:1> : SpecsManager::CreateSpec> <kuid2:211025:21345:1> "st_rmm_sosna100_1058_9m"
; <kuid2:211025:21345:1> : PrecacheManager::precacheNow> <kuid2:211025:21345:1>
; <kuid2:211025:21345:1> : PrecacheManager::precacheNow> <kuid2:211025:21345:1>
! <kuid2:211025:21345:1> : Setting an invalid texel factor
! <kuid2:211025:21345:1> : Setting an invalid texel factor
; <kuid2:211025:21345:1> : PrecacheManager::precacheNow> <kuid2:211025:21345:1>
; <NULL> : PrecacheManager::precacheNow> <kuid2:211025:21345:1>
make of it what you will, but its a thorough pain in the posterior.
 
Interestingly on viewing errors and warnings I get a similar result, however these are only warnings and have no effect on the route on my system.

; <kuid2:211025:21345:1> : Validating <kuid2:211025:21345:1>
! <kuid2:211025:21345:1> : Setting an invalid texel factor
! <kuid2:211025:21345:1> : Setting an invalid texel factor
! <kuid2:211025:21345:1> : Setting an invalid texel factor
! <kuid2:211025:21345:1> : Setting an invalid texel factor
; <NULL> : Performing asset precache
; <kuid2:211025:21345:1> : PrecacheManager::PrecacheNow> <kuid2:211025:21345:1>
; <NULL> : PrecacheManager::PrecacheNow> <kuid2:211025:21345:1>
! <kuid2:211025:21345:1> : Setting an invalid texel factor
! <kuid2:211025:21345:1> : Setting an invalid texel factor
! <kuid2:211025:21345:1> : Setting an invalid texel factor
! <kuid2:211025:21345:1> : Setting an invalid texel factor

I'm at a loss as to why it is showing as an error on your system and only a warning on mine.
cheers
Graeme
 
likewise over 60 people have downloaded the route and only one person so far ( and myself ) have had this issue. or they may well have had it and not informed me..... one thing, I do have the 2022 trainz install on a separate ssd. I changed it over from a smaller indstall in c drive as i did nto have sufficient drive space but i am sure it weas before i did the upload to the DLS, whatever the route was fine when uploaded and now it has the dreaded red exclamation mark next to it in the route selection window.
I just had a look in the route and when I click on a faulty asset it gives me a 'loading asset " message, I don't know if this is unusual with a faulty asset as I've never tried to insert one if they show red in CM.
 
Last edited:
So make sense of this, I fired up an earlier build of trs 2022 122418 which is using the exact same build on the same ssd drive and the route has no issues whatsoever, so I think it must be something to do with using 2022pe. Heinrich had issues with his first install, I had to install a patch upwards ( although this did fix the problem for a while. But this is just crazy. the route is installed but will not appear in the route selection presumably ,because it was made in a later version of 2022
 
grazlash said:
I have TRS22PE 126273 and only getting warnings on those trees
Click to expand...
i dunno how I'm going to ever diagnose just what is going on here as its ceased and then returned, and yet, I've done nothing to change the install or build, not even used it recently until Heinrich told me he has this issue ! !
 
I have both Alpine Tunnel and Timber Ridge installed in both TRS19 build 117009 & TRS22 PE build 126273 and both routes have no faulty assets or missing dependencies. The only issue I had was in the Alpine Tunnel route with textures not aligning correctly in TRS22. That is an issue known to N3V who made it clear that with textures set to Ultra this could happen. I reduced the setting to High and the issue was resolved. That was nothing to do with the route or Dans tremendous work but a known problem with the TRS22 game engine.
 
I'm using a pc , nvidea 1660t1 6gb. I dunno what Heinrich has , it appears to be a pre caching issue , is that a clue?
what I can't understand is, why did the patch to sp4 fix the issue and now , although I've not changed any settings, it's returned? Why are built in and packaged st rmm trees and shrubs not affected?
 
dangavel said:
I'm using a pc , nvidea 1660t1 6gb. I dunno what Heinrich has , it appears to be a pre caching issue , is that a clue?
what I can't understand is, why did the patch to sp4 fix the issue and now , although I've not changed any settings, it's returned? Why are built in and packaged st rmm trees and shrubs not affected?
Click to expand...
I've been looking into this with Gary. I have zero errors and warnings with all of the st_rmm trees installed.

I have him checking right now for specific missing and faulty assets. It could be a broken library installed by one of the non-RMM versions of the st_rmm trees that's causing this. An updated library not including a mesh referenced in a mesh-table can break a whole bunch of assets if the library uses the same KUID and version as the original. I've seen this with tracks, catenary and other assets that reference components in a mesh-library.
 
I am using PC with Nvidia RTX4080 and I have just deleted the <kuid2:211025:21345:1> from TRS22 PE and checked that it shows as missing dependency in both routes, it does. I then reinstalled it and it reinstalled with no errors. I would suggest you try deleting the libraries as detailed by CJitron in this thread https://forums.auran.com/threads/trs19-library-cache-corrupted.175400/#post-1990914

That has worked for me when I have had issues where Trainz seemed to have a memory for deleted or faulty items.
 
Thanks for all the help guys, however, you probably wont believe this, but this is what occurred this am,
As I said earlier, I fired up 2022 PE yesterday after opening an earlier version using the same build on an external SSD.
Today I thought I would attempt another extended database repair as a last resort in 2022PE.
Could not do a database repair at all, checked and my login wasn't working, NV3 had accepted the log in but could not verify the build number.
I restarted laptop twice, attempted 2022 PE login a few times, it seemed to hang and no FCT or successful login message .
Clicked on the driver surveyor window launch that appeared, but no routes
then I had another go at the launcher and lo !
2022 PE appeared and my FCT also was verified.
I then did a normal database repair and now the entire lot of ST rmm tress are now showing no faults at all , the timber ridge route in CM is now showing no issues at all.... for now ......
isnt trainz wonderful ? ........


I feel like tearing out whats left of my hair......as you can see at the moment my emotions re trainz are mixed to say the least........:mad::p:oops::rolleyes::giggle::p:eek:o_O:cautious:;)
 
I've had a DBR run without showing a progress bar in Plus. Something happened that caused the database to become corrupted. I would back everything up and run a DBR anyway.
 
You must log in or register to reply here.
Back
Top