Search options (Page 1 of 8)

I wouldn't say that it makes code exchange too difficult since most of the API remained fairly similar. It is a matter of adding a few "M"s here and there, really nothing more.

I did this refactoring mainly for readability, not with the intention to make code exchange impossible.
It just was not in my head that re-merging code could be desirable so I did not think about that problem.

I might actually port back some code to Maratis, seeing how some people request Android support. I worked a little with Android in the past and got one version of Neo (before the refactoring took place) to compile and run on Android. It wasn't fast, it had graphics glitches on some devices but it worked. Another point where I could help is the Lua API which could be automatically generated for better coverage and structure.

By the way: I saw you did some unicode stuff in your "development branch". What middleware do you use for that?

Have a nice day!

Good to now that everything works again.
I hope you had no data loss

The work on the new Neo release is finished now.
You can find the new version on my website: http://www.neo-engine.de/neo-0-4/

Have fun with it!

Hey SMALERS!

Your problem sounds like a texture issue. Did you unpack the textures from the .blend file before exporting?
You should save them to "<project>/maps" and you need to tell Blender that they are there.

Saving can be done using the "Image > Save as Image" option in the Blender UV/Image editor view.
Hope this helps

EDIT: Post got cut-off again -.-

Hey sunnystormy!

I'm very fine, thank you for asking

I wrote the "Maratis Manager" some time ago to overcome some usability problems with the Maratis editor like opening recently accessed projects and updating the editor from SVN.

Somewhat later I decided to experiment with FLTK a little and started to integrate Maratis with it.
Well, this experiment started growing and evolved into the Neo editor you can download today.

You can find more info here: http://scary-squid.de/wordpress/

Feel free to test it

Spaces are not nice. But Windows likes to use them...

You problems with the key input is about a timing problem between the update thread and the rendering thread. If the rendering takes too long then the update will not be called often enough for your input to get through.

I will do the drag'n'drop thingy exactly like you say. Sounds reasonable to me

Please retest. It should work now.
Btw: I included your new input method

And you can reparent objects by drag'n'drop now
The new binaries are online.

Ok, I will leave the warp feature this way for now

I fixed the input axis. It now rotates like it should (I compared it with default Maratis)
The cmd window should definitely not show. I don't know why it does...

I fixed the space issue when launching the player. I hope it works now

What is completely new is the possibility to add meshes/sounds/fonts by dragging and dropping them into the scene view from your file manager (i.e. explorer on Windows).
Please tell me how well it works for you

All changes are available in the current daily build.

You can download the development version on my website: http://scary-squid.de/wordpress/?page_id=83
Have fun!

Ok, good to know
I will experiment with that a little. Maybe I can fix it

Hm... You could send me an example? I tested all Maratis examples from the website and they worked, both in the editor and in the player.

Grouping is as simple as assigning a group as the parent of an object. It is only for organization and not necessary in any way.

There already was a discussion about the warp feature in GitHub. It currently only sets the position which should be ok for now. The idea is to calculate the position on the surface of a sphere which completely encloses the selection.

You have to reclick the 3D scene since it loses focus when double clicking in the list. To interact with the scene you have then to re-focus the graphics view in the middle. I do that automatically now when setting the position.

Thanks for your wav file! I tested it and found that the editor/player does not crash. Instead it had some glitches while playing. To work around this you could either convert it to ogg or make the sound mono. I'm working on this bug.

EDIT: You try to use a 32bit float encoded file. OpenAL only supports 16bit PCM files at max. Convert your file and everything should work.

Hm. The player window should not have the cmd window.
Did you try "Project=>Update Player"? Maybe you use an old version for your project.

The nameless frame (Which has a name now ) should normally display all output from your game. Even those done using print in Lua. It stops responding since it waits for data from the game which halts when the Window is not selected. I did not find any solution for that problem yet. We would need non-blocking I/O for that which it could easily be done on Linux but not on Windows and others. Maybe I will do the update stuff in a different thread. Let's see how that works out.

More exact profiling will be in the editor itself. I'm working on an in-editor play feature. The problem here is the structural difference between the editor and the player. You can take data about rendering times or script execution precisely but overall speed will not match the player.

With the load/save plugin menu you can save object configurations to a file which you can load in other scenes/levels or even projects to reuse your work. Note that you have to copy all needed assets when using it in another project. I used it to create a smoke particle system for easy drop in into projects: http://scary-squid.de/wordpress/?wpcpro … oke-prefab

Well, you can't see any sound file because the wildcard was not working. I don't know why but I fixed it.
Could you send me the sound file causing the crash? Because all files I tested worked without problems.

About your particle system: You need to set "LifeDivergence" to a high enough value. I found that about 1/3 of the life time is useful for this. Those values are given in ms btw.
You can control the speed with the "SpeedMultiplier" value. Set it to 0.1 or smaller and you will have a much lower velocity.

I hope this helps