XLua, MMF2 Extension

Textures should be loaded with the OpenGL object. Looki has not exposed the functions to do that directly, only to access the texture IDs after you've loaded them.

Maybe you can do it directly in LuaGL but I haven't looked into it. You don't have access to any glu shortcuts.

yeah i guess that would work too

EDIT: i hope the 256 texture limit isn't a hard limit because that's not even close to making me comfortable

EDIT: apparently the newest version of the extension doesn't have that limit anymore nvm

This post has been edited by Xgoff on Jul 15 2009, 09:48 AM

Hey Xgoff, does the collision/overlap stuff still work?

I can't get it to work anymore and I'm wondering if the latest R249 builds have come calling for blood.

this still works for me so

Could you post whatever copy of XLua you have? Your application isn't working for me.

Actually, it's only broken in the debug build, but works okay in the release build.

Weird....

Now my faith in this thing is shaken.

This post has been edited by Retriever II on Aug 4 2009, 05:23 PM

don't u quit

In the overlap functions, not the extension.

okay good

i mean if it's any excuse for someone to write a collisions c library for xlua then

Well you already pay the bounding box cost in MMF so might as well take advantage of it if you can.

Also, I added offset support to Object.OverlapsObject.

Also there's a new function os.microclock() per a request on Clickteam. And updated LuaGL stuff.

but what if i'm not using active objects anymore

If you're not using any sprite-based objects in MMF then I guess you're not paying any penalty.

whats a microclock

It's like os.clock() but the timing resolution is sub-microsecond instead of 10-15 milliseconds.

yeah figured it was something like that

also how would I go about using xlua in a lot of frames, some being subapplications? I'm referring to the states, wouldn't they overlap?

Pick a state (or several states) to simply reset at the start of every frame, effectively making them local states. States are global which in the case of subapps is usually something helpful because it not only shares data but also acts as a communication channel.

Of you could just use frame number as state ID and then everything is separate, just don't forget to destroy the state when you end the frame.

oh yeah, never thought of that. Cheers.

maybe i should start using xlua's states instead of hacking my own state **** in

would it be possible to give us a list of all registered functions by name? Not just those registered in mmf, but those registered in lua code.

edit: also your documentation is lying. For setting alterable values, the id range is not 0-25, but 1-26

This post has been edited by Mecha the Slag on Aug 7 2009, 09:32 AM

From one of my projects...

Which applies to Click events, but it looks like I actually corrected this problem for the Lua calls so you would be correct.

Also, if you want a list of functions, loop through _G. It's pretty much the only way.

This post has been edited by Retriever II on Aug 7 2009, 10:01 AM

_G?