Re: [Flightgear-devel] DOS line endings in base package
Ampere K. Hardraade wrote: I know. I am proposing that it may be a good idea to cut it down further so that the archive is around 40MB. I've just did some googling today, and I found that I am not the only one who see the size of the archive as a problem. I've been thinking about it and am more and more in favor of splitting up the download in the base package (including the C172 and some twin engine commuter) and an add-on package. The 3d models should then be saved in AC3d format (*.ac) because that is the file format that is used by FlightGear. (FYI Blender can import and export into *.ac file format) I am seeing a serious problem here: people thinks that FlightGear only supports AC3D! We really need to get those people to know that FlightGear supports variety of 3d formats. We especially need to stress that one can uses GMAX for modelling, so that people who have experience in modelling for MSFS would feel comfortable switching over, instead of asking what the heck is ac3d. I would request holding off stressing out the possible file formats we support right now. There has been some discussion behind the scenes that may affect the number and type of file formats we support. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] DOS line endings in base package
Speaking of the Base Package, I see that the Aircraft directory alone used up 123.9MB. Perhaps it will be a good idea to only include the C172, and allow the user to download the other aircrafts seperately? This may encourage new users to try out FlightGear without having to deal with a 78MB download. Ampere On October 13, 2004 02:53, Martin Spott wrote: Mathias Froehlich has been so kind to create a patch against the base package that is aimed to fix some bugs that were triggered by the recent performance-improving patches to PLIB and/or SimGear. His patch is available here: ftp://ftp.uni-duisburg.de/FlightGear/Devel/shading-update.diff.gz While investitaging this patch I realized that the file Aircraft/737/Models/B737-300.ac in the base package CVS still has DOS line endings. Someone might want to fix that, Martin. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] DOS line endings in base package
Ampere K. Hardraade wrote: Speaking of the Base Package, I see that the Aircraft directory alone used up 123.9MB. Perhaps it will be a good idea to only include the C172, and allow the user to download the other aircrafts seperately? This may encourage new users to try out FlightGear without having to deal with a 78MB download. Most of the aircraft are not included in the official base package anymore. That's why it fits in 78Mb. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] DOS line endings in base package
I know. I am proposing that it may be a good idea to cut it down further so that the archive is around 40MB. I've just did some googling today, and I found that I am not the only one who see the size of the archive as a problem. I think GotM could make a HUGE difference for FlightGear, maybe not for the Flightgear project itself, but for the gamers that (don't) play it. As it is now its really just a mess, ugly gui, almost impossible to find good scenery, half the planes are broken/incomplete, download far to huge and whatever. Yes, with enough knowledge and interest one can tweak everything so that it works, however the casual gamer won't. Simply polishing the GUI, adding just a single complete plane and scenery (thus reducing download and user frustration), all with airport full of 3d objects and such, and some missions and in-game tutorials to the game and you have a huge boost in playability. http://www.happypenguin.org/forums/viewtopic.php?t=1567 On another note: The 3d models should then be saved in AC3d format (*.ac) because that is the file format that is used by FlightGear. (FYI Blender can import and export into *.ac file format) I am seeing a serious problem here: people thinks that FlightGear only supports AC3D! We really need to get those people to know that FlightGear supports variety of 3d formats. We especially need to stress that one can uses GMAX for modelling, so that people who have experience in modelling for MSFS would feel comfortable switching over, instead of asking what the heck is ac3d. Ampere On October 13, 2004 06:52, Erik Hofman wrote: Most of the aircraft are not included in the official base package anymore. That's why it fits in 78Mb. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
