1.13 is a platform for mods,so xml editor can be launched for viewing at least with base 1.13 mod without any overhauls.
But some overhauls like AFS,brainmod,Vengence reloaded,etc can drop errors where errors not described properly.So i show few examples:
1)Mod AFS from 2019
The first error appears like that:
11/9/2022 8:05:18 PM - Memory: 18,532,076 - Error:
Source: mscorlib
Base Error Type: System.IO.FileNotFoundException
Message: Could not find file 'F:\Games\Ja\113\Data-AFS\BigItems\p8item00.sti'.
Stack Trace: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access)
at BackEnd.ItemImageManager.LoadBigImages(Int32 type) in J:\JA2 1.13 SVN\xml-editor-test\BackEnd\Images\ItemImageManager.vb:line 97
at BackEnd.ItemImageManager.LoadAllImages(String dataDirectory, Int32 itemTypes) in J:\JA2 1.13 SVN\xml-editor-test\BackEnd\Images\ItemImageManager.vb:line 39
Target Site: WinIOError
Available Physical Memory: 7690547200
Available Virtual Memory: 3897573376
This problem can be solved by removing few files which is not important or not finished.And after fixing such kind of problems another error will appear during loading on ammochoices.xml
11/9/2022 8:11:46 PM - Memory: 113,040,376 - Error:
Source: System.Data
Base Error Type: System.Data.ConstraintException
Message: Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints.
Stack Trace: at System.Data.DataSet.EnableConstraints()
at System.Data.DataSet.set_EnforceConstraints(Boolean value)
at BackEnd.XmlDB.EndInit() in J:\JA2 1.13 SVN\xml-editor-test\BackEnd\Data Access\XmlDB.vb:line 156
Target Site: EnableConstraints
Available Physical Memory: 7589912576
Available Virtual Memory: 3790467072
11/9/2022 8:11:53 PM - Memory: 113,064,952 - Details:
File: Items\Merges.xml
ForeignKeyConstraint Constraint5 requires the child key values (15) to exist in the parent table.
11/9/2022 8:11:54 PM - Memory: 113,064,952 - A fatal error has occured. The application will now exit.
Such kind of errors is also hard to understand.what wrong or how to fix or which line have problem.
2)Brainmod:
11/9/2022 8:21:02 PM - Memory: 166,029,288 - Details:
File: Items\Items.xml
ForeignKeyConstraint Constraint2 requires the child key values (0) to exist in the parent table.
11/9/2022 8:21:05 PM - Memory: 166,037,480 - Details:
File: Items\Weapons.xml
Column 'uiIndex' is constrained to be unique. Value '34' is already present.
Column 'uiIndex' is constrained to be unique. Value '35' is already present.
Column 'uiIndex' is constrained to be unique. Value '50' is already present.
Column 'uiIndex' is constrained to be unique. Value '35' is already present.
Column 'uiIndex' is constrained to be unique. Value '34' is already present.
Column 'uiIndex' is constrained to be unique. Value '50' is already present.
11/9/2022 8:21:11 PM - Memory: 166,086,632 - Details:
File: Items\Launchables.xml
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2321, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2321, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2322, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2322, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2323, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2323, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2324, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2324, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2325, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2325, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2326, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2326, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2327, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2327, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2328, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2328, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2329, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2329, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2330, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2330, 50' is already present.
11/9/2022 8:21:14 PM - Memory: 166,103,016 - Details:
File: Items\IncompatibleAttachments.xml
Column 'itemIndex, incompatibleattachmentIndex' is constrained to be unique. Value '50, 5664' is already present.
Column 'itemIndex, incompatibleattachmentIndex' is constrained to be unique. Value '5664, 50' is already present.
Column 'itemIndex, incompatibleattachmentIndex' is constrained to be unique. Value '5664, 50' is already present.
Column 'itemIndex, incompatibleattachmentIndex' is constrained to be unique. Value '50, 5664' is already present.
11/9/2022 8:21:17 PM - Memory: 166,111,208 - Details:
Those errors seems a problems of duplicating items and can be fixed but next error not giving any clue whats wrong:
File: Items\ExplosionData.xml
ForeignKeyConstraint Constraint2 requires the child key values (502) to exist in the parent table.
ForeignKeyConstraint Constraint2 requires the child key values (503) to exist in the parent table.
3)Vengence:reloaded.Stable version based mod.the plain 1.13 version of stable release launch normally and can be viewed but the overhauls like this mod not even launch.Error appear like this pon loading on mercstarting gear:
11/9/2022 8:26:59 PM - Memory: 59,047,968 - Error:
Source: System.Data
Base Error Type: System.ArgumentException
Message: Input string was not in a correct format.Couldn't store <> in mBig24 Column. Expected type is Int32.
Stack Trace: at System.Data.DataColumn.set_Item(Int32 record, Object value)
at System.Data.DataRow.set_Item(DataColumn column, Object value)
at System.Data.DataRow.set_Item(String columnName, Object value)
at BackEnd.MercStartingGearTable.LoadMSGData(String fileName, String filePath) in J:\JA2 1.13 SVN\xml-editor-test\BackEnd\Data Access\Tables\MercStartingGearTable.vb:line 55
at BackEnd.MercStartingGearTable.LoadData() in J:\JA2 1.13 SVN\xml-editor-test\BackEnd\Data Access\Tables\MercStartingGearTable.vb:line 17
at BackEnd.XmlDB.LoadData(DataTable table) in J:\JA2 1.13 SVN\xml-editor-test\BackEnd\Data Access\XmlDB.vb:line 212
at BackEnd.XmlDB.LoadAllData() in J:\JA2 1.13 SVN\xml-editor-test\BackEnd\Data Access\XmlDB.vb:line 184
at BackEnd.DataManager.LoadData() in J:\JA2 1.13 SVN\xml-editor-test\BackEnd\DataManager.vb:line 132
at GUI.Main.Main() in J:\JA2 1.13 SVN\xml-editor-test\GUI\Main.vb:line 62
Target Site: set_Item
Available Physical Memory: 7432867840
Available Virtual Memory: 3837419520
Can be logs be more specific about problems which cannot be loaded?For average user like me i think such errors hard to understand.
1.13 is a platform for mods,so xml editor can be launched for viewing at least with base 1.13 mod without any overhauls.
But some overhauls like AFS,brainmod,Vengence reloaded,etc can drop errors where errors not described properly.So i show few examples:
1)Mod AFS from 2019
The first error appears like that:
This problem can be solved by removing few files which is not important or not finished.And after fixing such kind of problems another error will appear during loading on ammochoices.xml
Such kind of errors is also hard to understand.what wrong or how to fix or which line have problem.
2)Brainmod:
11/9/2022 8:21:02 PM - Memory: 166,029,288 - Details:
File: Items\Items.xml
ForeignKeyConstraint Constraint2 requires the child key values (0) to exist in the parent table.
11/9/2022 8:21:05 PM - Memory: 166,037,480 - Details:
File: Items\Weapons.xml
Column 'uiIndex' is constrained to be unique. Value '34' is already present.
Column 'uiIndex' is constrained to be unique. Value '35' is already present.
Column 'uiIndex' is constrained to be unique. Value '50' is already present.
Column 'uiIndex' is constrained to be unique. Value '35' is already present.
Column 'uiIndex' is constrained to be unique. Value '34' is already present.
Column 'uiIndex' is constrained to be unique. Value '50' is already present.
11/9/2022 8:21:11 PM - Memory: 166,086,632 - Details:
File: Items\Launchables.xml
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2321, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2321, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2322, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2322, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2323, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2323, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2324, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2324, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2325, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2325, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2326, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2326, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2327, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2327, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2328, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2328, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2329, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2329, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2330, 50' is already present.
Column 'launchableIndex, itemIndex' is constrained to be unique. Value '2330, 50' is already present.
11/9/2022 8:21:14 PM - Memory: 166,103,016 - Details:
File: Items\IncompatibleAttachments.xml
Column 'itemIndex, incompatibleattachmentIndex' is constrained to be unique. Value '50, 5664' is already present.
Column 'itemIndex, incompatibleattachmentIndex' is constrained to be unique. Value '5664, 50' is already present.
Column 'itemIndex, incompatibleattachmentIndex' is constrained to be unique. Value '5664, 50' is already present.
Column 'itemIndex, incompatibleattachmentIndex' is constrained to be unique. Value '50, 5664' is already present.
11/9/2022 8:21:17 PM - Memory: 166,111,208 - Details:
Those errors seems a problems of duplicating items and can be fixed but next error not giving any clue whats wrong:
File: Items\ExplosionData.xml
ForeignKeyConstraint Constraint2 requires the child key values (502) to exist in the parent table.
ForeignKeyConstraint Constraint2 requires the child key values (503) to exist in the parent table.
3)Vengence:reloaded.Stable version based mod.the plain 1.13 version of stable release launch normally and can be viewed but the overhauls like this mod not even launch.Error appear like this pon loading on mercstarting gear:
11/9/2022 8:26:59 PM - Memory: 59,047,968 - Error:
Source: System.Data
Base Error Type: System.ArgumentException
Message: Input string was not in a correct format.Couldn't store <> in mBig24 Column. Expected type is Int32.
Stack Trace: at System.Data.DataColumn.set_Item(Int32 record, Object value)
at System.Data.DataRow.set_Item(DataColumn column, Object value)
at System.Data.DataRow.set_Item(String columnName, Object value)
at BackEnd.MercStartingGearTable.LoadMSGData(String fileName, String filePath) in J:\JA2 1.13 SVN\xml-editor-test\BackEnd\Data Access\Tables\MercStartingGearTable.vb:line 55
at BackEnd.MercStartingGearTable.LoadData() in J:\JA2 1.13 SVN\xml-editor-test\BackEnd\Data Access\Tables\MercStartingGearTable.vb:line 17
at BackEnd.XmlDB.LoadData(DataTable table) in J:\JA2 1.13 SVN\xml-editor-test\BackEnd\Data Access\XmlDB.vb:line 212
at BackEnd.XmlDB.LoadAllData() in J:\JA2 1.13 SVN\xml-editor-test\BackEnd\Data Access\XmlDB.vb:line 184
at BackEnd.DataManager.LoadData() in J:\JA2 1.13 SVN\xml-editor-test\BackEnd\DataManager.vb:line 132
at GUI.Main.Main() in J:\JA2 1.13 SVN\xml-editor-test\GUI\Main.vb:line 62
Target Site: set_Item
Available Physical Memory: 7432867840
Available Virtual Memory: 3837419520
Can be logs be more specific about problems which cannot be loaded?For average user like me i think such errors hard to understand.