MiniB3d for FreeBasic
Nice work.
But I think it would be better, to give it an other name.
- Simon have called its first implementation written in BlitzMax "MiniB3D"
- The someone other have created a different version of it on http://www.minib3d.com called "MiniB3D Extended" or "minib3dext".
- Later Simon have ported its own version to Objective C for the iPhone and called the port "iMiniB3D"
And now you ported iMiniB3D and parts of MiniB3D to C++ and calling it "MiniB3D" again :-/
Ok, on Sourceforge you call it "minib3d v0.25 for FB", but the address is
http://sourceforge.net/projects/minib3d
and the title is "MiniB3d library".
So this is very confusing, when there existing two projects called "MiniB3D".
Can you not call your port "FBMiniB3D", "MiniB3D4FB", "CPPMiniB3D" or something else?
It is already confusing to read this thread, because of that.
I describe it now in two versions.
Here there stand it like
"MiniB3D is a port of iMiniB3D with some extension. But the code of Terrains is ported from MiniB3D."
But what it mean is like
"Your MiniB3D is a port of iMiniB3D with some extension. But the code of Terrains is ported from Simons MiniB3D."
But really nice work.
Greatings
theuserbl
But I think it would be better, to give it an other name.
- Simon have called its first implementation written in BlitzMax "MiniB3D"
- The someone other have created a different version of it on http://www.minib3d.com called "MiniB3D Extended" or "minib3dext".
- Later Simon have ported its own version to Objective C for the iPhone and called the port "iMiniB3D"
And now you ported iMiniB3D and parts of MiniB3D to C++ and calling it "MiniB3D" again :-/
Ok, on Sourceforge you call it "minib3d v0.25 for FB", but the address is
http://sourceforge.net/projects/minib3d
and the title is "MiniB3d library".
So this is very confusing, when there existing two projects called "MiniB3D".
Can you not call your port "FBMiniB3D", "MiniB3D4FB", "CPPMiniB3D" or something else?
It is already confusing to read this thread, because of that.
I describe it now in two versions.
Here there stand it like
"MiniB3D is a port of iMiniB3D with some extension. But the code of Terrains is ported from MiniB3D."
But what it mean is like
"Your MiniB3D is a port of iMiniB3D with some extension. But the code of Terrains is ported from Simons MiniB3D."
But really nice work.
Greatings
theuserbl
>:P
Needs a lot of documentation on it ... can't find much
I won't use names with "4FB" or similar: in fact, even if I developed it with FB in mind, the library can also be used in other languages (GFA Basic, RapidQ.... but also C or C++, if you want)
OpenGL4FB cannot be used: in fact, MiniB3D is not a wrapper for openGL, it uses different commands and has different features: also, openGL for FreeBasic already exists, it's a simple .BI file included in FB download.
Maybe I'll use OpenB3D...
OpenGL4FB cannot be used: in fact, MiniB3D is not a wrapper for openGL, it uses different commands and has different features: also, openGL for FreeBasic already exists, it's a simple .BI file included in FB download.
Maybe I'll use OpenB3D...
Hey
Is there a way to make a MiniB3D-Variable a shared Variable?
Something like this:
I hope, you can help me.[/code]
Is there a way to make a MiniB3D-Variable a shared Variable?
Something like this:
Code: Select all
Dim Shared As TCamera camera
Of course:
All objects are simply pointers, you don't need to specify: so, you can use MoveEntity on a mesh, a light, or a camera with no limits. Since freebasic doesn't support polymorphism, this is the simplest work-around.
Code: Select all
Dim shared as any ptr camera
-
- Posts: 255
- Joined: Jan 05, 2006 0:56
Playing around with terrain, why is one corner "down" after this piece of code:
Picture of what i mean:
Code: Select all
var terrain = CreateTerrain(16)
for x = 0 to 15
for z = 0 to 15
ModifyTerrain(terrain,x,z,0)
next z
next x
PositionEntity terrain,0,-1,0
-
- Posts: 255
- Joined: Jan 05, 2006 0:56