[W.I.P] LF2 Data Debugger | Update [4/5/09]

[Boop]

Some bugs:
-There is a weird white dot at the top-left corner behind the sprites when you play as player 3.
-If you press F4 in game, it'll show the red/blue box in the selection menu.
-When you change the sprite facing direction, the box move away a bit.

Beside those, this is spartawesome.

EDIT: Say, why don't you change the x any thing in to centery and centerx instead of the coordinates of where you are standing?

1.White dot = 0,0 ... Where all the stuff is calculated from. It is a feature .
2.Fixed
3. Do you mean when you turn, and you see it flash for a split second? Not much I can do about that, doing complicated maths ;P.
4. Done .

Anyway updated . Read first post.

Looking for design suggestions for the editor... I don't think a blank window is good .

[YinYin]

Looking for design suggestions for the editor... I don't think a blank window is good .

true
you might first of all want to label every input so we know what it is
and then perhaps align in a similar way to the original data

[no one]

The editor window was brillian. Does it change the code in the dat file when you do in the game too?

Only one thing to complain about: hard to code since there is no label.

EDIT: ninja'd.

[YinYin]

i just noticed that the first input is actually the frame itself - thats pretty damn neat

now how about adding centerx/y and other values d:

edit:
theres are one/two things i really really could use this for
wpoint(/cpoint) positioning and weaponact(/action)
because for itrs/bdys i usually create/select the areas as i draw/render the spritesheet and thus its usually right in first place (unless its a really complicated combo/juggling(-possibility) move thing) and hence i would only use this to quickly check whether its all lookin good

with wpoints(/cpoints) you cant really do that - you may get the general area where it needs to go - and the angle(/frame) that might fit - but then you really need to test it in action, with several items(/characters) - doing it manually would take even more effort and time

[kieutuan]

can't save
all changes will be lost when close

[Cerberus]

WOT?! i already DCed bit 2 (yes me) and i ever had problems with this x, y, w, h... but now the problem doesnt exist any longer.
thank u silva!

[genevrier]

can't save
all changes will be lost when close

The LF2 programme load the data into the memory. When you edit it with this debugger, only the data in memory will be edited. (At least, you can know the test the value in real time.)

@Silva
So would it be possible to add a "save to data" button?
(It may require an external procedure to edit the data file though.)

[Triak]

No pictures on the first post