Glew shouldn't be an issue with Pioneer port. Bigger problem seems to be vertex buffer object usage. Working around it may slow down the performance.

Oolite is written in objective-C. Somebody needs to port a compiler first, or port the codebase to a supported language. Both options sound a bit tedious.

@Hans

Good work.

@Hans

Not yet :(

@kas1e

I guess so. I didn't do very deep testing though. It also makes now sense why 333 worked (111 vertices, can be divided by 3) and 300 not (100 vertices, can't be divided by three)

@Hans

Yes, it's my fault. Count parameter set wrong. Sorry. Bug is here:

IWarp3D->W3D_DrawArray( context, W3D_PRIMITIVE_TRIANGLES, 0, VERTICES/3 );

@kas1e

Thanks bro, but it's possible that my code has a bug. IIRC I don't divide by three the triangle count. Have to check. And sorry about the hassle :)

EDIT: or maybe the other way around, I did an unnecessary division.

@kas1e

Try to find the simplest possible test case for it. So we know corruption happens with some MiniGL programs. Does it also happen with plain W3D programs? Even with non-3D programs? Minimize the amount of running software, maybe try with/without compositing and so on.

@kas1e

I think I had some screen corruption earlier with MiniGL demos so if it's the same issue, it might be a MiniGL or even W3D issue. Can you try MiniGL demos and try resizing and moving the windows?

@kas1e

That corruption might be related to the gfx card (driver) used.

@sofistisoftware

You have 640*480*16 right?

@xeron

Works here with uA1. Custom SVN build of MiniGL. Not updated for a some time..

@sofistisoftware

What kind of screenmode Giddy wants? What screenmodes you have defined for your system?

@Atheist

Lua binary seems to be in the "src" dir.

Both Lua and Python can be used to write simple games, say, text adventures. Advanced features, such as graphics output or mouse input, need glue code to the operating system services. (There isn't currently, but there might be some day.)

AFAIK, Hollywood uses Lua as the basis and if you already have Hollywood, try it.

@Atheist


Actually, if we start nitpicking, you must add steps to your AMOS version because you must start the interpreter, write/load the BASIC program and compile/start it to see the dot.

The inventor of the C language was probably thinking how to write an efficient, platform agnostic language suitable for writing operating systems like Unix.

C is very flexible with a small amount of commands.

http://en.wikipedia.org/wiki/C_(programming_language)#Philosophy

@Atheist

Just fire up a Lua or Python interpreter and start experimenting. Your scripts will run cross-platform too.

EDIT: now this is pretty fancy. You can try Lua in the web browser: http://www.lua.org/cgi-bin/demo

@Atheist

Anyway, what kind of a game you are planning?

@Atheist

10. It doesn't need the SDK unless you want to embed/link Lua with C. Start the interpreter.

ISO: burn it onto a disc.

@nexus

It could be that sound is a victim of the performance issue.

@mufa

Compiled already :) I will upload this at some point but I would like to find the bug that makes floors flicker in OpenGL mode first. Meanwhile, you can play the older version which works nicely in SW mode.