Can't make much more than a create object actuator when the ship collides with the walls which creates a spark texture... I still have to see if particles work in-game...
Anyways: Here's the 95% completed GX F362:
Attachment 2472
Can't make much more than a create object actuator when the ship collides with the walls which creates a spark texture... I still have to see if particles work in-game...
Anyways: Here's the 95% completed GX F362:
Attachment 2472
just a compliment :)
sorry I didn't help you guys much back then, I'm back now sooo...
yeah...
Been super busy with finals, but school is finally out, so I'm back I guess.
Here's a .dae of my track - the proportions of it aren't there yet, the track textures are mostly random and it's a bit messy. I don't have the skill, time, or patience to really flesh out and finalize it, could someone else here do that? The track's there, you'll just need to make it so it works in game, e.g. smooth it out, make the physics work and the flow happen.
Caldrion II: http://www.mediafire.com/?q74nqshsz3nzd9n
I'm working on another track too. I think you guys will like it.;)
Quick update- I have a prototype logic brick based 'best lap time' setup. At the minute it is collision based so you could cheat by going backwards but I will think about ways around this. Eventually I would like to move this to Python.
That's cool :P:+ With that cheating i think that setting 3 invisible checkpoints on track and make "function that counts laps" true only when those 3 CP will be reached in defined order will fix that problem.
As for me, i'm making big progress with Maya and guess what i found when i was searching for tutorials :P Free software (proffesional i guess: look here (i found better movie but i forgot where :dizzy)) called Unity3D for making games:o Check it out! I'm gonna learn it after Maya :)
I did look into Unity 3d, recently a visual programming 'click together' system has been tested for it but I didnt use it because:
1: The full program (Pro) costs $1500 dollars
2: The free version is restrictive (it lacks features of the Pro version).
Admittedly it has better game features (better lighting, particles etc) but it requires C to really get the most out of it.
So for me at least, Blender is the way (and its free).
Erm... why take Pro version first off, if we can make game with free version? :rolleyes:
btw. Learning C is not a problem.
Look here to compare: http://unity3d.com/unity/licenses
Lots of features missing that Blender has that would be fiddly to emulate. But its personal choice, I'm only offering my opinion.
On other news, I have a working (Python based) race positon system! The same thing I thought I could never figure out
:rock:rock:rock:guitar:bomb:coffee:robot
It works by having each car calculate how far its travelled (using the formula distance = speed x time), this number is then sorted in a list and outputted to a numeric field (Ist, 2nd etc).
Its a basic system (and relies on the player going forwards!) but it works.
Unity does not require C. You can program in any of C#, JavaScript, or Boo, which is a Python derivative. I really recommend Unity, it's a very nice engine. You should come to IRC channel (#unity3d on freenode), there are a few people there who are actually making Wipeout-like games.
Its tempting augur, but there are several features (like render to texture, post processing) that I do need. But thanks for educating me a bit more on Unity: knowledge is power! I do sometimes look at some of the other features of Unity and feel a bit jealous though (Blenders game engine does lack features).
I think when I become a bit better at programming / scripting I may start looking around, I did see a Unity Wipeout hovership demo that was nice. At the minute I do get confused very easily code wise and the Blender logic system is a robust back up that I use a lot. I realise that Unity has this too, but its not as advanced (yet!).
On a side note, this tread is quite interesting as now we will have Blender, Unity and Dark Basic being used....