Maratis forum - Google Code Shutting Down

Re: Google Code Shutting Down

dummy@example.com (jurgel) — Wed, 13 May 2015 00:34:00 +0000

Great, I will fork from your repository and make some pull request later.

Re: Google Code Shutting Down

dummy@example.com (anael) — Tue, 12 May 2015 15:23:40 +0000

I published the current (experimental) code of Maratis 4 on github - linked to Maratis tiny C library - with the base code of the new editor :

https://github.com/anael-seghezzi/Marat … -C-library

Re: Google Code Shutting Down

dummy@example.com (anael) — Sat, 02 May 2015 18:17:30 +0000

The adjustment is quite small, I'm surprised how simple it is.
First thing to check is the window/events system, but when using glfw or sdl there is no problem (sdl is better supported though), then the main loop need to be parsed a bit differently. There might be some modifications to do for file parsing but I didn't test it.

Re: Google Code Shutting Down

dummy@example.com (jurgel) — Sat, 02 May 2015 13:59:51 +0000

That's cool, even though I know nothing about voronoi
So, anything can be compiled with emscripten or there are some adjustment to make it work?

Re: Google Code Shutting Down

dummy@example.com (anael) — Sat, 02 May 2015 12:24:41 +0000

Some update on github : https://github.com/anael-seghezzi/Marat … -C-library
And a first web experiment compiled to asm.js with emscripten : http://maratis3d.org/js/m_voronoi/m_voronoi.html

Re: Google Code Shutting Down

dummy@example.com (anael) — Wed, 15 Apr 2015 08:12:21 +0000

On x64 platform it should be by default, because SSE is a part of x64 standard, you may need to use "-O3" flag though.

But on 32bit it's not, so you need to add a compiler flag, on gcc it's "-msse2" ("-O3" may be needed too like above).

"-ffast-math" flag can also improve it. But it's potentially unsafe.

Re: Google Code Shutting Down

dummy@example.com (jurgel) — Wed, 15 Apr 2015 03:39:37 +0000

Hmm, I don't know if the compiler could do auto compile to SSE instructions. What compiler flags should I use? Or it's on by default?

It's a great then
Nice info. Thanks.

Re: Google Code Shutting Down

dummy@example.com (anael) — Tue, 14 Apr 2015 15:29:23 +0000

Normally the compiler will use SSE instructions when the code is linear and simple to vectorize like the raytracing functions (I tried to use intrinsic on the ray-triangle code but there was no speedup compared to the compiler).

But in maratis mesh tools, it was a good speed-up : (see void blendMatrices)
https://code.google.com/p/maratis/sourc … hTools.cpp

Re: Google Code Shutting Down

dummy@example.com (jurgel) — Tue, 14 Apr 2015 12:12:08 +0000

Great, looks like an optimized code.
I still think to implement SSE function for matrix or vector math function though.
It won't be portable, but it will cut down the number of instruction.

Re: Google Code Shutting Down

dummy@example.com (anael) — Mon, 13 Apr 2015 21:09:12 +0000

I published a first version of the tiny C code we were talking about :
https://github.com/anael-seghezzi/Marat … -C-library

Still need to link it completely with MCore to publish the rest.

Re: Google Code Shutting Down

dummy@example.com (anael) — Fri, 10 Apr 2015 07:57:40 +0000

Yes, it's in the wind like pure old school 2d, a voxel is just a 3d pixel, it means "volumetric pixel",
it often looks like cubes, but in fact it is more like a stack of bitmaps (the stack being the Z dimension),
and because it's packed and aligned, it can be traversed very fast, using ray-casting or ray tracing.

When parsed directly it can render as cubes (like minecraft) or smoothed cubes depending of the filtering,
but it can also be converted to triangles using "marching cubes" and create smooth surfaces.

voxels are also used to accelerate the parsing of a scene for raytracing, like a fixed size octree.

Re: Google Code Shutting Down

dummy@example.com (Tutorial Doctor) — Fri, 10 Apr 2015 03:50:59 +0000

What is sorta crazy is I was just thinking of a style I wanted to do that I called a 3D 8bit style. Found the keyword was "voxel"

Found this software:

https://voxel.codeplex.com

Re: Google Code Shutting Down

dummy@example.com (jurgel) — Thu, 09 Apr 2015 06:05:18 +0000

It's great if we can add voxel renderer in current engine, so user can choose FixedRenderer, StandardRenderer, VoxelRenderer, and maybe DeferredRenderer later.

I don't understand how your code works , I'll look some reference to implement voxel based renderer which is compatible to CPU rendering then.

Re: Google Code Shutting Down

dummy@example.com (anael) — Wed, 08 Apr 2015 16:10:24 +0000

Voxel based rendering could be done with the base code, as other things, not as a full-feature engine though, something for little games or educational purpose. Well that's just an idea.

In fact I did some test some months ago in Maratis standard renderer : https://code.google.com/p/maratis/sourc … nderer.cpp

It's commented, but if you look at MStandardRenderer::updateVisibility
there is some test code to draw the voxels of the scene in software. The idea is to compute a low-res occlusion culling map on the cpu to avoid the overhead of hardware occlusion culling. It's not complete yet, but it renders voxels from a mesh.

Re: Google Code Shutting Down

dummy@example.com (jurgel) — Wed, 08 Apr 2015 15:15:11 +0000

Did you mean voxel based rendering? It's cool if we could create voxel based game engine, but I don't know anything about it yet. If you have a specific plan for voxel based rendering, just let me know.
We can't combine the current code and we have to start from scratch if we want to implement it, because it's different on every aspect though.

After a bit of googling it looks promising for the future, as it can perform real time ray tracing, but I concern about sparse voxel octree creation per frame if we want dynamic scene, and there isn't many resource out there for further implementation, so this is required much research.

This is interesting and can make Maratis unique from others I think.