Showing posts with label X3D. Show all posts
Showing posts with label X3D. Show all posts

Monday, 26 November 2007

Flux player no longer open source?

Back when I last experimented with Flux Player and Flux Studio, I seem to recall their website still contained references to the player being open source. The source code in CVS at the sourceforge project was however three to four years out of date but there was an archived snapshot of a more recent release (fluxsrc-2006-07-09.zip) which is still available here and other places.

Now unless I am mistaken, all such references to it being open source are gone from the main Media Machines web pages. There are references in various other places to a later source code release from this year but all the files have been deleted from the sourceforge project.

It is still possible to find the deleted files if you google for the file names and substitute them into the standard sourceforge download paths:

This isn't the first time I have seen the wind down of the open source release of a commercial product on sourceforge. It is nice to know that with a minimal amount of effort you can track down the released files.

Given the four year old age of the files checked into CVS I wonder whether it was released based on an initial open source faith which waned in the face of reality or from buying into the false promise of there being volunteers who would pop up and help out.

Sunday, 11 March 2007

Ajax3D experiment: Flux Studio - Getting acquainted

I don't have much experience with using 3D modeling tools, so when I see something like the following when I start a tool like Flux Studio, I am at a loss for any idea what to do with it.


So in order to work out how to accomplish what I have seen others create using this, I started by looking at their creations. One example which stands out in the gallery on Media Machines' web site is New by MrGB.


Looking at it didn't learn me nothing, as they say. Well, 'they' probably don't say it. In any case I decided to download the X3D file and see what I could learn from that. After all, X3D is XML. Loading it into a text editor quickly showed that it was either compressed or saved as some form of binary encoding. So I decided to try and import it into Flux Studio with the following result.


With it imported I could now export readable XML within which I could see local references to textures. So I went back, tracked down the directory the X3D file came from and downloaded all the images located there. This gave me a textured display in both Flux Player and Flux Studio.



Looking at the preceding Flux Studio and XML screenshots, you can see that the same node is highlighted in each. In the XML it is named 'dad_MoveF' and in Flux Studio it is called 'Group13'. I am not sure what is up with this, but it makes it quite a bit harder to ascertain what is going on when looking through the node hierarchy in Flux Studio than it is when doing the same by browsing the XML.

The most interesting thing which I came to realise through poking around at New is that all its game behaviours are completely implemented in terms of nodes. While it is possible to embed ECMAScript in X3D, as it was also in VRML, MrGB (also called GammonBrat in some other places) did not use it in the creation of this game prototype. And New includes a variety of interesting behaviours like picking up objects, jumping, using picked up objects and killing an opponent. And of course it looks great :-)

Saturday, 10 March 2007

Ajax3D experiment: Learning X3D

One of the problems with X3D is how little useful information there is on how to use it. There is the occasional tutorial, blog entry or forum post which is relevant to what you want to know, but beyond this it seems to come down to blind experimentation. With plugins which also support Firefox but tend to be very crash prone in it. Or largely undocumented editing studios.

Now X3D is a standard and it does have specifications which you can browse and download, but in my experience they tend to have their own accessibility issues. Designed using frames and not available in a form conducive to either printing or looking up items of interest, what you really need is for them to be available in other more accessible forms. Like PDF. Unfortunately they are not.. well, actually they are available to some definition of the word. You can pay an extortionately high price to get a PDF of at least the main specification from ISO:


230 CHF? That's around 270 $NZ in real money. Or 11000 ISK in not so real money. It'd almost be worth my time for that price to write a Python script to reformat the frame based HTML.

On the bright side however, www.web3d.org does provide zipped versions of the HTML for download. And I may refer to a few problems with Media Machines' plugin and editing studio in my initial paragraph, but they are both very capable and free and still my X3D tools of choice.

Friday, 9 March 2007

Ajax3D experiment

Years ago I used to do MUD development as a hobby. The direction we were heading was to define the text based game world in 3D in order to have a continuous world rather than room based as was the standard. The long term goal was to have a simple 3D editor to streamline world building. Luckily one of the other programmers, Brian Behlendorf, was a doer and he put his head down and came up with a prototype. A VRML viewer for the game world. It took advantage of the fact that our MUD had an integrated web server, which could be used to fetch the static world data, and used Javascript to make a VRML plugin (Cosmo Player) fetch that data from it.

Nowadays I have a hobby project I need to visualise. There are easy ways to do this like PyOpenGL or PyGame, but taking the direction behind Brian's VRML viewer and extending it for the latest trends like AJAX (which I assumed could be used to establish a bidirectional channel) has a lot more advantages. It is in my best interest to educate myself about the latest web development techniques like AJAX and the end goal of having an X3D based browser client is an interesting project in and of itself.

The first step was to learn what AJAX was and to get it working with a web server. I encountered Pyjamas which looked promising, but the problem was that it had been a long time since I last did Javascript programming and given that it replaces that with Python, it looked like it would get in the way of the learning process. Next were the various Javascript frameworks and as interesting as they looked, it also looked like I needed to learn Javascript before I could benefit from what they offered. In fact it looked like the approach I needed to take in order to achieve what I wanted and to ensure I understood how it all worked from the ground up was to build it from the ground up.

Interestingly the people behind my X3D plugin of choice (Flux Player) have started Ajax3D.org in order to forward the use of AJAX with X3D. Although the examples it provides are just simple client based AJAX and none go to the extent of establishing bidirectional communication.

Anyway AJAX led to JSON and I ended up using BaseHTTPServer with simplejson on the server side and JSON in Javascript on the client side with Flux Player embedded. And this is the point I am at now, learning X3D and how to use it, especially controlled by browser based Javascript. One setback however, is the fact that Flux Player seems crash prone. When you combine that with Firefox's saving of tabs, what you get is a browser which
continually crashes every time it restarts unless you are willing to throw away whatever else is in your other tabs. In theory Flux Player is open source but it looks like releases of the latest source code have trailed off years ago, so debugging this myself is out of the question. Oh well, will see how it goes.