Search results

Ok then I'll simply use a very very high negative value as the flag for "not set" and still allow user to set negative values other that this specific one, which they will never have to use anyway.

Ok so probably not a big deal if I prevent the user from setting negative value and use -1 as the "not set" value. I must use an explicit number value for the not set value (can't use null) because those fields are present in the right form with the spinners. Those spinners are connected to the...

Is is possible to have negative z values for boxes ? If not I can add a workaround using -1 under the hood to reference unset values.

I think it something related to grabdistance or something. But basically this is why there's a bug with this field. For any other field its straightforward, no value can be considered as 0, but not in this case.

Probably because you rarely set bbox z value manually. I just checked it's a very old bug. It has nothing to do with the value 50 or something, it just takes whatever value is there when the value of the new focused bbox is unset or is 0. Basically it's a bug related to how bbox work. When you...

I see. You can see that the value was already 50 on the left, before you drew the box. It seems that for some reason CMT is taking this as default Z value when not set. I don't think it's new though, probably here since a long time. You probably set the z value to 50 one time in an animation...

I don't understand, nothing has changed, it doesn't add z value. Maybe it's a special situation but even when I test on my end, it doesn't add z value

Happy birthday :)

Added support for this request @O Ilusionista

Piccolo updated Chronocrash Modders Tools with a new update entry: Changelog 0.6.20 Read the rest of this update entry...

Fixed this bug

Piccolo updated Chronocrash Modders Tools with a new update entry: Changelog 0.6.19 Read the rest of this update entry...

Sure but it's a workaround the problem, the problem is still there, and it should work properly by default.

It's the same issue as O Ilusionista reported a few hours before. Don't know if you realized or if its a coincidence. I'll fix it, but it's one example that illustrate well how the legacy system can be a PITA to support. As for the order of dropv/hitfx and so on, I didn't check but I would be...

Hello, in one of your entities files you have "94s" somewhere. Instead of what should be "94". You probably used Ctrl + S to save this file, and one time the "Ctrl" key wasn't properly held so you input "s". I suggest you use a file search software and search for the string "94s" in the content...

- Fixed this bug @O Ilusionista - Save icon in main editor (the one next to undo and redo buttons) will now indicate if current file is saved or not. There was already a save indicator in the left panel, but this one is useful when you have lots of files opened and still want to see a save...

Piccolo updated Chronocrash Modders Tools with a new update entry: Changelog 0.6.18 Read the rest of this update entry...

In the update I documented that if you want to reset those parameters you have to remove/add the project again. But yes manually editing the global ini works too.

Great ;) Good that you mention that, actually this button is not finished (forgot to remove it) and during development I replaced its function with the new prompt that you get when loading project for the first time : So the idea of this button was to basically let users choose the global...

I'm assuming you mean the difference between legacy "single" style command (attack x y z ...) and new "property" style command (attack.property x) As a game developer, the best thing is probably that you don't have to count and refer to the manual to know which parameter refer to what. It's not...