Search options (Page 2 of 8)

Yeah, a "Set to default" is really needed.

About the font size: I think it should be big enough for everyone to read. I will think about if it is neccessary to modify this.

Vegas: What keys do you use instead of WASD? I need the info for the input plugin

Thank you guys for testing!

Akira_san: I messed up the path saving. It should work better in one of the next daily builds.

ant0n: Yes, it is possible. I was already thinking about that but did not come around to think about how to do this in a clean fashion. There are some other (serious) usability problems that need to be addressed first.

Vegas: The controls are currently hardcoded to WASD. The plan is to have easy to change profiles written in Lua to allow a more in depth control. It's on my todo list

Currently you can't save any editor related settings. I wanted to do that in favour of a settings dialog where you can control all aspects of the editor i.e. input profile, theme etc.

The camera preview should be quite easy to do. Just render the current scene with the selected camera in a viewport in one corner of the window.

You can find the exact todo list for the next release here: https://github.com/Sponk/NeoEditor/milestones/0.4

Thank you very much for your time! I appreciate it!

I fixed the scene reloading issue. Was an one liner.

I could not reproduce the crash either. Can't be fixed without reproducing it.

It's online now.

Have fun with it

Fixed it. The behavior now checks if the texture has changed and reloads it if needed.

During runtime you can use

setBehaviorVariable(object, 0, "ParticlesNumber", 0)

to deactivate the particle system. I do not want to make an API call in the engine itself since the particle system code is in a modular behavior which is not in the core engine. It should be treated as any other behavior you load in your native game plugin.

If we had a bool variable the code would look very similar:

setBehaviorVariable(object, 0, "Active", false)

Colors are currently not possible since I use the color attribute array to copy other per particle data to the GPU. I have to think about it some more.

Fade out will be implemented. No problems there. Same for rotation.

Premade particle systems should be made using the integrated prefab feature. I'm currently writing code to improve behavior handling (and plugin debugging). Then you can easily package all textures and prefab files in a zip and distribute them.

I introduced multithreading for particle systems by the way. That way they are basically for free on the CPU side what means that you can simulate more particles with the same framerate. Keep in mind that it still is limited by your graphics hardware.

The next daily version will be uploaded as soon as the prefab plugin supports particle systems.

You need to update your player with the menu option everytime you update Neo. Just click "Project->Update Player" and you should be fine.

I just closed the last "enhancement" issue on GitHub.
That means that now begins the phase of testing before the new 0.3 release.

I wrote some documentation about the new Lua API functions btw.
It is not yet completed but you might still be interested: http://scary-squid.de/wordpress/?wpwtds … -lua-api-2

Have fun!

Hey Vegas!

Thank you for reporting. I could reproduce it on XP as well. It seems that the particle count does not initialize correctly and goes through the roof sometimes leading to an allocation way too big for the heap.

I fixed it and the new version is now online.
I hope this one works

BTW: The editor crashes sometimes at exit in virtualbox. Does it happen on native Windows too?

Well, I _should_ write docs. But you know, I always find something more interesting to do

I will upload a first set of Android publishing binaries as soon as I get all graphics features to work with OpenGLES. The particle system does not render correctly under some circumstances.
But that's quite off-topic here

Sponk

Hey Akira_san!

I don't think you can do that with Maratis right now without creating a C++ game plugin or modifying the engine.
This feature is quite essential so it _should_ be included by default (just like functions to load meshes or add lights etc.).

Sponk