3D Engine?

[Brandon]

Why so many objects, well every wall is 5 objects, one is invisible and static and is used for placing walls on the map, it's also used for collisions and the other four are what the player sees, each of them is a different surface of the wall, one might be the north side of the wall and another east side etc.

There is definitely a more efficient way to make walls than that. Five objects for 1 wall is ridiculous, and will severely hinder your level size and performance. I know that all of your walls are boxes, and that's what is causing it, but not all of the walls can be seen for every wall, for example the exterior walls don't need all four sides, only 1. That alone could save you a couple hundred objects.

Another idea is that you only have walls that are visible to the player in the frame, and that will help you a lot. But it is a little tricky and would require some dynamic coding.

This is more entertaining than most TV nowadays.

How is this relevant?

It's not really relevant, but its funny, and kind of what I was thinking as well. And dragonguy, didn't you say you were going to give up on 3D last week? Because if so...

[neat_Kliker2]

change number of objects at runtime.
And listen to Brandon; if this doesn't work stop posting for help on it and forget 3D because you really becoming a thorn in our backsides and annoying us with stupid questions

[dragonguy]

Well that is a very good idea brandon, but I woudn't know exactly how to do it.

When I was designing it I decided to do the following.

The 4 display walls are connected to the 1 map wall via an advanced technique called object linking, which is only 3 events per each link, what it doe's is it keeps the exact same amount of one object as the other and this makes it easier to change alterable A and B of the Display Walls to the X & Y Positions of the Map Wall.

I did give up, that's beacuse the walls of this game (which I planned out weeks ago) were thought to be impossible until only recently, now that I know the walls can be done almost properly, the game can be as much made, this example shows how the walls will be done in the game.
http://www.clickteam.com/epicenter/ubbthreads.php?ubb=showflat&Number=95514&#Post9551 4

Remember if your game can be done: it ain't worth giving up on.

[Cody]

Interesting!

dragonguy, if you really really want to continue to create 3D game with MMF2, you need to know few things like the back of your hand:

- math and math: specially the topics on - matrix, vectors, quaternion, dot product, cross product, and any geometric calculation such as for AABB, rays, lines, barycentric, etc..

- the popular render algorithms for optimized and collision detection: Binary Space Partioning (BSP) with PVS, and kDtree or other tree. Because without these, you won't be able to render huge level and have collision detection working properly.

- models: you need to use 3D models that built from 3D modelling program for your objects because sprites won't cut it. In reality, 3D game uses sprites for interface and special effects. For objects, they use models with textures(2D sprite applies to polygons) or build their own models using their own polygon generation class. For special effects, shader will be used in association with sprites to create cool effects.

- shader: 3D game without shader will not look good. You need to find a way to build shader engine in MMF2. And choosing which vertex shader 1.0, 2.0 or 3.0 is up to you.

- Importantly, you will need to know how to create your own extension for MMF2 because chances are you will not have everything built for you in MMF2 to do your 3D game. And I don't think anyone on the forum will be willing to dig out their time to build 3D engine for you from scratch.

Honestly, by the time, you've figured out something to do in MMF2 for a 3D feature for your 3D game, you will probably finish at least 3 or more features using a 3D engine.

And for your quote
"Remember if your game can be done: it ain't worth giving up on."

It's about making the right choice for your project. It seems like you missed this part in your planning phase. The planning phase is the most important in game development. This is why companies spend alot of time on to plan their game. In the planning, they make sure they got the game planned out for such what can be done and what can't be done etc..There are more lot of points that needed to address in planning. You may want to look at your plan document and put in the part "Technology Analysis" where you examine the proper technology that is going to be used for your game - answer yourself some questions like "Will I be able to implement this feature in this engine?", "What's my completion rate if I use this technology?", "Does all of my teammates know the knowledge to extend the engine?" and etc..

Good luck with your project!

[SEELE]

^
|let me sum up this post;
| GIVE UP!
|

[dragonguy]

What is going on here, I tried using the 3D Actives object but that just doesn't work no matter what I do with it, changing it's X camera angle and it's Z camera angle do the exact same thing and changing it's Y camera angle doe's absolutely nothing, only two objects can be seen during runtime, that makes no sense, more than two objects should show up at a time.

I think all of my problems have nothing to do with what I'm doing but is in MMF2 itself, you know what why don't I just get a better game making tool and stop wasting my money on useless clickteam products. Unless somebody can come up with a good reason why I shoudn't.

[Anders]

Use the right tool for the job.. I think that was mentioned at least 10 times during this thread.

Honestly, you don't know much about 3D math and then you jump to conclusions when things don't work because you don't understand it. Of course.. Thats the easy solution. If you are 120% certain you've found a bug, you file a bug report describing exactly what happens and what should have happened instead.

If the example files using 3D Actives works fine, then you are obviously doing something wrong. From your description of your problem we have no idea what you are doing and where the mistake is.

[dragonguy]

I know the examples work fine but when I use it in my game it doe's some totally different than what it doe's in the examples, which is just huh?

In the examples it works perfectly, X turns the camera up/down, Y turns the camera left/right, Z turns the camera clockwise/anti-clockwise.

But when I use it my game for some strange reason both X and Z make it turn up/down and Y doe's nothing.

Is it possible my .mfa may have been damaged some how?

[Benicle]

The extension will work the same no matter what, it has to be code error - and seriously stop pursuing this whole 3D in MMF thing! It's a 2D development environment.

[dragonguy]

MMF2 is nothing like TGF2, TGF2 only had one bug and that is it crashes one hour after you ran it, MMF2 didn't have that but it appears to have loads of bugs (bad objects, .mfa damage, misbehaviour, somtimes even crashing when creating a new condition in the event editor and more), I'm afraid of using MMF2 now, as it might damage my games but not all of my games are TGF2 compatible, so I might not be able to finish those.