|
Re: XML Editor Bug Reports[message #135393]
|
Mon, 09 April 2007 01:00
|
|
Wil473 |
|
Messages:2815
Registered:September 2004 Location: Canada |
|
|
I was in the process of trying to convert the XM25 and RPG-7 over to the new "true" explosive ammo when I noticed that the editor is still treating the variable "High Explosive" as a simple yes/no flag. I'm not sure how long this has been the case but for some time now, the High Explosive variable should take a reference to an index in the Explosives.xml (Please see re: explosive ammo, the wiki description being a a tad out of date, and the DBB modders figuring this out while I was getting unexplained teargas clouds...
http://www.ja-galaxy-forum.com/board/ubbthreads.php/ubb/showflat/Number/118156/page/2#Post118156 )
I tried using excel to fill in indexes linking to explosives.xml; but all this did was make the Editor crash. From looking at the xml right now, the existing explosive ammo types will produce the explosion defined under index 1 in explosives.xml when they strike ground (and the expected old JA2 explosive effect on object/character strikes). Will test later...
Similarly, I noticed the Bipod is a yes/no flag in the editor. I could have sworn before the editor we could actually fill in an actual value for how much bonus one would get when prone.
EDIT: I've just noticed that the suggestion to use ExplosionSize = 4 to activate the true explosive effect seems to have been implemented... partially... still getting a bullet strike effect on hitting a character, Explosion on ground strike, but no harmless animation at least.
EDIT2: Just more thinking, the editor seems to have no direct way of getting at explosives.xml yet (I think this was mentioned before). From the interface perspective, one way to get around this would be for the editor to recognize that on ExplosionSize = 4; the HighExplosive field needs to change from a check box to a button displaying the explosives.xml index the ammotype would link to; clicking the button opens one of those small editing windows used for item properties.
[Updated on: Mon, 09 April 2007 02:11] by Moderator Report message to a moderator
|
|
|
|
|
Re: XML Editor Bug Reports[message #136993]
|
Fri, 27 April 2007 04:42
|
|
Wil473 |
|
Messages:2815
Registered:September 2004 Location: Canada |
|
|
Not sure if this is fixable but this might be important for anyone trying to create "DIY" weapon families via the XML Editor: the XML editor does not like it when you try to duplicate an items that has a "complex series of mergers" (at least it generates an error immediately and offers the quit or try to continue on prompt, I suggest quitting and going back to pre-error version from your last save).
- Earlier this week, I built up the six versions of the SCAR in stats (now that we have the graphics in 1.13 for the current official six plus graphics for SCAR parts). I had no problem duplicating the original SCAR Heavy and SCAR Light to act as the base for the additional four types.
- Then defined the 30 mergers to allow conversion between any one SCAR type to another one.
- Later on I tried to copy the original SCAR-H used previously as the base stats for the much predicted 7.62x39mm SCAR and promptly got the error. All of the SCAR's in my xmls will generate the error (pasted below is the details from trying to duplicate from the original SCAR-H that the other two were produced from). As far as I can tell, the only difference is that when I duplicated the first 4 SCAR's the complicated merger definitions did not exist yet.
The same error occurs when I tried duplicating the HK416 (now HK416 14.5" barrel) after I had defined mergers where all 5.56mm and .223 AR-15 variants in the Hybrid can be merged with a 416 Upper to create the basic HK416 14.5" barrel. As I do not yet have the other 416 in-game graphically, I'm going to take my time building up their stats as new items.
Below is the error I get when I now try to duplicate the original SCAR-H used to generate the other two H variants.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Data.ConstraintException: Column 'firstItemIndex, secondItemIndex' is constrained to be unique. Value '1175, 1180' is already present.
at System.Data.UniqueConstraint.CheckConstraint(DataRow row, DataRowAction action)
at System.Data.DataTable.RaiseRowChanging(DataRowChangeEventArgs args, DataRow eRow, DataRowAction eAction, Boolean fireEvent)
at System.Data.DataTable.SetNewRecordWorker(DataRow row, Int32 proposedRecord, DataRowAction action, Boolean isInMerge, Int32 position, Boolean fireEvent, Exception& deferredException)
at System.Data.DataTable.InsertRow(DataRow row, Int32 proposedID, Int32 pos, Boolean fireEvent)
at System.Data.DataRowCollection.Add(DataRow row)
at BackEnd.DefaultTable.DuplicateRows(DataRow[] rows, DataRow parentRow, Int32 baseKey)
at BackEnd.DefaultTable.DuplicateRows(DataRow[] rows, DataRow parentRow, Int32 baseKey)
at BackEnd.DefaultTable.DuplicateRow(Int32 key)
at BackEnd.XmlDB.DuplicateRow(DataTable table, Int32 key)
at GUI.ItemGridForm.DuplicateMenuItem_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
XML Editor
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/JA%201.13/XML%20Editor.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
BackEnd
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/JA%201.13/BackEnd.DLL
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Web
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.210 (QFE.050727-2100)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
[Updated on: Fri, 27 April 2007 05:17] by Moderator Report message to a moderator
|
|
|
|
|
|
|
Re: XML Editor Bug Reports[message #138034]
|
Tue, 08 May 2007 16:23
|
|
Thor |
|
Messages:423
Registered:February 2007 Location: Belgium |
|
|
Yep, it's something similar
With some Dutch words (using Ditch windows version)
[Updated on: Tue, 08 May 2007 16:24] by Moderator Report message to a moderator
|
Master Sergeant
|
|
|
|
|
Re: XML Editor Bug Reports[message #138166]
|
Wed, 09 May 2007 10:46
|
|
Starwalker |
|
Messages:759
Registered:October 2005 Location: Hannover, Germany |
|
|
Madd Mugsy@Starwalker: What problems are there with the inventory? Can you please list out the steps to recreate the problem? Thanks!
Sorry, I can't, because it did not happen again (which is fine by me).
I simply added some new items, and indicated that Tony should buy them (checked the box, but left inventory at 0).
Saved and then exited the XML-Editor.
SVN showed changed versions for all the files I changed (all Items-xmls, magazines.xml, merges.xml, etc.), but did not show any change for the NPC-inventories, those were left untouched although I changed at least two (Tony and Sam).
I do not remember precisely, but it could be that even the Windows Explorer did not show the new time/date stamp for the inventory-xmls.
But it did not happen again on later runs, so you can probably not recreate it
The other Tony-problem is much more pressing, the German forum is mentioning it more often, but I have yet to see it here on the BP.
Report message to a moderator
|
|
|
|
|
|
Re: XML Editor Bug Reports[message #142603]
|
Sun, 03 June 2007 10:27
|
|
Deus Ex |
|
Messages:37
Registered:July 2006 Location: Sarawak, Malaysia |
|
|
Help! XML editor stopped working!
It occured after the most recent update (rev818). Now whenever I start it up it says "Error: unable to assign constraints" and goes on about some values are unique or some other crap. I think it's the german items XML causing the problems cos' the editor specifically brought up a window with uiIndex 795 in germanitems...oh i can't remember the exact message.
[Updated on: Sun, 03 June 2007 10:44] by Moderator Report message to a moderator
|
Private 1st Class
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: XML Editor Bug Reports[message #159865]
|
Sun, 30 September 2007 00:50
|
|
E4MC |
|
Messages:6
Registered:August 2007 Location: Arizona, USA |
|
|
I gave Starwalker some correct weights for items in the last few days, and he made changes to the game. After updating with the SVN yesterday I noticed that the weights sill didn't seem right, and some of my IMP's items that had been the correct weight were now much heavier. So I checked the xml editor to see if someone had edited weights, but the xml editor was showing the correct weights in hexagrams for what my IMP's items used to weigh.
For example, the Colt M4 Commando weighs 5.5 lbs in real life and in the game. 5.5 lbs converts to metric 24 hg, which was the setting for its weight in the xml editor. However, after the update, the Commando's in-game weight is now incorrect at 6.8 lbs, but its xml editor weight is correct at 240 hg.
Before I updated, 10 hg set with the editor equaled the correct conversion of 2.2 lbs in game. After the update, 10 hg converted incorrectly to 2.6 lbs in game. I figured that changes had been made to the conversion for some reason or other, so I started experimenting with the editor to find out what each setting would weigh in game so I could make adjustments to items. I started at 0 hg and went up and this is what I found:
0 hg = .1 lb
1 hg = .2 lb
2 hg = .4 lb
3 hg = .7 lb
4 hg = .9 lb
5 hg = 1.1 lb
6 hg = 1.3 lb
7 hg = 1.5 lb
8 hg = 1.8 lb
9 hg = 2.0 lb
10 hg - 2.2 lb
Wait a minute! These are the correct conversion weights in lbs. So I stopped because I figured I must have been mistaken earlier that the conversion was incorrect. But then I noticed that the Commando still weighed 6.8 lbs when it should weigh only 5.5 lbs, so I started checking items again, including items I had already checked, and all of the sudden, 10 hg was incorrectly weighing 2.6 lbs again!
Report message to a moderator
|
Private
|
|
|
|
|
|
|
Re: XML Editor Bug Reports[message #160008]
|
Mon, 01 October 2007 16:11
|
|
Alastor |
Messages:1
Registered:October 2007 |
|
|
Hello!
I seem to have a serious problem getting the editor to run:
Quote:
XML Editor.exe - Application Error
Application has generated an exception that could not be handled.
Process ID=0x260 (608), Thread ID=0x148 (328).
Click OK to terminate the application.
Click CANCEL to debug the application.
I have already deleted the JA2Data.xsd file but it didn't change a thing.
I'm running Win2k pro with SP4 and .NET Framework 2.0 installed.
I'm using the newest vanilla SVN revision 891.
Any ideas on this would be welcome.
Edit:
Looks like I caused that myself -_- :wb:
After installing again and updating to the new SVN build it works. I must've probably screwed up some files with a third party xml editor.
[Updated on: Mon, 01 October 2007 16:50] by Moderator Report message to a moderator
|
Civilian
|
|
|
|
|
|
|
|