While working through the whole thread I am now summarizing the problem.
Therefore let me verify/falsify a couple of assumptions and hypotheses:
Hans, what exactly is this "Remap IDs" under "Tools" in S3D? Wouldn't that help us?
If you use the remap Option a whole unit(file) will geht everywhere New IDs.
So in that case we would have to reassign everything again. Shipwaves, damage files, sounds, etc.
Remap only recreates the IDs _within_ that one selected unit you just opened.
But it is unclear what you mean by "have to reassign everything".
PM just confirmed that there are no other references that need to be reassigned - from where have you got that, Gunnar?
We are JUST NOW talking about this online - so if you could come online and talk this would really bring us forward and clear another misunderstanding.
Quote from: Grey Eminence on 20161212, 20:34:51
What pisses me off is that it seems we are trying to fix years of lazyass work from other modders who
couldn't be bothered to check if there were duplicated IDs for the ships they were creating copying others.
True! And what pisses me off even more is that we only have this assumption and no evidence that the way proposed WILL work.
I admire Blitz for taking all the efforts!!
Grey is correct. Read on why.
Quote from: Philipp_Thomsen on 20161122, 01:04:29
Reason for this is, for some reason some of these IDs are duplicated, so when the game calls for an ID already in use, game crashes.
By replacing these IDs with new IDs, we should be preventing these crashes.
This hypothesis is most apparently
wrong. Read on as to why.
Quote from: HanSolo78 on 20161119, 09:22:14
The origin of these duplicated IDs is probably Bad cloning from other units. This tool appears the First time on subsim and I think not many do know it. So Most people were not aware that the new units they did have duplicated IDs with existing ones. It was always in my mind that this could be very complicated ... new units... No one ever had a look to the entire mega mods.
This assumption is
partly wrong.
The "problem" of duplicated IDs (if there is one, read on!) has not come to life with the mods or mega-mods!
Reason: I have scanned GWX3 and WAC4 with the D-Finder and they both have duplicated IDs, too!
Even stock 1.4b has! And all them three do not crash.
Conclusion: The crashes do NOT have their root in the duplicated IDs, otherwise GWX3, WAC4 and stock1.4 would crash, too (which they do
not)
Quote from: HanSolo78 on 20161122, 14:21:57
What is the root cause of these duplicated IDs?
Who cloned what and where?
Does WAC 4.1 also have these duplicated IDs?
Do also other mods such as GWX have these duplicated IDs?
I sense there might be a totally different problem that came much later than WAC 4.1...
The root is every ship/unit creator. Every unit is cloned from an existing unit. Then the IDs are renewed by the creators. Unfortunately only Most of IDs from the .dat files were only renewed, not all. IDs from all other ship files are more often duplicated.
WAC4.1 has also duplicated IDs, but probably not that much. Gwx I dont know. I dont have it installed. But it does not change one Thing. The problem is real and there is nothing that can be done except solving this problem.
As explained above, this problem is no problem for WAC4, GWX3 and stock.
So it cannot be the IDs that cause WAC5 to crash.
Prozedurmeister was correct when doubting it - he was also asking for proof:
duplicated IDs which probably cause the CTDs as a unit which has duplicated IDs also cause SH3 to collapse.
Is that certain?
Most obviously, following the above argumentation, this is not the case.
It is of course true that Duplicated IDs are no good, and certainly even PACK3D only copied existing IDs.
But I fail to see why GWX3 and WAC4 would not crash - they contain bunches of these duplicated IDs as well!