Report, edit, etc...Posted by TERRAINFIGHTER on 2005-12-20 at 22:32:18
QUOTE(petphot @ Dec 20 2005, 09:08 PM)
can u fix and post soon? im missing DatEditor already 
[right][snapback]384906[/snapback][/right]
[right][snapback]384906[/snapback][/right]
No, I can't fix it cause I didnt make DatEdit...I'm only a tester
Report, edit, etc...Posted by LoRdOfWaR]Dark[ on 2005-12-21 at 01:39:12
QUOTE(petphot @ Dec 20 2005, 06:08 PM)
can u fix and post soon? im missing DatEditor already
[right][snapback]384906[/snapback][/right]
[right][snapback]384906[/snapback][/right]
yes fix it
im missing it to x*PReport, edit, etc...Posted by Lord_Agamemnon(MM) on 2005-12-21 at 13:35:38
Save us, Broodkiller! Free us from our despair!
Report, edit, etc...Posted by petphot on 2005-12-21 at 14:01:33
My mod might just have to wait till he fixxes the DatEdit error...
Report, edit, etc...Posted by Lord_Agamemnon(MM) on 2005-12-21 at 14:13:00
Oh, I had an idea for the final release(if it's possible): Give the program the ability to open an entire arr folder. If you do, we won't need to open units.dat, weapons.dat, etc. every time we load custom files. Just a thought.
Report, edit, etc...Posted by petphot on 2005-12-21 at 14:17:41
hmm good idea...
ADDITION:
maybe if you want to expand DatEdit you can make it have similar features to the programs ICE and MemGraft. That way people dont have to keep switching between programs
Maybe u can improve the added in MemGraft software too (like make it so it can ACTUALLY load its own files)
ADDITION:
maybe if you want to expand DatEdit you can make it have similar features to the programs ICE and MemGraft. That way people dont have to keep switching between programs
Maybe u can improve the added in MemGraft software too (like make it so it can ACTUALLY load its own files)
Report, edit, etc...Posted by TERRAINFIGHTER on 2005-12-21 at 15:27:04
QUOTE(petphot)
maybe if you want to expand DatEdit you can make it have similar features to the programs ICE and MemGraft. That way people dont have to keep switching between programs
Maybe u can improve the added in MemGraft software too (like make it so it can ACTUALLY load its own files)
Maybe u can improve the added in MemGraft software too (like make it so it can ACTUALLY load its own files)
I dont think he intends on adding features other then .dat editing (except possibly mpq functions)
Report, edit, etc...Posted by BroodKiller on 2005-12-21 at 15:53:38
QUOTE
Hmm... I don't think the build time is in ms though...
Even up to 27 seconds, pal. It's still very little though...
###The Bug###
Ow-key, I think I know what is the problem here. The unit size data is stored as an 8-bit long variable, but DatEdit only uses 4-bit long variables. So, in order to be able to edit this property I split it into 2 4-bit variables that are handled separately.
This should work fine if you're editing an already existing file (please, test if the corruption happens if you're only editing a file, not "Save As"-ing it), but the problem appears when you save the data into a new file.
Normally, the file output routine (read:the one that does the saving stuff) just writes the data in a linear way, that is one bit after another. However, because the Unit Size property is controlled by two different variables, it corrupts it becase it writes in a linear way the data that should be written as "var1+var2".
I think I already know how to fix this. Stay tuned...
EDIT:Actually, I expected something like this to happen, but those few tests I did with this Beta didn't show anything wrong, so I thought that *magically* the problem disappeared.
Report, edit, etc...Posted by Voyager7456(MM) on 2005-12-21 at 16:31:12
QUOTE(BroodKiller @ Dec 21 2005, 02:53 PM)
Even up to 27 seconds, pal. It's still very little though...
###The Bug###
Ow-key, I think I know what is the problem here. The unit size data is stored as an 8-bit long variable, but DatEdit only uses 4-bit long variables. So, in order to be able to edit this property I split it into 2 4-bit variables that are handled separately.
This should work fine if you're editing an already existing file (please, test if the corruption happens if you're only editing a file, not "Save As"-ing it), but the problem appears when you save the data into a new file.
Normally, the file output routine (read:the one that does the saving stuff) just writes the data in a linear way, that is one bit after another. However, because the Unit Size property is controlled by two different variables, it corrupts it becase it writes in a linear way the data that should be written as "var1+var2".
I think I already know how to fix this. Stay tuned...
[right][snapback]385559[/snapback][/right]
###The Bug###
Ow-key, I think I know what is the problem here. The unit size data is stored as an 8-bit long variable, but DatEdit only uses 4-bit long variables. So, in order to be able to edit this property I split it into 2 4-bit variables that are handled separately.
This should work fine if you're editing an already existing file (please, test if the corruption happens if you're only editing a file, not "Save As"-ing it), but the problem appears when you save the data into a new file.
Normally, the file output routine (read:the one that does the saving stuff) just writes the data in a linear way, that is one bit after another. However, because the Unit Size property is controlled by two different variables, it corrupts it becase it writes in a linear way the data that should be written as "var1+var2".
I think I already know how to fix this. Stay tuned...
[right][snapback]385559[/snapback][/right]
But then the Marine would have a build time of 360 ms, which would be less than a second.
I can't get the Save feature to work at all.
It just says "File saved successfully", but no changes are made.Report, edit, etc...Posted by Lord_Agamemnon(MM) on 2005-12-21 at 16:47:00
QUOTE(BroodKiller @ Dec 21 2005, 02:53 PM)
Please, test if the corruption happens if you're only editing a file, not "Save As"-ing it
It occurs whenever you open a file in Datedit. No editing is necessary; simply open it, save it, and watch it get corrupted.
Report, edit, etc...Posted by TERRAINFIGHTER on 2005-12-21 at 18:28:33
QUOTE(BroodKiller)
This should work fine if you're editing an already existing file (please, test if the corruption happens if you're only editing a file, not "Save As"-ing it), but the problem appears when you save the data into a new file.
Actually, I tested both "Save" and "Save as..." and they both mess up the height
Report, edit, etc...Posted by petphot on 2005-12-21 at 18:32:24
Hope this gets fixxed soon
Report, edit, etc...Posted by BroodKiller on 2005-12-23 at 08:13:33
Ok, I fixed the bug. It turned out to be much less serious that I thought. To be perfectly honest - the bug was a result of my typo ...
The output routine for the Unit Size was writing only 2 bytes of data, instead of 4. It was a matter of simply changing the number....damn, I do suck if I make such mistakes.
I will upload the new build ASAP (can't do this from where I am now)
Eh...? Sorry, I misunderstood you - I thought you were speaking about the time that takes the build of the program, actually....
This may be because you changed the "Reload after Save" option. Now that I think of it, It is seriously mislabeled (but I fixed this in the new version). What this does is - if unchecked - after you "Save As" a file, it will not make the editor edit the newly saved file, but it will stay with the original one. Thus, the changes will be reflected only in the newly saved file, and the original one will be kept intact.
ADDITION:
###DatEdit 0.91 fix###
I fixed the Unit Size bug that have been discussed above. Shouldn't cause any more problems =)
As for other stuff in this release:
-Added confirmation on exit
-Made the application window resizable by default
-removed the options menu (the resizing is default, and the other option causes more problems than it is actually worth)
However, the options are not gone completely. I just removed them until I can work out a config file to store the settings from one session to another (I'm having some strange problems with this...)
So, enjoy (and test it out, of course).
ADDITION:
###DatEdit 0.91 fix###
I fixed the Unit Size bug that have been discussed above. Shouldn't cause any more problems =)
As for other stuff in this release:
-Added confirmation on exit
-Made the application window resizable by default
-removed the options menu (the resizing is default, and the other option causes more problems than it is actually worth)
However, the options are not gone completely. I just removed them until I can work out a config file to store the settings from one session to another (I'm having some strange problems with this...)
So, enjoy (and test it out, of course).
file link removed. Use SEN's Download DB instead =):
http://www.staredit.net/index.php?download=4668
The output routine for the Unit Size was writing only 2 bytes of data, instead of 4. It was a matter of simply changing the number....damn, I do suck if I make such mistakes.
I will upload the new build ASAP (can't do this from where I am now)
QUOTE(Voyager)
But then the Marine would have a build time of 360 ms, which would be less than a second.
Eh...? Sorry, I misunderstood you - I thought you were speaking about the time that takes the build of the program, actually....
QUOTE(Voyager)
I can't get the Save feature to work at all. sad.gif It just says "File saved successfully", but no changes are made.
This may be because you changed the "Reload after Save" option. Now that I think of it, It is seriously mislabeled (but I fixed this in the new version). What this does is - if unchecked - after you "Save As" a file, it will not make the editor edit the newly saved file, but it will stay with the original one. Thus, the changes will be reflected only in the newly saved file, and the original one will be kept intact.
ADDITION:
###DatEdit 0.91 fix###
I fixed the Unit Size bug that have been discussed above. Shouldn't cause any more problems =)
As for other stuff in this release:
-Added confirmation on exit
-Made the application window resizable by default
-removed the options menu (the resizing is default, and the other option causes more problems than it is actually worth)
However, the options are not gone completely. I just removed them until I can work out a config file to store the settings from one session to another (I'm having some strange problems with this...)
So, enjoy (and test it out, of course).
ADDITION:
###DatEdit 0.91 fix###
I fixed the Unit Size bug that have been discussed above. Shouldn't cause any more problems =)
As for other stuff in this release:
-Added confirmation on exit
-Made the application window resizable by default
-removed the options menu (the resizing is default, and the other option causes more problems than it is actually worth)
However, the options are not gone completely. I just removed them until I can work out a config file to store the settings from one session to another (I'm having some strange problems with this...)
So, enjoy (and test it out, of course).
file link removed. Use SEN's Download DB instead =):
http://www.staredit.net/index.php?download=4668
Report, edit, etc...Posted by Darius.DeValle on 2005-12-23 at 10:20:39
I just downloaded DatEdit for the second time, and although I hadn't actually done any modding with it yet, I did notice something. When you had the resize option set as, well, an option, it resized everything perfectly. When set as a default option, it only increases the overall size of the window, but moves none of the boxes or buttons like it did in the last release. It also obscures the ID# box at the bottom...
Report, edit, etc...Posted by Lord_Agamemnon(MM) on 2005-12-23 at 10:34:18
QUOTE(BroodKiller @ Dec 23 2005, 07:13 AM)
###DatEdit 0.91 fix###
I propose that we nominate BroodKiller for Starcraft Modding Sainthood. Anyone who can save us from Arsenal III's intermittent crashing and Arsenal Zero's lack of a decent interface truly deserves it. Thanks, BroodKiller!
And, if memory serves correctly, the build times listed in .dat files are in FIFTHS of a second.
Report, edit, etc...Posted by Pauper on 2005-12-24 at 20:46:16
Is data edit out yet? If so where can i get it?
Report, edit, etc...Posted by Doodle77(MM) on 2005-12-24 at 21:03:59
just look above...
Report, edit, etc...Posted by TheEvilBeaVer on 2005-12-25 at 22:56:07
Pubblic BETA ! YAY 
Report, edit, etc...Posted by Darktossgen(MM) on 2005-12-26 at 13:09:20
There is a bug that, when you Overwrite a file nothing happens.I did not change the '' Reload After Save '' tab, nor anything but unit HP, Shields, and Weapons. (and AI Actions, Graphics... Etc.)
Report, edit, etc...Posted by Nightfire on 2005-12-27 at 00:10:16
I dont know if this is the place to put this but I just thought of a few features that would be nice to have in DatEdit.
1. The ability to copy all of a units propertys to another unit inculding their sounds.(arsenal III does not copy the sounds)
2. The ability to preview sounds/grp's in their respective editors.
Hmm thats all I can think of for now.
I'll understand if you cant make the second one happen but I just thought I would ask.
1. The ability to copy all of a units propertys to another unit inculding their sounds.(arsenal III does not copy the sounds)
2. The ability to preview sounds/grp's in their respective editors.
Hmm thats all I can think of for now.
I'll understand if you cant make the second one happen but I just thought I would ask.
Report, edit, etc...Posted by Staredit.Net Essence on 2005-12-27 at 03:12:38
QUOTE(TERRAINFIGHTER)
it enables animations other then turning therefore if you set it to 127 for the zealot it wont be able to walk cause it cant play movement animation but if you set it to 127 for the drone it will still be able to move just wont play movement animation cause it uses a float command and not a walking command
And I think the reason the interceptor has 60 in the number is cause you cannot control them without controling them through the carrier and the movement is read from the Iscript or hardcoded
[right][snapback]325941[/snapback][/right]
QUOTE(terrainfighter)
And I think the reason the interceptor has 60 in the number is cause you cannot control them without controling them through the carrier and the movement is read from the Iscript or hardcoded
[right][snapback]325941[/snapback][/right]
Prolly tru, set the number to 60 and u get no movement controlls, set it to 127 and u get the movement controlls but no actions
ADDITION: i think i got it!
ur wrong about the zealot, because it has iscripted flingy...lol
when its flingy'd movement ect, and the number is 30, this means there is movement controlls but no actions, it just "hovers", but for air units, if the number is 30, then there is movement and controlls, meaning it does have actions, but if its 127, it has only controlls and just "hovers" like the ground units do at 30...
i havnt tested this tho...
Report, edit, etc...Posted by TERRAINFIGHTER on 2005-12-27 at 13:45:02
That was a major typo I made that I corrected later on...
That value isnt even read by starcrafts exe and does nothing (according to DoA)
That value isnt even read by starcrafts exe and does nothing (according to DoA)
Report, edit, etc...Posted by Darktossgen(MM) on 2005-12-27 at 14:08:55
I have a feature for DatEdit... But its pretty hard. The Ability to preivew the changes you have made to all the .dat files.
Like if you made a change in units.dat so that hydras looked like Dragoons and had Burst lasers, it would show a dragoon shooting burst lasers at ___.
And that it had a drop down list in the preivew tab, so you only had to view one units changes at a time .
You get the idea now, right?
*of course they do,...right?*
*Hopes*
Like if you made a change in units.dat so that hydras looked like Dragoons and had Burst lasers, it would show a dragoon shooting burst lasers at ___.
And that it had a drop down list in the preivew tab, so you only had to view one units changes at a time
.You get the idea now, right?
*of course they do,...right?*
*Hopes*
Report, edit, etc...Posted by TERRAINFIGHTER on 2005-12-28 at 15:18:41
Just a sugguestion, but you should make it so when you "Jump to ID #:" it doesnt make that noise...
It sounds like the programs having a error
It sounds like the programs having a error
Report, edit, etc...Posted by BroodKiller on 2005-12-29 at 15:19:22
QUOTE
I just downloaded DatEdit for the second time, and although I hadn't actually done any modding with it yet, I did notice something. When you had the resize option set as, well, an option, it resized everything perfectly. When set as a default option, it only increases the overall size of the window, but moves none of the boxes or buttons like it did in the last release. It also obscures the ID# box at the bottom...
Yeah, I know that. Wait for DatEd 0.92 (which I work on currently) to have this fixed.
QUOTE
There is a bug that, when you Overwrite a file nothing happens.I did not change the '' Reload After Save '' tab, nor anything but unit HP, Shields, and Weapons. (and AI Actions, Graphics... Etc.)
Strange...try DatEdit 0.91 and see if the bug appears in it. I tried and overwriting worked fine (for me at least).
QUOTE
1. The ability to copy all of a units propertys to another unit inculding their sounds.(arsenal III does not copy the sounds)
2. The ability to preview sounds/grp's in their respective editors.
Hmm thats all I can think of for now.
I'll understand if you cant make the second one happen but I just thought I would ask.
2. The ability to preview sounds/grp's in their respective editors.
Hmm thats all I can think of for now.
I'll understand if you cant make the second one happen but I just thought I would ask.
Ad. 1-This has been already asked for. I'll see what I can do...
Ad. 2-I thought about this feature already, if you wanna know. Previewing sounds can be done only through external MPQ manipulation, which is doable, but I'm getting some strange errors while working with the MPQs, so I can't really tell if I will succeed with this. Previewing GRPs goes the same way.
QUOTE
I have a feature for DatEdit... But its pretty hard. The Ability to preivew the changes you have made to all the .dat files.
Honestly, I know this is doable, but I don't really see the point. If you know what you're doing, and if you can trust the program you're using-you won't need anything like that. 8)
QUOTE
Just a sugguestion, but you should make it so when you "Jump to ID #:" it doesnt make that noise...
I don't understand. The program should not make any noise at all. It doesn't make any when I try it...