zsim-devel Mailing List for zSim flight simulator
Status: Beta
Brought to you by:
zoltan_hubert
You can subscribe to this list here.
2008 |
Jan
|
Feb
|
Mar
(3) |
Apr
(2) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|
From: HUBERT Z. <zol...@zz...> - 2008-06-25 16:02:56
|
??? -- ________________________________________________________ HUBERT Zolt zol...@zz... http://www.zzaero.com/ tel : (+33) (0) 145 07 75 43 fax : (+33) (0) 145 07 79 17 mobile : 06 87 54 90 46 ________________________________________________________ |
From: Olivier B. <ol...@ob...> - 2008-04-13 17:45:17
|
Zoltán wrote: > ... > > This is a *beginning* of a fork, it doesn't need to become a > full fork, because, as many here have said, a fork splits > the available ressources. Hello Zoltan, Could you explain what do you like more in openscene ? What is easier to do with it ? |
From: Zoltán <zol...@zz...> - 2008-04-13 16:12:22
|
Hello all, I'm happy and proud to announce that a new version of the flight simulator I've been working on for some weeks now is ready for release: zSim-0.2.0 It's now a fully functioning flight simulator, derived from CRRCsim, a beginning of a fork we've been discussing here for some time now. You can see some screenshots here: https://sourceforge.net/project/screenshots.php?group_id=222139&ssid=81338 https://sourceforge.net/project/screenshots.php?group_id=222139&ssid=81339 https://sourceforge.net/project/screenshots.php?group_id=222139&ssid=81341 and download the source files here: http://sourceforge.net/project/showfiles.php?group_id=222139 http://www.zzaero.com/downloads/zSim-0.2.0.tar.gz Any comments and suggestion are welcome. This has only been built on Linux (openSuSE 10.3) but OpenSceneGraph and SDL are available on other platforms. In order to build you need to edit the Makefile and adjust the OSG_LIB_DIR and OSG_INC_DIR variables. To run the code you also need to adjust the OSG_LIB_DIR variable in the zSim wrapper script. You also need to adjust the input.xml file for your joystick. Usage: ./zSim --aircraft Aircraft/ASK21/ask21.xml \ --scene Scenery/StEynard/StEynard.xml \ --input joystick --testmode 1 ./zSim --aircraft Aircraft/Skorpion/Skorpion.xml \ --scene Scenery/Panorama/Panorama.xml \ --input joystick ./zSim --scene Scenery/JoeDirt/JoeDirt.xml \ --input joystick \ --aircraft Aircraft/Trainer/Trainer.xml Some fundamental things are still missing, like windfield and ground-height, shadows, sound, ... Also, a particular thing works but I'm not satisfied at all with it: it's the zTimer interface, timer.sleep() and timer.update_fdm(). This is a *beginning* of a fork, it doesn't need to become a full fork, because, as many here have said, a fork splits the available ressources. As I have experienced, making releases is in itself a lot of work, that has to be added to the coding time. Aircraft from CRRCsim need to be converted to run under zSim, but it's a minor task (10 minutes / aircraft) Jens Wilhelm Wulf wrote on Saturday 12 April 2008: > Maybe we should go ahead and modularize important parts > step by step. I'd go the easy way and make different > source repositories for each module. We agree on the > design of a certain module, create a source repo for it, > zSim and CRRCSim copy a certain revision (or most current > revision) into their build directories by means of the > makefile. > > Make compatible changes to such modules only or create a > new branch -- but zSim and CRRCSim should again go this > way together. > > Maybe in the end zSim and CRRCSim only differ by some > glue code, as even the GUI and 3D rendering has become > modular and interchangeable. I agree that it would be nice to merge. But because zSim is based on OpenSceneGraph rather than Plib, there are fundamental internal differences. I'm not sure how much these can be overcome. Another possibility would be to merge "old" CRRCsim into zSim, that would in effect become the follower of CRRCsim (look at what happened with XFree86 and Xorg). > To do this, we might need to work/agree on directory > layout, build system, source code repository and things > like that, then start with simple modules which contain > basics needed for everyone: XML interface, vector and > matrices. Afterwards the power system could be easy and > then the FDM. At least this is my point of view. I agree here too. What If you'd take a look at the zSim code and find what you like, dislike, and discuss from there ? I've said before that I think the CRRCsim code is: - very good - a mess so for me to participate an important clean-up is necessary, and I won't have the time to do that clean-up myself. Any comments and suggestion are welcome. bye-bye Zoltán -- ________________________ Zoltan ________________________ |
From: Zoltán <zol...@zz...> - 2008-03-26 13:52:54
|
??? z -- ________________________ Zoltan ________________________ |
From: Zoltán <zol...@zz...> - 2008-03-26 13:32:26
|
??? z -- ________________________ Zoltan ________________________ |
From: Zoltán <zol...@zz...> - 2008-03-26 13:21:36
|
??? z -- ________________________ Zoltan ________________________ |