Search options (Page 5 of 18)

... I'm sorry... clearly my mind wasn't working well this morning.

Thanks

Having had a couple of issues with rendering some videos with Blender to look right, I have had a thought for another potential plugin that shouldn't be _too_ hard to do.

MVideoDirector!

I think, the most basic thing that can be done for this is that we can set up a scene in Maratis with camera pans etc, test it by running the game. We can add a behaviour to the camera which does nothing much, and just has a single boolean for recording... The (custom) MGame instance can then check for this behaviour on the current camera, check the variable, and then either do normal drawing, (and?/)or render to video.

I'm not sure whether there would be any issues with the draw taking too long. I know Maratis logic is locked to 60fps, but we would really need rendering to a stable framerate (well, to be syncronised with logic, so even if a frame takes 1s, it still thinks of it as 1/60)

Anyway, this was just a thought I had, I'm definitely not going to be picking it up now. I just thought I'd mention to see what people thing

you still need to register MScript::function to respond to the calls from lua (otherwise the symbols are all nil). This is only ever done in MScript::init()

Either MScript::init() needs to be called the first time we run the script (rather than when MScript is initialised), or we manually link MScript::function to the function name in MScript::addFunction. As long as we always add to the map, either way should work, if MScript gets restarted, MScript::init() will then re-link any previously added functions. It's just really a case of whether there was a particular reason MScript::init() was being called on construction, or if it's ok to leave it until we run the script.

It finally occurred to me what's happening.

MScript calls init() on construction, to add all the functions to the lua state. It doesn't call init again unless runScript is called when the script is already running. Therefore, adding functions manually, like I suggested, won't work because it's post-init but pre-run. m_isRunning will be false. The choice then, I think, is either to always call init() on runScript (and not on construction) or to blindly add the function to the lua_State, regardless of whether the script has been initialised, running or whatever. Personally I think the former is best, but I don't know if there was a reason this wasn't done before

Nope, that didn't work. It seems to be that at all points where I can realistically put addFunction, it's before the script is initialised

The first line is from within the register function that I've been trying to call from various places, the second is from within the script, outside any functions, the last is the first update of the script.

I have no idea why this might be happening, as the MScript setup seems to be that it should add the functions on init(). This is particularly difficult to debug, as I have to build both Maratis, and the game together... I'll see what I can find out

That's cool. I had a lot of fun when I was writing the driving mechanics for a game we did at work. It's nice having things like this with pure numbers you can put in (torque, grip, stearing etc) and can get something actually different out of it.

Never did 3D vehicle collision though, so no flips for me.

Looks amazingly fun to play with Keep up the great work

cool! How are you doing the vehicle handling? One contact point per wheel, one per car? What kind of things have you got to tweak and play around with?

LoD.
Well, don't necessarily need LoD in engine, can easily be implemented in a behaviour (at least, without checking too much, I believe it should be able to be...) but for this, it would need, as a minimum, a ModelRef type for MVariable we can expose in the editor.
I assume it would be possible to switch the model at run time from a behaviour?

Right. I've finally got around to testing the function calling in the new build (I think maybe we should move this conversation somewhere else...?) I'm now getting an error, trying to call number value or something. Which makes me think that maybe we're pushing onto the stack in the wrong order.

I'm looking at this incredibly long winded webpage (section "Arguments and Return Value")

whereas we are having to push first, then getglobal... I'm wondering if there's any nice way around this...