LÖVE

I~=Spam wrote:(BTW why doesn't LOVE do this automatically? It shouldn't be too hard to do that. )

It might be doing that, but each time you draw you're calling a function, crossing a Lua/C barrier, something like that. Even if LÖVE culls automatically (it might be doing that already) you will still have to cross that barrier, which is one of the main bottlenecks as far as I know.

Nixola wrote:It might be doing that, but each time you draw you're calling a function, crossing a Lua/C barrier, something like that. Even if LÖVE culls automatically (it might be doing that already) you will still have to cross that barrier, which is one of the main bottlenecks as far as I know.

It depends on what you are doing. But crossing that boundary (at least in lua anyway) does not cost much. Plain lua was designed in such a way that crossing this boundary costs incredibly little. This was because lua was designed to be embedded in a c program from the ground up.

But because we are using luajit this gets even faster. But you are right. Calling c functions does have some overhead. But this overhead is going to be about the same (maybe less) as calling a lua function because of the way lua was designed.

Damn I'm loving all the sounds. I feel embarrassed about my abilities.

I~=Spam wrote: But because we are using luajit this gets even faster. But you are right. Calling c functions does have some overhead. But this overhead is going to be about the same (maybe less) as calling a lua function because of the way lua was designed.

At least in puc lua it's significantly worse. In luajit there's the added problem of c calls not being eligible for jit compilation.

bartbes wrote:

I~=Spam wrote: But because we are using luajit this gets even faster. But you are right. Calling c functions does have some overhead. But this overhead is going to be about the same (maybe less) as calling a lua function because of the way lua was designed.

At least in puc lua it's significantly worse. In luajit there's the added problem of c calls not being eligible for jit compilation.

That is true. But the overhead isn't going to be much compared to a lot of other things. I think the FFI library and terria attempt to solve this but they still have their own disadvantages. (ie. no direct c++ support in FFI)

Trying to make a right HUD

You say "trying"... It looks like you aren't trying anymore. You clearly succeeded. It looks great!

I~=Spam wrote:You say "trying"... It looks like you aren't trying anymore. You clearly succeeded. It looks great!

Because I deleted it 3x and started from scratch and the weapon indication (in the middle) still isn't what I wanted. It's because it isn't finished yet and a few things is still missing.

This looks increadible, now I feel like coding a space game like No Man's Sky or Elite: Dangerous.

Very very good work on that HUD, it looks amazing!