Rojo3d. 3D engine for Construct 2

> > > R0J0hound Hey, i think that the shadow issue in first person is due to camera frustrum making objects behind the camera disappear. Unfortunately it is impossible to set camera near to anything lower than 0.01. Do you think you could this one little tweak? Thx

> >

> > Whats the shadow issue?

>

> Two issue actually: 1. it flickers 2. It shrinks/expands/disappears depending on the viewing angle/ Now I know it is Z axis related. for shadows created at Z close to camera Z it doesn't happen. There's also a possibility that because of two sided mesh it generates two different shadows being casted from two opposing angles.

About the flickering:

I saw that... I didn't test, but I think that if you use rounded rotations it will be 'flikerless', what shadows map configs are you using? I think (3096; Infinty; 0.05) it's pretty good. Also, If you make your game 'higher', I mean, making your player have 300 pixels high instead of 32, for example, it might not even be noticeable.

About the second issue:

What??

But... have you tried moving the light a bit and it's angle, or making the shadows bias higher a little bit?

I'm working on 16x16 3d grid. Can't make it much larger because of floating point error on large layouts ( and I have quite big map ). Can't remember what to bias it is set, something like 0.03 maybe, best I could set. But the borders do flicker pixels. In general I did correct it to max of my possibilities. It would be nice if we could smooth it out.

Re resolution, I had to set it to 8k, otherwise it was pretty bad.

I'm working on 16x16 3d grid. Can't make it much larger because of floating point error on large layouts ( and I have quite big map ). Can't remember what to bias it is set, something like 0.03 maybe, best I could set. But the borders do flicker pixels. In general I did correct it to max of my possibilities. It would be nice if we could smooth it out.

Re resolution, I had to set it to 8k, otherwise it was pretty bad.

Can you post a picture the moment the shadow is 'flickering'?

Someone have the LiteTween behavior? I am planning to rebuild almost everything I did, I already did almost everything and acquired knowledge of most 3D things, I am not saying that I became an expert or sort of, I still very 'newbie' to this, but I hope I could do my project even better.

Someone have the LiteTween behavior? I am planning to rebuild almost everything I did, I already did almost everything and acquired knowledge of most 3D things, I am not saying that I became an expert or sort of, I still very 'newbie' to this, but I hope I could do my project even better.

Good. Try sticking to data driven approach, and stay away from functional or inheriting way of doing events. It will a: make it slower, b: make it difficult to change anything later down the line.

There you go.

drive.google.com/drive/folders/1IXq2kMz5I6jmv9qd4hQUXIxL8M1Galho

R0J0hound When the obj file containing the 2d mesh does not have a value for uv defined, the plugin gives an error saying that it cannot read the value as undefined (reading '0') pointing to code line 1313 column 22 where you get the uv value for be able to load the mesh. The error prevents you from loading the 3d mesh in your plugin.

I think of 2 solutions, if the value is undefined, set it to zero so the property has a valid value, but I would need to change its code or create an action to set the object's UV before reading, but I didn't analyze the code to see if it would work. of the loaded object or would have to redirect to this value set in another action as a plugin property.

Easiest would be to only use obj files with uvs. If I was still working on the plugin I would just add 0,0 for missing uvs and improve the obj loader to give more understandable errors.

Currently the plugin is on the back burner indefinitely. It is in need of a rewrite and the event system makes things more complicated than they need to be. And finally time and interest isn’t really there at the moment.

Seems interesting. But can you destroy the ground? I mean, can you 'mine'?

The '3d default project' is a project that I am trying to do, I thought you had the same idea.

My objetive was to create a single project that could handle basically almost all 3D games. Practically a premade 3D engine using the plugin and C2 events.

R0J0hound I followed your suggestion and created an else for the code line 1313 error when uv is not defined, as you suggested with the value of: uv.push(0, 0), but this did not inhibit the c2 error alert, but the 3d mesh did not load. but I saw on line 421, that you defined a mesh object and assigned the property mesh.uv = [ 0, 0, //tri 1 1, 0, 1, 1, 0, 0, //tri 2 1, 1, 0, 1]

What are 2 triangles, shouldn't the same logic be used when a 3d mesh loaded from an obj file is not defined? any other ideas?

I only vaguely remember what the code was and haven’t been on my computer in weeks. But let’s see.

I think I meant that you’d need to add the uvs to the mesh object when loading the obj file. The uv array would need to be 2/3 the length of the verts array to work. And as I recall it first is in a normal js array then that’s put into a typed array to be useable with webgl.

I still say it’s better/simpler to just open the obj file in a 3d modeler and re-export it with uv’s.

That other two triangle thing is unrelated. The plug-in draws to a texture and those two triangles make up a quad so that texture can be drawn to the screen.