MiniB3D mini-survey

BlitzMax Forums/MiniB3D Module/MiniB3D mini-survey

simonh(Posted 2007) [#1]
If you're currently using MiniB3D, if you can respond to these few questions that would be much appreciated:

1) What is your primary platform for BlitzMax/MiniB3D dev? (Win/Mac/Linux)
2) What are using MiniB3D for? (for fun, a game, an app etc)
3) In the next update, what is the one thing you'd most like to see improved?
4) In the next update, what is the one thing you'd most like to see added?
5) Would you rather MiniB3D remained as it is - a subset of Blitz3D, or would you rather it matched the complete Blitz3D command set, or thirdly, expanded it?

Thanks in advance.


kfprimm(Posted 2007) [#2]
1) Windows
2) A variety of things
3) Collisions
4) More mesh loaders (.3ds/.x), not that I couldn't write them myself, and a Direct3D9 driver.
5) The complete Blitz3D command set and then expanded.


KimoTech(Posted 2007) [#3]
Windows
Planning using it for a world editor
Fix on gimbal lock, and generally some speed improve,ents in animation and collisions.
Some support of CG shaders, and shadow mapping
thirdly, expanding B3D would be great!


Picklesworth(Posted 2007) [#4]
1. Linux right now. Windows occasionally.

2. I am using MiniB3D for a part of the front-end in a crazy editor built around the paradigm of "nodes" (such as Blender's node editor, except expandable!). I intended to use it (and still may use it) for a game, but I am exploring Ogre as well, since it does really nice stuff with materials. (The graphics in that game are very reliant on materials).

3. In the future, I would like to see decoupled code which can be very easily pried apart and (thus) customized. For example, mesh loaders not built in to the main MiniB3D module but in their own modules, as well as collisions, etc. Trouble there is that more functions then have to be called to do tasks. Maybe the 'normal' MiniB3D import could contain helper functions such as LoadAnimMesh that hard-code easiness as necessary without harming backwards compatibility. (With the nice thing being that it is not the only choice).

4. Hm... I think #3 turned more into an addition wish than an improvement wish.

5. I like MiniB3D's mininess, and I think by decoupling chunks of the engine, expansion and reusability would come more naturally while keeping its default behaviour similar to Blitz3D.


The r0nin(Posted 2007) [#5]
1) Windows (might use Linux in the future once my second box is up).

2) Games primarily.

3) Some of the math (Euler to Quat, etc.) could be added/expanded/refined. Otherwise I'm pretty satisfied.

4) Terrain functions (by heightmap, et al.) to allow simple terrain generation (useful for quick prototyping of games...)

5) Expanding would be incredible (so long as it remains modular)!


Dreamora(Posted 2007) [#6]
1) Windows
2) Game and Editor for it
3) Collisions and getting back in some of kleptos speed ups to the core version
4) RenderTargets
5) Match the needed functions and extend in sectors B3D needed hacks to get something done on a usefull performance level


jkrankie(Posted 2007) [#7]
1) Win/Mac equal
2) Games
3) Compatibility with Low end graphics chips such as Intel GMA
4) Don't care
5) Matched

Cheers
Charlie


z4g0(Posted 2007) [#8]
1) Windows, but the crossplatform is a main feature!

2) A simply editor for now: still too slow for a game.

3) speed, speed... and mmm speed! (loading time and framerate) :D (I hope that the klepto2 version of 0.42 will be really faster with octree!) And no graphics differences (or less difference) between *.b3D in Blitz3D and *.B3D in Minib3D

4) classic 3D formats loader ( the same of blitz3D, x, 3dsm md2 etc.. for now ).

5) a complete Blitz3D command set ( cameraProjMode, for example): a free Blitz3D like 3D engine, with the same features ( and same, or better, framerate and general performance ), first of all.
But I think that is not enought: Shadows and shaders seems to be a minimum requirements.

Thanks for the work that you and klepto are doing!

