What a difference!!! (and a question)

[TORDO222]

Originally Posted by MarkShot

I think I worked out the error messages.

One thing I notice recently is that in GitHub, a couple of logs files have the same statement as yours ("sharedassets0.assets' is corrupted!"). I even assumed some kind of intentional maneuver to damage the material to unload.None of those involved in development answered my question.So that’s all speculation. Maybe groundless on my part.I’m glad you fixed the issue of error messages.It would be useful for everyone if you told us what you found out about it and what you did to fix it. Greetings!. Marcelo

[MarkShot]

For some reason, I had other follow on files in my install which caused those conflicts. I must have seen a post my first day aware of DOT-MOD (out of date) and added those.


All you need is DOT-MOD and the modded DLL, if you want to change sensors.


BTW, the log (unmodded) will have a couple of errors if the game is not in the Steam default path. They programmatically create and attempt to read a file. They use hard coded and not symbolic or relative paths. This is poor programming style.


But, in any case, it works fine.

[TORDO222]

Originally Posted by MarkShot

For some reason, I had other follow on files in my install which caused those conflicts. I must have seen a post my first day aware of DOT-MOD (out of date) and added those.


All you need is DOT-MOD and the modded DLL, if you want to change sensors.


BTW, the log (unmodded) will have a couple of errors if the game is not in the Steam default path. They programmatically create and attempt to read a file. They use hard coded and not symbolic or relative paths. This is poor programming style.


But, in any case, it works fine.

Excellent description of a possible root of ALL problems.......Enjoy the mod. Greetings!.Marcelo

[Firebar]

Originally Posted by TORDO222

One thing I notice recently is that in GitHub, a couple of logs files have the same statement as yours ("sharedassets0.assets' is corrupted!"). I even assumed some kind of intentional maneuver to damage the material to unload.None of those involved in development answered my question.So that’s all speculation. Maybe groundless on my part.I’m glad you fixed the issue of error messages.It would be useful for everyone if you told us what you found out about it and what you did to fix it. Greetings!. Marcelo

That’s due to some material changes and code changes that the Unity serialisation system detects and ignores. Just a consequence of how we’ve had to get into the code.

[TORDO222]

Originally Posted by Firebar

That’s due to some material changes and code changes that the Unity serialisation system detects and ignores. Just a consequence of how we’ve had to get into the code.

Ah! good explication. And the solution would then be?. Because,obviously, that way of approaching the bowels of the game brings consequences...Greeetings. Marcelo