Search options (Page 50 of 60)

the chdir method was something I was doing in the past, and it occurs to create some problems in some specific cases, for example on iOS and with the editor. But to be honest I don't remember clearly what was the problem.

For now lets not break too much things at the same time, it can create some problems with the editor and with the data system,
I need to think about it, if it's not a problem, I'll do the change later, but I don't want to block you, so the best is to convert to relative path for now.

For the font, if you want to test, load a TTF using Maratis editor, you will see that a .font is created, it is the bin file.
The .font can be load from editor also yes.

Hi,

yes it's true, I forget to tell that filenames was converted to global when send to data loader,
the gui is an exception and is editor-relative (don't take it in account).

If there is a package detected you can get the local filename :

MEngine * engine = MEngine::getInstance();
MSystemContext * system = engine->getSystemContext();

char localFilename[256];
getLocalFilename(localFilename, system->getWorkingDirectory(), filename);

If the loader received a project-local filename,
the conversion to global would be needed when loading using fopen, so it doesn't change much to modify the path system.

Hi,
nice
it's a really big work, thank you for your commitment !

About writing, I don't think we need to be able to write inside the pak ?
At least, the current writing (convert xml, save font as bin) can be done before the packing.

For the publishing, I prefer it's in code as the users normally don't need to have python installed.

Thanks !
Anaël.

I only have vc 2005, and Microsoft has the good idea to change the structure of the project files each time they release a new version... There is maybe some conversion problems, I never tried vc 2010...

Davide, who made the scons build system, told me it was possible to use scons to build but to run it using visual and be able to debug. I can try to contact him if you want ?

Mh, I feel it will be too much risk for the non-desktop system and I'm a bit afraid of the testing/debugging when I see all the problems we already have when running Maratis on untested hardware.

I understand it will create more work because of the external libs, but if you want to focus on adding npk and creating a layer for fopen/fread I can take care of the DevIL and libsnd loaders as I'm familiar with the libs.

We don't need to modify tinyXML as we should really convert the xml into binary (levels and meshs).

Then there is MBinFontLoader where to replace fread by the layer,
we also don't need to adapt the Freetype loader (it is only needed in the editor, the font is already converted in binary).

I need to check how the script is loaded.
EDIT > we can use "luaL_dostring" or "luaL_dofile"

Ok, thank you, I was not knowing anything about function patching, interesting. I'm maybe a bit afraid by the cross-platform compatibility, but it's mainly because it's the first time I'm hearing about this. I would have picked the first option (the only one I was knowing) but if the function patching is simpler why not.

Is it possible to check that the same thing exist for unix, as it is a more secured OS ?
It might be forbidden on iOS and Android, even if the ARM support it.

It's good to hear about new things, don't worry, Maratis is starting evolving by itself, and there is a lot of better programmer than me

Take your time, you don't need to do it in just 2 hours

I will send you a mail about creating you an account on google code for svn so you can commit,
if it's ok with you I prefer we don't have multiple public repository.

Is it working when you use a compiled version from the website or is it writing the same error ?
download : http://www.maratis3d.org/?page_id=57

Also, we should make it more clear, but the build is copied with all the needed files and dynamic lib in trunk/dev/prod/
Don't try to run the one in trunk/dev/build/

When I see the npk sample code, I really like how it looks, clear and simple :
http://code.google.com/p/npk/wiki/SampleCode

Hi Philipp,
welcome to the forum and thank you for your message, it is very worm and interesting,
I think it is very valuable to the community to read from a professional, I hope some people will respond and keep the topic alive

I'd love to see more about your project when it's started.

Hi,

the best is to do extensive and repetitive code in c++,
you can make a light flick in lua (using a cos and the time value for example),
but it will be a pain and it will be slow to do AI in lua (except if it is very basic).

To add behaviors in the behavior-tab of Maratis, you have to use c++ and make a dll plugin.
You can find a tutorial with a simple example to download here : http://www.maratis3d.org/?p=500

And you can find an example called "WaterGameDemo" in the Maratis package you can download on the website, it is c++ code for fish AI, it is compiled as a "Game.dll" plugin (Game.dylib on mac).

Basically, a game plugin permit to extend Maratis, you compile a dll that is loaded by Maratis :
   - by coding behaviors (MBehavior class) that will appear in the interface, which you can use like you use the "LookAt" behavior.
   - optionally by customizing the Game class (MGame class), to change the pipeline of the game, do special effect...

When you want a better flexibly for the game design and level design, the best is to create a bank of Behaviors specific to your game, for example a "Player" behavior, a "Alien" behavior, a "Door" behavior... You code how they are interacting, so when it's done, you just have to create your level, say that one mesh is the Player, the other is an Allen etc

In the WaterGameDemo, if you load a fish mesh, you just have to select the "RedFish" behavior or the "BlueFish" behavior, set the speed they are moving, and the fishs are interacting immediately. It's done with a c++ game plugin.

Hope it helped,
Anaël.