If your .ref file entey is written with the correct syntax but the filename was misspelled and is now pointing at nothing at all, TSRE will still have the .ref file entry in the list of place-able objects. When you select and place that item the properties window will display x, y, z values as-if it actually placed an object... but nothing is visible because the filename wasn't pointing to a real shape file.
It's not a problem for the software or the world files but it can be very confusing for the user -- the descriptive phrase is correct and it is in the list of available objects to place... you wind up wondering where it went, waste time trying it again -- was the origin point wildly off?? -- etc. etc.
No real harm but it is confusing. KUJU's RE does bother checking, warns when this condition occurs, and the description is not included in the list of available objects to place. It would be nice if TSRE did the same.
Page 1 of 1
Placement bug (minor)
#2
Posted 11 November 2018 - 03:29 PM
Genma Saotome, on 07 November 2018 - 06:40 PM, said:
If your .ref file entey is written with the correct syntax but the filename was misspelled and is now pointing at nothing at all, TSRE will still have the .ref file entry in the list of place-able objects. When you select and place that item the properties window will display x, y, z values as-if it actually placed an object... but nothing is visible because the filename wasn't pointing to a real shape file.
It's not a problem for the software or the world files but it can be very confusing for the user -- the descriptive phrase is correct and it is in the list of available objects to place... you wind up wondering where it went, waste time trying it again -- was the origin point wildly off?? -- etc. etc.
No real harm but it is confusing. KUJU's RE does bother checking, warns when this condition occurs, and the description is not included in the list of available objects to place. It would be nice if TSRE did the same.
It's not a problem for the software or the world files but it can be very confusing for the user -- the descriptive phrase is correct and it is in the list of available objects to place... you wind up wondering where it went, waste time trying it again -- was the origin point wildly off?? -- etc. etc.
No real harm but it is confusing. KUJU's RE does bother checking, warns when this condition occurs, and the description is not included in the list of available objects to place. It would be nice if TSRE did the same.
Yes same issue happened to me, initially making me suspect the .s file i had generated was corrupt.
#3
Posted 03 December 2018 - 11:11 AM
Another thought on this. Perhaps the most efficient solution would be for the TSRE assets to include a simple shape -- a cube -- square or three sided -- whose texture said "Missing .s file". When the software goes to get the .s file to place, notices it didn't get anything, moves the .s, .sd, and texture files into the route (if not already there) and then place the "missing .s file" shape. That would avoid the lengthy test at startup to see if everything is present. The appearance of the unusual shape fills the feedback "gap" for the user and tells him what is wrong.
Page 1 of 1