Quote:
Originally Posted by Felix Nephthys
Ok, I don't know what this import function is so you'll have to enlighten me. However, let me just see if I can drive down to the bedrock of what you are wanting to accomplish (let me know if I'm in error).
|
The function he is referring to never made it past initial testing before SP2WW2 was first released in 1998 as it was revealed very quickly how easy it was for bad data to be put in and a lot of work on an OOB was lost and had to be redone. The button for that function was still in the MOBHack issued with the DOS games but it was deactivated and occasionally someone asked about it but was removed when we reissued MOBHack with the first Windows version. The only reference to it is in the MOBHack Help files
Quote:
|
Dump CSV button - This dumps 3 Comma Separated Value (CSV) files for the currently loaded OB file - these can be read by such spreadsheet programs as Excel or database programs like Access. This is for internal Camo Workshop team usage, and is meant to provide a data dump for comparisons, data checking and so on. There are no guarantees that all the data fields are in there, this facility is an unsupported extra to an unsupported product!. (To answer an oft asked question - there is deliberately no CSV import, as the only method used in early versions of the editor had zero error checking. Adding Error checking would have taken too much effort. Too many folk used a spreadsheet or similar and then uploaded duff data, so this was removed, and the facility is only included for output now). It is very useful for checking consistency
|
So it has not been active for 22 years and in that time we have expanded the existing OOB's and introduced MBT all without ever needing it and AFAIK the section of code that ran it was removed from both games MOBHack code.
DO NOTE we are told
Quote:
|
Only an insane person would go into every OOB and change every range, item by Item. It's at least 25000 clicks and error prone.
|
Yet that is exactly what we are expected to do to make this change to both SPWW2 and SPMBT not to mention all of the peripherals like the Armour Pen calc that is set up in the standard 50 meters/yards and of course the game's code for distance as well.
I can well imagine the "solution" would be for us to re-introduce the function and add error checking and that is not going to happen.
The game scale is what it is and is not going to be changed.
As for infantry unit frontages
https://balagan.info/infantry-unit-frontages-during-ww2