(But the official 3D module? what Mark says?)


impixi(Posted 2007) [#9]
1. Windows and Mac
2. Several games (although they’re all currently on hold)
3. Performance at least equivalent to Blitz3D (especially collisions)
4. Terrains (as per item 3. Utilising VBOs?)
5. Complete B3d command set. And then any performance-related expansions/enhancements.

Thanks Simon.


Morbius(Posted 2007) [#10]
1. Windows and Mac
2. Working on a game to accompnay a book / tutorial
3. Performance, collisions, and rotations
4. Easy shaders, shadows
5. A close match to B3D

Thanks Simon.


semar(Posted 2007) [#11]
1. Windows
2. Games and applications
3. Performance, collisions
4. The ability to use the SpriteCandy library
5. Complete B3D set and more (expandable)

Thank you Simon for your work and for keeping us informed.

Sergio.


Robert Cummings(Posted 2007) [#12]
1) Mac. I am using Blitz3D SDK with a view to using Mini to port to mac.

2) A game which requires 3D, but not heavy or advanced 3D, this is why blitz3d / minib3d is chosen!

3) I would like the feature set to match blitz sdk of course... higher performance of boned meshes seems vital to me.

4) Fast boned meshes.

5) There's no point at all expanding it! The genius of this is its original concept - blitz3d cross platform.

If you ask me I would package this up with simon armstrongs sdk so we can set a minib3d driver or b3dsdk driver for wonderous cross platform fun.


siread(Posted 2007) [#13]
1) Win and Mac.
2) A game.
3) Speed when using animated meshes.
4) 3DS loader.
5) Matched.

Cheers, Simon. Keep up the great work! :)


*(Posted 2007) [#14]
1) Windows, although I hope to support Mac and Linux
2) Game applications :)
3) More of the Blitz3d commands supported
4) All of the Blitz3d commands
5) Matched, still open sourced

I am currently using it for Elite Multiplayer and want to use it for other things at a later date.


mongia2(Posted 2007) [#15]
1)windows mac linux
2) Game applications :)
3) fast speed and fast animate ....performance
4) shaders
5) shadows

thankss


Barnabius(Posted 2007) [#16]
1) Windows but Mac is planned
2) For fun at the moment. Educational game planned for later
3) Collisions, speed in general (at least on Klepto's level)
4) DX10 compatibility. Not because I need it but because by the time it is implemented it will be needed anyway
5) Complete Blitz3D set of commands at least, preferable expanded at later date

Barney


Dirk Krause(Posted 2007) [#17]
1) Win/Mac
2) Fun, maybe more later.
3) collisions
4) terrain
5) all of Blitz3D


Sveinung(Posted 2007) [#18]
1)windows
2)Mostly fun
3)Speed
4)Shaders
5)Complete B3D

Sveinung


CASO(Posted 2007) [#19]
1)Windows
2)Fun (for now)
3)Speed
4)Terrain functions, 3DS-X-MD2-etc. loading, and use of Max2d functions with MiniB3D
5)Complete Blitz3D command set, maybe more


The Caffeine Kid(Posted 2007) [#20]
1) Windows, and a smidgeon of the other two.

2) Fun & Games :)

3) Collision Detection please.

4) Loaders for more file types?

5) A complete command set would be wonderful, and additions even more so.


MikeHart(Posted 2007) [#21]
1. Windows
2. Fun & games
3. Performance like Blitz3D
4. ViewPort setting
5. Complete B3d command set.


JetFireDX(Posted 2007) [#22]
1. Mac (with plans for Windows)
2. Game and app.
3. More variety of simple render options (ex. Flat Shaded, Wireframe w/out textures, etc...) Useful when you are looking at editing meshes.
4. Shadows with options for changing how nice they are.
5) Complete and then additions. Who would answer anything else? heh.


anawiki(Posted 2007) [#23]
1) Win/Mac - we develop on both platforms at the same time.
2) Game - Pony World
3) Better integration with Max2D
4) Better performance
5) Don't know.

