I like to think of it this way:-
I could wait until the game is finished (when S3 final is released) and then pay my £36 which is about average for a PC game.
Only with LFS, the dev team let me pay a bit every now and then and get to see pre-release versions of the game, and even take part in what amounts to the most involved testing programme for any game.
I could wait until the game is finished (when S3 final is released) and then pay my £36 which is about average for a PC game.
Only with LFS, the dev team let me pay a bit every now and then and get to see pre-release versions of the game, and even take part in what amounts to the most involved testing programme for any game.
Yeah come on Scawen - give your audience what they want. I'd like to see fully functioning cup holders in all the touring cars please! Oh - and air con.
I suspect you're right about the translation - a lot of Motors TV content is French, and the guy reading the English translation presumably has no knowledge of the subject. This is guy is much better than the one they used to have with the "Beavis&Butthead" voice though, who used to really get on my wick by pronouncing bonnet (i.e. the lid over your engine) as "bo-nay". Presumably he thought "well it's French innit?" (or should that be "innee" ?
) I can only assume the long periods of silnce on this review are because it takes bloomin ages to say anything in French 
I thought the review was pretty accurate on the whole, although they seemed to have grasped the wrong end of the stick about the skins. The main problem for LFS in any short TV review though is that the viewer is just not going to be able to grasp just what sets it aside from popular console or PC arcade type racing games in a 5 minute piece, although he did touch on the fact that you need to drive it like a real car.
One other confusing thing probably lost in translation - apparentley the LFS developers don't need to worry about "R-Factor" because the next LFS is called "LFS-S3". Erm. Righto then. I'm sure you're not worrying about R-Factor, but I doubt the name of the next release will affect anything...
I like Motors TV - it has a sort "Home made" feeling about it
I suspect you're right about the translation - a lot of Motors TV content is French, and the guy reading the English translation presumably has no knowledge of the subject. This is guy is much better than the one they used to have with the "Beavis&Butthead" voice though, who used to really get on my wick by pronouncing bonnet (i.e. the lid over your engine) as "bo-nay". Presumably he thought "well it's French innit?" (or should that be "innee" ?
) I can only assume the long periods of silnce on this review are because it takes bloomin ages to say anything in French I thought the review was pretty accurate on the whole, although they seemed to have grasped the wrong end of the stick about the skins. The main problem for LFS in any short TV review though is that the viewer is just not going to be able to grasp just what sets it aside from popular console or PC arcade type racing games in a 5 minute piece, although he did touch on the fact that you need to drive it like a real car.
One other confusing thing probably lost in translation - apparentley the LFS developers don't need to worry about "R-Factor" because the next LFS is called "LFS-S3". Erm. Righto then. I'm sure you're not worrying about R-Factor, but I doubt the name of the next release will affect anything...
I like Motors TV - it has a sort "Home made" feeling about it
Hi Ajp71..
Thanks for that. I played around with this Today, but got much the same results as you did. Ie that the output 3d converter produces is either junk, or the target modelling software imports the data but you see nothing.. Moray, for example reads the UDO output from 3D converter, and even lists all the objects correctly, and lets you assign materials to them - but you still see nothing at all in any of the views. I did try adding some light and rendering the scene anyway but POVRay choked on Moray's output.
I did manage to get something on the screen in "Model Scene Editor":-
http://mse.sourceforge.net/ By exporting to RAW format from 3D converter, and importing that in MSE.
I got nothing in the single plane views but adding a camera and switching to the camera view got me a wire frame view of the car, but very close up - I saw the back wheels... Unfortunately, MSE, like all the modelling software I tried (and I tried about 6 Today) seems almost deliberatley obtuse. It wouldn't zoom out, or allow me to select an object on screen, and then just started generating access violations.
It's almost as if the designers of all these modellers have not grasped the idea of dragging and intuitive manipulation of things with a mouse. Things like entering rotation values by hand, selecting from lists rather than what's in front of you on the screen etc etc. I wanted to be able to point at an object to select it, and then change the properties of the selection (like say Visio for exmaple). It's almost like the modern desktop age has passed them by. Maybe this is what you pay Autodesk £2,500 for
Lot's more software to test though...
Cheers,
Scoot.
Thanks for that. I played around with this Today, but got much the same results as you did. Ie that the output 3d converter produces is either junk, or the target modelling software imports the data but you see nothing.. Moray, for example reads the UDO output from 3D converter, and even lists all the objects correctly, and lets you assign materials to them - but you still see nothing at all in any of the views. I did try adding some light and rendering the scene anyway but POVRay choked on Moray's output.
I did manage to get something on the screen in "Model Scene Editor":-
http://mse.sourceforge.net/ By exporting to RAW format from 3D converter, and importing that in MSE.
I got nothing in the single plane views but adding a camera and switching to the camera view got me a wire frame view of the car, but very close up - I saw the back wheels... Unfortunately, MSE, like all the modelling software I tried (and I tried about 6 Today) seems almost deliberatley obtuse. It wouldn't zoom out, or allow me to select an object on screen, and then just started generating access violations.
It's almost as if the designers of all these modellers have not grasped the idea of dragging and intuitive manipulation of things with a mouse. Things like entering rotation values by hand, selecting from lists rather than what's in front of you on the screen etc etc. I wanted to be able to point at an object to select it, and then change the properties of the selection (like say Visio for exmaple). It's almost like the modern desktop age has passed them by. Maybe this is what you pay Autodesk £2,500 for
Lot's more software to test though...
Cheers,
Scoot.
Hi Spoop,
In theory yes you can *render* these models using POVRay, but to do this, you'll still need some modelling software to create the scene, with the model in it (and some light, and maybe some background). The modelling software would also need to be able to output POVRay scripts for POVRay to render.
Moray is the thing most POVRay users use. It won't read these CMX files either, but there's good support/docs for it so it may not be too difficult to write a converter.
Cheers,
Scoot.
In theory yes you can *render* these models using POVRay, but to do this, you'll still need some modelling software to create the scene, with the model in it (and some light, and maybe some background). The modelling software would also need to be able to output POVRay scripts for POVRay to render.
Moray is the thing most POVRay users use. It won't read these CMX files either, but there's good support/docs for it so it may not be too difficult to write a converter.
Cheers,
Scoot.
FGED GREDG RDFGDR GSFDG