I think it might be best to have a game engine as part of a distro and not a part of the OS. There are so many game engines out there, that to say this is blessed by OBOS might be a mistake. Each game engine has their strength and weaknesses. Also game engines are not very good if you are working on a vis-sim application. Many of the games that would be great if they could be ported to the OBOS have their own game engine in place or something other than this one. It would be better to spend time finishing up the OGL capabilities of the OS and have hardware acceleration. $0.02 John -----Original Message----- From: Steve Vallée [mailto:svallee@xxxxxxxxxxxxxx] Sent: Wednesday, February 27, 2002 8:38 PM To: openbeos@xxxxxxxxxxxxx Subject: [openbeos] Re: 3d engine In my dictionnary (ok, ok ... we can go far with that :-) I think a game engine is too specialized for a "basic" OS package. We have to concentrate on more generic services that can be used for. Like DirectX is a generic API for games development, but not an engine itself. But if we plan for a huge packaging (like Linux distros), sure we can bundle anything else, including this engine... I just want for those "extra" to remain extra and not be considered as "native" in the heart of the OS... ----- Original Message ----- From: "Nathan Whitehorn" <nathan.whitehorn@xxxxxxxxxxx> To: <openbeos@xxxxxxxxxxxxx> Sent: Wednesday, February 27, 2002 7:02 PM Subject: [openbeos] Re: 3d engine > > I think it's a bad idea to include any "engine". In my book an OS > > provide APIs. Period. > > And in my book those APIs are tied to a system that *does* something. > What are the media_server, the app_server, or the net_server if not > 'engines' for media, graphics, and networking, repsectively? > -Nathan > > -- > Fortune Cookie Says: > > Tussman's Law: > Nothing is as inevitable as a mistake whose time has come. > >