Search options (Page 12 of 60)

kostik > thank you for reporting, the link is fixed in the tutorial.

It is also a limitation of the rendering, the engine uses the 4 nearest light for each sub-mesh (or each object).
Please read this for more details : http://www.maratis3d.org/?p=277

Sure, you can do this if you still use percents (if the screen need to adapt to the resolution) :

    int marginLeft = viewport[2]*0.1f;
    int marginRight = viewport[2]*0.1f;
    int marginTop = viewport[3]*0.1f;
    int marginBottom = viewport[3]*0.1f;

    render->setViewport(
           viewport[0]+marginLeft,
           viewport[1]+marginBottom,
           viewport[2]-marginRight-marginLeft,
           viewport[3]-marginBottom-marginTop
    );

or if you want to enter pixel coords direcly :

    int X = 10; // pos x
    int Y = 10; // pos y
    int W = 500; // width
    int H = 300; // height

    render->setViewport(
           X,
           viewport[3]-H-Y,
           W,
           H
    );

"release" should be somewhere in the top bar,
usually a project is in "debug" mode by default, if you see "debug" somewhere, clic on it to change to release.

when you compile, the project should create a file named "Game.dll"
if it's not done by visual studio, copy it inside the maratis project folder

tell me if something is not going well,
it should be ok, there is a visual studio project in the example

- install visual studio (version 2005 works, express edition is free, I'm not sure with the more recent versions)
- open the .sln file
- check the paths in the project properties
OR be sure the .sln file access maratis SDK folder this way : "..\..\..\..\SDK"
OR open the vcproj file with a text editor and replace "..\..\..\..\SDK" by your own path
- compile in "release" mode

ok

did you ever tried to compile this example ?
http://www.maratis3d.org/?p=563

because the code you need will be a minor modification of this.

ok, I understand.

mathematically, with the first method, a larger FOV will produce the same result, even with a moving cam,
the only negative point is that a part of the drawing will be rendered for nothing.

about the sound problem with the render to texture, I don't have a solution that can be done in lua,
the only way I can see is to make a custom game class with a plugin. If you can manage to compile it yourself,
I can make you the code, it's not very complicated.

Yes, there is typically a one frame delay, specially with the use of physics.
When not using physics, the delay can be removed by forcing the matrix update from script : updateMatrix(player)

This is because the game update happens as follow :

1 : script "onSceneUpdate"
2 : behaviors update
3 : scene update
4 : physics update
5 : matrices update

If you want a perfect attach with no delay, it's better to use parenting (edit > link selection).

Tutorial Doctor : true, I also recently watched some videos of tomb raider 1 and it's still working very well, gameplay is there, atmosphere is there. Indeed a lot of things can be done with small budgets.

"Smultron" for mac is good and minimal,
I was thinking adding it in the mac maratis bundle

Hi,

the z pre-pass is useful as a general technique to reduce fragment call
and improve performance for complex shading or middle-aged graphic card,
at the same time the pass is building occlusion culling.

You might be able to get better performance for special use by skipping it indeed,
but large scene with complex shading/lighting will usually get improved.

Different 3d cards can react differently (on some, like iPhone/iPad pre z-pass to reduce fragment call is bad because the card already does it internally as a strategy).

Hi, thank you for the tip,

I started adding real unicode support in the experimental branch,
so I'll also try to check that to be sure the symbols are loaded by lib freetype.