Re: [Flightgear-devel] About 3D Clouds
On June 28, 2005 12:06 am, Ampere K. Hardraade wrote: > On June 27, 2005 04:26 am, Erik Hofman wrote: > > Harald at one point added a check to make sure the RenderTexture context > > was actually available. It almost looks like this was a bit too drastic. > > > > Erik > > Interesting. I happen to keep getting an error regarding RenderTextuer > context -- in both 16bits and 24bits color. > > I have done "apt-get install --reinstall" for XFree and Mesa already, but > the error still presists. I have begun doing searches on Google for this > error, but I haven't find anything helpful so far. > > Do you guys know what cause this error? > > > > Thanks in advance, > Ampere hmm... I have tried removing, purging and reinstalling everything related to Mesa, but the error message about RenderTexture is still there. Mathias is the only other person who has the same problem as I have, and he/she is also using the r200 driver: http://baron.flightgear.org/pipermail/flightgear-devel/2005-June/037272.html I guess something in RenderTexture.cpp is incompatible with Radeon driver? Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS for OpenAL
I give up... could someone save me the suffering and mail me a tarball of openal they have to this address? I've decided cvs hates me lol... kind of reminds me of Martin's signature on all his posts!! ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] readXML problems
Erik: Are you calling readXML while another call to readXML is in progress? Norman: Can't be done unless this other call is in a different thread :-) Jon: > I'm doing it in standalone JSBSim (calling readXML from within another > readXML()). I > thought you simply had to provide new arguments. Why would it work perfectly > in > standalone JSBSim, but not within FlightGear? Doh!!! Of course Norman is right - and JSBSim is not calling ReadXML() while another call to readXML() is in progress. I still don't know what could be causing our abort, though. In standalone JSBSim we use our own compiled easyXML and eXpat code - though I would assume it's the same code SimGear uses. When building with FlightGear we resolve the references at link time with the simgear libs like everyone else. Seemed to work fine. Until it died when called from the propulsion loading code. Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Attaching Views to Other Objects
> From: "Alberico, James F" > > Hi, > > I'm trying to track down how I can attach a view to another object in > the sim, particularly for a multiplayer aircraft other than the ownship. > I would like to switch to the viewpoint of each of the "other guys" in > the virtual world. > > As documented at http://flightgear.org/Docs/fgfs-viewer-howto.html : > > > Syntax for the eye position is: > true or false > modelnumber > Syntax for the target or at position used in views of type "lookat" is: > true or false > modelnumber > - > > But I can't find out where the "modelnumber" comes from, or what it > really means. All the examples use zero, so I've assumed that was the > ownship. > > I've looked through the code and docs, and searched many of the > mailing-list archives, but haven't found any examples or explanations > yet. A idea of how to use this for "models" in general, followed by > understanding the implications and current capabilities for multiplayer > "otherships" would be great. > > Any help would be appreciated, even references to archived discussions. > Thanks! > The model number was originally a concept which was thought to provide a hook for accessing the location of a particular model. Basically, it would internally end up going back to the FGLocation object for a particular model in order to reference it's position and orientation data. This would be set up by the model manager, be reserved for just aircraft models, and would provide a method of accessing models as an array of objects, similar to how the view manager sets up views. AFAIK this has not been implemented. The AI models, the scenery model work, the 3D cockpit, aircraft model work has involved a few developers and even so it is very well organized. It probably wouldn't actually take much to index the aircraft models and allow a view mode that rotates through a dynamically modified list of views which are sourced at the location of multiple models (without having to set each view up individually in preferences.xml). Some modifications to the code would be required. Without that happening, or happening right away, you can still acheive something similar by setting up additional views in preferences.xml. If you look at the "Look From" Tower in preferences.xml you'll see clearly how you can reference position and orientation values from anywhere in the property tree. And if I remember this code correctly, you can probably modify these "property paths" on the fly. For example if you had a nasal script that changes the string value in "/config/eye-alt-ft-path" then in fact the source property of the altitude of the view would change, next time the view manager class updates (every frame). Look especially at the update function in the viewmgr.cxx file in FlightGear/src/Main. Hope this helps. Best regards, Jim ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 747 Project
Durk Talsma wrote: On Tuesday 28 June 2005 18:36, John Wojnaroski wrote: Still running with a modified version of Durk's code we used at Scale3x. we've been invited back for Scale4x and might just go to the AVSIM meeting in San Diego during September. See www.flightgear.org/Project/747-JW Great to hear that you actually managed to use the code. Hopefully by the time of the next show, I have the taxiway following code in place. I have now added some basic AI network editing capability to taxidraw. Getting this to use by flightgear shouldn't be too hard to code anymore (provided I have time). Ground handling in FG is still lacking for the "heavies". Having to deal with a few more moving objects on the apron and taxiways would be an interesting exercise in ground handling. What's the date of the next meeting? Have been thinking of the AVSIM show in September down in San Diego, but not certain they will provide the support ( space and power) needed at the "low-ball" rate for freeware exhibits. Next planned event after that is Scale4X here in LA around Feb '06 ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 747 Project
On Tuesday 28 June 2005 18:36, John Wojnaroski wrote: > > Still running with a modified version of Durk's code we used at > Scale3x. we've been invited back for Scale4x and might just go to the > AVSIM meeting in San Diego during September. See > www.flightgear.org/Project/747-JW > Great to hear that you actually managed to use the code. Hopefully by the time of the next show, I have the taxiway following code in place. I have now added some basic AI network editing capability to taxidraw. Getting this to use by flightgear shouldn't be too hard to code anymore (provided I have time). What's the date of the next meeting? Cheers, Durk P.S., It's very likely I'm in San Fransisco around mid April next year, visiting the society for Cognitive Neuroscience meeting. Any shows scheduled around that time? D. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] ..multi-X trick ideas,
Martin Spott wrote: > "Ampere K. Hardraade" wrote: > > >>Interesting. I didn't know one can use both XFree and Xorg at the sametime. >>In anycase, this is way out of my league. =P > > > In principle there's nothing magic about this, as you can always run > more than one X server on your machine - be it XOrg or XFree86. > The only difficulty accrues from the habit that both installations > (XOrg and XFree86) tend to reside in /usr/X11R6/ - which is how it will > be handled by your Linux distribution. If you compile X11 yourself then > you can easily define "ProjectRoot" to some different location and run > both systems in parallel, > > Martin. The only problem I had when trying this was keeping one from loading the other's libraries. Josh ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Shadows
Ampere K. Hardraade wrote: > On June 27, 2005 05:40 pm, Curtis L. Olson wrote: > >>Yes, that's a tough one ... think about what happens when the sun is low >>in the sky ... an object that casts a shadow on the current view could >>be *way* outside the view frustum. I don't really understand how >>shadows work, but you'd almost have to do a complete rerendering >>(ssgCullandDraw) of the world from the sun's perspective to get this >>right ... I'm guessing that may be a bit expensive??? >> >>Curt. > > May be a history of the shadows can be kept, so the object that casts the > shadow is not drawn, the shadow will still stay for a while? > > Ampere > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > That wouldn't work if you were moving N or S, but at least you wouldn't see the shadow just up and disappear. Josh ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Attaching Views to Other Objects
Hi, I'm trying to track down how I can attach a view to another object in the sim, particularly for a multiplayer aircraft other than the ownship. I would like to switch to the viewpoint of each of the "other guys" in the virtual world. As documented at http://flightgear.org/Docs/fgfs-viewer-howto.html : Syntax for the eye position is: true or false modelnumber Syntax for the target or at position used in views of type "lookat" is: true or false modelnumber - But I can't find out where the "modelnumber" comes from, or what it really means. All the examples use zero, so I've assumed that was the ownship. I've looked through the code and docs, and searched many of the mailing-list archives, but haven't found any examples or explanations yet. A idea of how to use this for "models" in general, followed by understanding the implications and current capabilities for multiplayer "otherships" would be great. Any help would be appreciated, even references to archived discussions. Thanks! Jim ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 747 Project
Oooops, that's www.flightgear.org/Projects/747-JW John Wojnaroski wrote: Greetings, Between the time spent getting ready for shows like Scale and MIADC and the myriad other things that consume our daily lives found some time to work on the Project. Curt posted a couple of pics detailing the '05 rebuild. The project for the summer is to finish the center pedestal. MCDU screens are cannabilized from Sony Playstations with a little added circuitry to handle standard VGA output rather than TV and create composite video sync signals. The pedestal panels are from Flightdeck Solutions, located in Toronto and led by Peter Cos --- a top notch, world class oufit. Great parts and super support. The MIADC show with Mathworks in May was a big success. Support was outstanding and the sim log was full from setup to teardown. We had a large premium room all to ourselvs along with hospitality bar -- talk about a deadly combination ;-) Still running with a modified version of Durk's code we used at Scale3x. we've been invited back for Scale4x and might just go to the AVSIM meeting in San Diego during September. See www.flightgear.org/Project/747-JW Enjoy Regards John W ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Regarding buildings (was Shadows)
Martin Spott wrote: Frederic Bouvier wrote: Quoting Martin Spott : Look by yourself : http://terraserver.microsoft.com/image.aspx?T=4&S=12&Z=10&X=706&Y=5191&W=3 Oh, nice I think we urgently need a way to inject user-submitted landcover details into the process of scenery generation Curt, do you see a chance to accept geo-referenced shapefiles from users ? Martin. Since we are talking about scenary generation... Has no one wrote a converter from Taxidraw output to .btg ? Am I the only one frustrated because I can not (simply) edit a few airports and use the result imedialty ? From the terragear source I find it quite easy to do that, so if nothing exists I will write the converter. Harald. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] 747 Project
Greetings, Between the time spent getting ready for shows like Scale and MIADC and the myriad other things that consume our daily lives found some time to work on the Project. Curt posted a couple of pics detailing the '05 rebuild. The project for the summer is to finish the center pedestal. MCDU screens are cannabilized from Sony Playstations with a little added circuitry to handle standard VGA output rather than TV and create composite video sync signals. The pedestal panels are from Flightdeck Solutions, located in Toronto and led by Peter Cos --- a top notch, world class oufit. Great parts and super support. The MIADC show with Mathworks in May was a big success. Support was outstanding and the sim log was full from setup to teardown. We had a large premium room all to ourselvs along with hospitality bar -- talk about a deadly combination ;-) Still running with a modified version of Durk's code we used at Scale3x. we've been invited back for Scale4x and might just go to the AVSIM meeting in San Diego during September. See www.flightgear.org/Project/747-JW Enjoy Regards John W ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Last Driver NVIDIA 7667:==>approach lighting"rabbit" DO NOT Conflict with Graphic Card
> Gerard Robin wrote: > > > I am Just Ending the test of the last NVIDIA driver 7667 > june-22 The > >slowness in FG with VASI as vanished. > >That new driver seems right when working with existing OpenGL > >functionalities used by FG. > >I just notice a global speed a bit less than before (7664, without > >VASI). > >Good NEWS. > > > > > > That's great news, thanks for checking this out and reporting back. > Tried latest NVidia driver for Quadro Fx 3400. Better, but still a problem with VASI/PAPI. Sitting at KFSO: 7184 8-10 fps with VASI 75 fps without VASI 7718 15-18 fps with VASI 75 fps without VASI The "without VASI" is with Gerard's "fix" that comments out one line. All cases run with enhanced lighting turned off. BTW, this is on WinXP. Jim ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] readXML problems
> Norman Vine wrote: > > Erik Hofman writes: > > > >>Are you calling readXML while another call to readXML is in progress? > > > > > > Can't be done unless this other call is in a different thread :-) > > Hmm, that makes sense. I had the detached method of reading XML files > (non-easyXML) in mind where you had to do everything yourself. > > Erik I'm doing it in standalone JSBSim (calling readXML from within another readXML()). I thought you simply had to provide new arguments. Why would it work perfectly in standalone JSBSim, but not within FlightGear? I could probably get around that, but it would require some tedious re-work. Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] readXML problems
Norman Vine wrote: Erik Hofman writes: Are you calling readXML while another call to readXML is in progress? Can't be done unless this other call is in a different thread :-) Hmm, that makes sense. I had the detached method of reading XML files (non-easyXML) in mind where you had to do everything yourself. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] readXML problems
Erik Hofman writes: > > Are you calling readXML while another call to readXML is in progress? Can't be done unless this other call is in a different thread :-) Norman ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS for OpenAL
On Tue, 2005-06-28 at 08:23, bass pumped wrote: > > > > > > cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository co openal > > > I tried this command too!! nothing happened. it just sits. Didn't > even ask me for a password. I am using Fedora Core 2. Does this have > anything to do with it? > It's not Fedora Core 2 per se. I checked out OpenAl a while back with no trouble on FC2. Not tried updating recently, but last time I did, that happened just fine too. Steve ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] readXML problems
Jon Berndt wrote: I'm continuing to install the new JSBSim code. I've run into a strange problem. After I start up FlightGear and begin to parse an aircraft, I'll be humming along just fine until I get to the point where the engine file is specified. When the engine file is specified, it causes the file to be opened and read using a call to the easyXML routine, readXML(). It's the same routine, of course, that is being used to successfully parse the main aircraft config file. This works fine in JSBSim standalone, but in FlightGear, when this second call to readXML() is made, the program dies: FlightGear aborting I'm wondering if I missed something in the build process? Are you calling readXML while another call to readXML is in progress? It could be (I haven't checked this yet) that this function uses static local variables to store information and calling it again while another call is in progress would destroy the stored values. It might be better to store the filenames that need to be read and read them one after another. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] C library timing
There's ISO C's time() which only has second resolution. Then there's SUSv3's gettimeofday() which theoretically has microsecond resolution and in practice in the order of 10ms. Cheers -Gerhard -- Gerhard Wesp o o +43 (0)699 815 98 770 Bachtobelstrasse 56 | http://www.cosy.sbg.ac.at/~gwesp/ CH-8045 Zuerich \_/ See homepage for email address! ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] readXML problems
> I'm continuing to install the new JSBSim code. I've run into a strange > problem. After I > start up FlightGear and begin to parse an aircraft, I'll be humming along > just fine until > I get to the point where the engine file is specified. When the engine file is specified, > it causes the file to be opened and read using a call to the easyXML routine, > readXML(). > It's the same routine, of course, that is being used to successfully parse > the main > aircraft config file. This works fine in JSBSim standalone, but in > FlightGear, when this > second call to readXML() is made, the program dies: > > FlightGear aborting > > I'm wondering if I missed something in the build process? > > Jon Here's my call to readXML: --- start --- bool FGPropulsion::Load(Element* el) { string type, engine_filename; Element* document; FGXMLParse *engine_file_parser; ifstream* engine_file; Element* engine_element = el->FindElement("engine"); while (engine_element) { engine_filename = engine_element->GetAttributeValue("file"); if (!engine_filename.empty()) { engine_file = FindEngineFile(engine_filename); if (!engine_file->is_open()) { return false; } } else { cerr << "Engine definition did not supply an engine file." << endl; return false; } engine_file_parser = new FGXMLParse(); readXML(*engine_file, *engine_file_parser); // <-- dies here --- end --- Anyone else out there use readXML()? Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] help: .cxx extension not processed inMakefile.am
> As far as I know, none. This is the first time I heard of this behavior > ?!?? > > Erik It's frustrating as hell. I don't see that I am doing much different from the Makefile.am from the previous build. Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] readXML problems
I'm continuing to install the new JSBSim code. I've run into a strange problem. After I start up FlightGear and begin to parse an aircraft, I'll be humming along just fine until I get to the point where the engine file is specified. When the engine file is specified, it causes the file to be opened and read using a call to the easyXML routine, readXML(). It's the same routine, of course, that is being used to successfully parse the main aircraft config file. This works fine in JSBSim standalone, but in FlightGear, when this second call to readXML() is made, the program dies: FlightGear aborting I'm wondering if I missed something in the build process? Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] help: .cxx extension not processed in Makefile.am
Jon Berndt wrote: I've gotten the new JSBSim code to build in FlightGear. But, I had to rename the JSBSim.cxx file to JSBSim.cpp in order to get the Makefile that was generated from Makefile.am to work. I also had to refer to the JSBSim.cxx file as JSBSim.cpp in my Makefile.am. This all seems to work fine when I build JSBSim in standalone mode, but with FlightGear I can't seem to get the .cxx extension to be recognized. Does anyone know what kind of special considerations need to be made in order to get .cxx files to be recognized. As far as I know, none. This is the first time I heard of this behavior ?!?? Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] help: .cxx extension not processed in Makefile.am
I've gotten the new JSBSim code to build in FlightGear. But, I had to rename the JSBSim.cxx file to JSBSim.cpp in order to get the Makefile that was generated from Makefile.am to work. I also had to refer to the JSBSim.cxx file as JSBSim.cpp in my Makefile.am. This all seems to work fine when I build JSBSim in standalone mode, but with FlightGear I can't seem to get the .cxx extension to be recognized. Does anyone know what kind of special considerations need to be made in order to get .cxx files to be recognized. This is what I am using as Makefile.am in src/FDM/JSBSim/ now: --- start --- SUBDIRS = initialization models input_output math noinst_LIBRARIES = libJSBSim.a libJSBSim_a_SOURCES = JSBSim.cpp FGFDMExec.cpp FGJSBBase.cpp FGState.cpp INCLUDES = -I$(top_srcdir)/src/FDM/JSBSim -I$(top_srcdir)/src AM_CXXFLAGS = -DFGFS --- end --- Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Regarding buildings (was Shadows)
Frederic Bouvier wrote: > Quoting Martin Spott : >> Is this a natural river in the background ? > Look by yourself : > http://terraserver.microsoft.com/image.aspx?T=4&S=12&Z=10&X=706&Y=5191&W=3 Oh, nice I think we urgently need a way to inject user-submitted landcover details into the process of scenery generation Curt, do you see a chance to accept geo-referenced shapefiles from users ? Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Regarding buildings (was Shadows)
Quoting Martin Spott : > Frederic Bouvier wrote: > > > What do you mean ? > > http://ccrma.stanford.edu/~salauns/Oracle_building.jpg > > Hey Frederic, you obviously forgot to model the basin in front of the > buildings :-) I didn't lose the idea fgsd can do it one day ( I mean without addind other artefacts ). > Is this a natural river in the background ? Look by yourself : http://terraserver.microsoft.com/image.aspx?T=4&S=12&Z=10&X=706&Y=5191&W=3 -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Regarding buildings (was Shadows)
Frederic Bouvier wrote: > What do you mean ? > http://ccrma.stanford.edu/~salauns/Oracle_building.jpg Hey Frederic, you obviously forgot to model the basin in front of the buildings :-) Is this a natural river in the background ? Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Jitter related
bass pumped wrote: Did you perhaps modify the value of --model-hz somewhere? Low numbers here could cause all sorts of problems in the time-stepping code. run all the models at 48hz. could that cause a problem? I'll play with them and see what happens. That's quite low, I would at least double the value. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Regarding buildings (was Shadows)
Quoting "Ampere K. Hardraade" <[EMAIL PROTECTED]>: > On June 27, 2005 05:00 pm, Frederic Bouvier wrote: > > In the first, an oracle building cast its shadow on another one > > http://frbouvi.free.fr/flightsim/fgfs-shadow-1.jpg > > > > If I go forward a bit, the shadow disappear : > > http://frbouvi.free.fr/flightsim/fgfs-shadow-2.jpg > Would it make sense to give the building a base (such as a parking lot) for > future models? What do you mean ? http://ccrma.stanford.edu/~salauns/Oracle_building.jpg -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Jitter related
> Did you perhaps modify the value of --model-hz somewhere? > Low numbers here could cause all sorts of problems in the time-stepping > code. > run all the models at 48hz. could that cause a problem? I'll play with them and see what happens. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS for OpenAL
bass pumped wrote: The website says the password is 'guest'. It doesn't work for me! just stalls!! Try (no password). I works for me. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Jitter related
bass pumped wrote: I've seen what you talk about in all aircraft... except the point is that there is NO WIND!!! Did you perhaps modify the value of --model-hz somewhere? Low numbers here could cause all sorts of problems in the time-stepping code. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Shadows
Frederic Bouvier wrote: Harald JOHNSEN wrote : Don't change your model for that. If it's not a problem to rename your objects you can add a 'noshadow' prefix to your markings, they won't caste shadow ('mydecal' => 'noshadow.mydecal'). That can makes object names a bit long. It seems to me that there are a length limit on names in Blender. My personal preference is to turn the shadows into an animation. It would be a way to turn the shadows off by applying the animation. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS for OpenAL
> > Why do you yell at me !? I'm sorry... I didn't think I was yelling at you. But if u feel I did so, I sincerely apologize, that was not my intention. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS for OpenAL
bass pumped wrote: >> after doing a CVS login. I don't remember the password, though .. >> > The website says the password is 'guest'. It doesn't work for me! > just stalls!! Why do you yell at me !? Probably you are using a firewall which blocks your attempts - just an idea, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: CVS for OpenAL
* bass pumped -- Tuesday 28 June 2005 09:23: > > > cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository co openal > I tried this command too!! nothing happened. it just sits. I didn't try to check out again, but updating from that server works as it always did. I'd run cvs with the -t trace option: $ cvs -t -d ... co openal Maybe you have to update your cvs version. In some cases there were incompatibilities with local cvs binaries and the cvs server version. (My cvs is v1.12.9.) $ strace -fF cvs ... might tell you something about the problem, too. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS for OpenAL
> > > > cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository co openal I tried this command too!! nothing happened. it just sits. Didn't even ask me for a password. I am using Fedora Core 2. Does this have anything to do with it? ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS for OpenAL
> Yes, I do this already for months at least since FlightGear uses > OpenAL. I did the initial checkout using this command: > > cvs -d:pserver:[EMAIL PROTECTED]:/usr/local/cvs-repository co openal > > > after doing a CVS login. I don't remember the password, though .. > The website says the password is 'guest'. It doesn't work for me! just stalls!! ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d