We're pretty happy about MiniB3D, but we always can make use of something new :)

best
Roman


Stu_ovine(Posted 2007) [#24]
1) Windows
2) games
3) better performance and speed
4) shaders...
5) expanded


LAB[au](Posted 2007) [#25]
1) Linux,Windows, Mac , crossplatform feature is the main reason why I use it
2) Applications
3) better performance and speed
4) Loaders for 3DS and Collada (and/or other formats)
5) expanded


Sledge(Posted 2007) [#26]
1) Win only at the moment, but I use it because if and when I do cross-platform development it will be there.
2) Fun.
3) Mesh loading... via Incbin.
4) Compatibility with Intel integrated GFX 'out of the box'.
5) Matched then expanded. EMBM Bump Mapping is a good fit for indie development I always think.


(tu) sinu(Posted 2007) [#27]
1) Windows
2) games
3) the commands implemented working exactly like blitz3d
so i can run some stuff from my blitz3d stuff exactly how i had it.
4) shadows
5) Blitz3D command set, the community can really be part of the expantion.


JA2(Posted 2007) [#28]
1) Windows, but Mac planned for the future
2) Just for fun at the moment. Waiting for 4)
3) Speed
4) Shaders, shadows, etc
5) Expanded


Mikele(Posted 2007) [#29]
1) WinXP
2) Games, fun, etc
3) Better performance
4) Shaders...
5) Blitz3D command set + expanded


degac(Posted 2007) [#30]
1) In the order: Mac/Linux/Win
2) testing / fun / game
3) speed / easy integration with Max2d
4) In the order: Shadows, shaders, physic
5) Anything you can do to get better results is welcome

In any case: your work is awesome.


Sanctus(Posted 2007) [#31]
1)Windows
2)Game/App
3)Working with MaxGUI
4)More file formats suported and more shaders
5)Expanded


Chroma(Posted 2007) [#32]
1. Windows XP
2. I'm using MiniB3D in place of Max3D...
3. speed optimization
4. normal map / dot 3
5. matching the Blitz3D command set is fine as long as there's no speed hit


lodger(Posted 2007) [#33]
1) Mac and Linux
2) right now it's for fun and learning. But I've got some plans for a game ...
3) better mouse handling on Linux
4) shaders, shadows
5) matching B3D sounds good, expanding it even better - as long as cross-platform availability doesn't suffer due to that.


deps(Posted 2007) [#34]
1) Used to be OSX 10.3.9, now it's WinXP
2) Games
3) Collision
4) "Simple" shaders. (Bloom, Field of depth, etc.)
5) Complete, then expanded.


Neochrome(Posted 2007) [#35]
1) Windows
2) Games
3) Collision
4) BSP Style Q3 or Unreal Maps
5) DirectX9 Shader, expaded coolness ;)


D4NM4N(Posted 2007) [#36]
1) mostly linux, double checking stuff on windows.
2) Games mabe apps
3) Collisions only moan so far
4) shaders shadows
5) match it would be great

Great work so far Si!

better mouse handling on Linux

I made a kind of very simple fix for this, see here:
http://blitzbasic.com/codearcs/codearcs.php?code=2111


AltanilConard(Posted 2007) [#37]
1) Mac and windows
2) Small games and fun mostly
3) Collisions
4) Don't need anything really.
5) I think it is great as it is, it would allways be good to make it match b3d a bit more though.


ima747(Posted 2007) [#38]
1) Mac and Windows
2) Mostly games
3) Collision speed and or types
4) Quat based core for better rotation and more (turn entity global please work)
5) To match would be best IMO, I think the extended version of klepto's fits the expanded desire perfectly. Some project I use some expanded features, but in the interest of simplicity if I don't need them I stick with the "classic" minib3d

P.S. Really can't thank you enough for this project, it's helped me in many many ways with many many projects and ideas. Seriously, thank you.