Gaulish Gaming Banquet: editor

adrientd

lol

adrientd

Since the min/max range of the choreokey duration is broken, wouldn't it make sense to change the editor to only show the min, and setting max to be the same as min? Unless there's an usecase for having very slight randomness as the actual duration is closer to min the more FPS you have.

pegperegogaucho

I've already used it nontheless a couple of times :Obelul:

pegperegogaucho

Adrien, would it be possible for the inspector to load the addendum?

pegperegogaucho

Also, maybe it would be cool if you two <@&1311814439649153094> @adrientd could work out a way to bring over the position saver into the inspector because it's really useful for testing!

pegperegogaucho

Freecam is good as well

pegperegogaucho

Because I'm looking for the memory inspection features of the editor + the nice tools by the cheat tool

adrientd

It should be possible to implement I guess, you would have to open the file XEADD%03i.KWN right after the LVL. Ideally it should be possible to use the file class by Kal and deserialize pointers through Kal, then when you deserialize the added info for a particular object, you could make a map from a Kal object pointer to the added data. Possible yes, but when it's going to be implemented, not sure :Obelul:

adrientd

I think I already have tons of things to do in the XXL Editor, and maybe other projects, so not sure if I will ever be able to update the XXL Inspector.

adrientd

I haven't updated it in a while and most likely won't :/

pegperegogaucho

That sucks! But it's not a big deal

pegperegogaucho

But the position saver, is that possible? Apparently hesopesomeso might not have the code anymore, so that could be out of question as well.

adrientd

If he lost the code, oh well...

adrientd

Maybe it might be possible to load both the Inspector and Cheat tool at the same time?

adrientd

Maybe through the ASI Loader but not sure

pegperegogaucho

I don't think that is a good idea unfortunately because of the main window, there would be two copies and maybe it would even crash

hesopesomeso

You could boot up a different program along with the cheat tool to act as the inspector, no? Since I've lost the ugly ass code, don't think I want to rewrite everything from scratch (especially the position saver image feature - D3D9/X is a load of crap). Additionally, my XXL1 tools will be :Soon:

done, so there won't be any need for it anyways.

pegperegogaucho

The main problem is you removed some useful functionality of the inspector, like having the cheats separated into another window, the scene tree and also added the annoying fov patch :Obelul:

hesopesomeso

I haven't added that (fov patch) :Obelul:

that's within the inspector! I always left the windows there, as I thought they were useful. Well, speedrunners complained... :)

pegperegogaucho

Must be a new feature of the inspector

#editor