Re: [Flightgear-devel] Turn Coordinator is out ==> c172r and others
On Sunday 26 June 2005 04:04, Ampere K. Hardraade wrote: > I notice it as well, but I thought my CVS version is outdated, so I didn't > mention it. > > Beside the turn coordinator, everything on the radio stack seems to be out > as well. It's the new nasalised electrical system. The turn indicator is hardcoded to expect 60 ampere as input. The new system outputs 28 volts instead (I told Curt that it made more sense to output volts rather than amperes). So the result is that the gyro is not spinning fast enough. I tried the radiostack just now, and it seemed to work fine. -- Roy Vegard Ovesen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Turn Coordinator is out ==> c172r and others
On June 25, 2005 08:20 pm, Gerard Robin wrote: > Beware instrument failure ! > C172r and others aircraft have a turn coordinator out of order :=( > seems to be property: > /instrumentation/turn-indicator/indicated-turn-rate I notice it as well, but I thought my CVS version is outdated, so I didn't mention it. Beside the turn coordinator, everything on the radio stack seems to be out as well. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Turn Coordinator is out ==> c172r and others
> Beware instrument failure ! > C172r and others aircraft have a turn coordinator out of order :=( > seems to be property: > /instrumentation/turn-indicator/indicated-turn-rate I noticed that. I wonder when that happened? Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Turn Coordinator is out ==> c172r and others
Beware instrument failure ! C172r and others aircraft have a turn coordinator out of order :=( seems to be property: /instrumentation/turn-indicator/indicated-turn-rate -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] RE: cygwin simgear problem
> > > >There was a similar problem report not far ago. It seems cygwin switched > >recently from gcc 3.3 to, and that is the problem. > >Vivian, what is your own version of gcc ? > > > >-Fred > > > >Vivian Meazza wrote : > > > > > tom bonnell > > > > > > Not really, except to say that I've compiled the cvs version under > > > Cygwin successfully in the last couple of days. > > > > > > Do you have a reasonably up-to-date version of Cygwin? > > > > > > I take it that plib compiled correctly? > > > > > > You might like to try the cvs version. > > > > > > Vivian > > > > > > In the make process of simgear 3.8 undercygwin I get these errors. can > > > you help? > > > > > gcc 3.4.4-1 updated last Thursday. I've just downloaded simgear cvs/head, > and compiled. No problems here. > > I had a problem: I thought possible file corruption, which is why I > updated. > It would certainly be worth trying going back to 3.3 and then re- > downloading > 3.4.4-1, which is what I did. I'm neither sure if that was the problem, > nor > if that solved it, but it all works here now. > > > I downloaded cygwin from internet a day ago I used older version of > cygwin and compiled the same simgear.tar withot having any problems. I > make and install zlib(in simgear) plib1.8 and I think as you said the > problem is caused from cygwin. What can i do TO MAKE it work?? > You can go back to gcc-g++ 3.3.3 by opening Cygwin setup, checking the appropriate box and re-downloading. That should fix the SimGear problem. If not then you are stuck with going forward to SimGear-cvs and using gcc-3.4.4. Either way, it's easy. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: New turbo/supercharger code
Le samedi 25 juin 2005 à 13:53 -0400, Josh Babcock a écrit : > Gerard Robin wrote: > > Le samedi 25 juin 2005 à 13:16 -0400, Josh Babcock a écrit : > > > >>Vivian Meazza wrote: > >> > >>>Josh Babcock > >>> > >>> > >>> > >>>I have a nagging memory that the Wright Cyclone R-3500 was fitted with > >>>reduction gearing between the crankshaft and propeller, although I can't > >>>find any reference to it right now. Do you have any details of the ratio? > >>>It's needed to migrate to the new Yasim propeller definition. > >>> > >>>You could use the R-2600 ratio, I suppose: > >>> > >>>Propeller Reduction Gear Ration (crankshaft to propeller): 16:9 > >>> > >>>That comes from here: > >>> > >>>http://wrightpattjobs.wpafb.af.mil/museum/engines/eng42a.htm > >>> > >>>V. > >>> > >>> > >>> > >>> > > > > Only for the fun, and may be seriously i can try to calculate it with > > the help of the new aeromatic propeller, i have implemented it locally. > > I need: Engine RPM -- Propeller diameter (inch or feet) -- Engine power > > ( HP or KW without boost). > > > > > 2700 rpm > 16'7" (4 blades) > 2200 hp > > Josh > = The results, i notice the calculation gives 3 blades with 2200 HP Inputs: horsepower: 2200 pitch: variable max engine rpm: 2700 prop diameter (ft): 16.7 Outputs: max prop rpm:1123.53 gear ratio: 2.40 Cp0:0.059661 Ct0:0.051308 static thrust (lbs):3327.61 --> 54.2414 200.4 3 2.40 12 30 899 1124 Again with 2400 HP we get 4 blades (min rpm and max rpm are the same) Inputs: horsepower: 2400 pitch: variable max engine rpm: 2700 prop diameter (ft): 16.7 Outputs: max prop rpm:1123.53 gear ratio: 2.40 Cp0:0.065084 Ct0:0.055972 static thrust (lbs):3630.12 --> 72.3219 200.4 4 2.40 12 30 899 1124 I don't know if it will be useful. > > > -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: New turbo/supercharger code
Gerard Robin wrote: > Le samedi 25 juin 2005 à 13:16 -0400, Josh Babcock a écrit : > >>Vivian Meazza wrote: >> >>>Josh Babcock >>> >>> >>> >>>I have a nagging memory that the Wright Cyclone R-3500 was fitted with >>>reduction gearing between the crankshaft and propeller, although I can't >>>find any reference to it right now. Do you have any details of the ratio? >>>It's needed to migrate to the new Yasim propeller definition. >>> >>>You could use the R-2600 ratio, I suppose: >>> >>>Propeller Reduction Gear Ration (crankshaft to propeller): 16:9 >>> >>>That comes from here: >>> >>>http://wrightpattjobs.wpafb.af.mil/museum/engines/eng42a.htm >>> >>>V. >>> >>> >>> >>> > > Only for the fun, and may be seriously i can try to calculate it with > the help of the new aeromatic propeller, i have implemented it locally. > I need: Engine RPM -- Propeller diameter (inch or feet) -- Engine power > ( HP or KW without boost). > > 2700 rpm 16'7" (4 blades) 2200 hp Josh ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Shadows
Paul Kahler wrote: Oh does that sound like a bad hack. What happens to objects that have specular highlights? Would the illumination be as if the sun were shining rather than the spotlight? Lighting is important, but this doesn't seem like it's physically correct at all. OTOH, fake lighting is better than no lighting ;-) Paul You are right, this is totaly incorrect lighting. For correct lighting and correct specular we should use an Opengl light for each light source. The problem is that opengl is sill slow for spot lights, and there can be more than 100 light around an airport. Of course opengl can not handle more than 8 lights in hardware (and I am not sure that it is still realtime on lot of machines) so we would have to switch ogl lights depending on the position of objects or ground geometry... a bit overkill I think. Perhaps can we use a real ogl light for the aircraft landing light and fake light for the airport lights, and since the view is centered on the aircraft the hack could be good enought. Harald. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: New turbo/supercharger code
Le samedi 25 juin 2005 à 13:16 -0400, Josh Babcock a écrit : > Vivian Meazza wrote: > > Josh Babcock > > > > > > > > I have a nagging memory that the Wright Cyclone R-3500 was fitted with > > reduction gearing between the crankshaft and propeller, although I can't > > find any reference to it right now. Do you have any details of the ratio? > > It's needed to migrate to the new Yasim propeller definition. > > > > You could use the R-2600 ratio, I suppose: > > > > Propeller Reduction Gear Ration (crankshaft to propeller): 16:9 > > > > That comes from here: > > > > http://wrightpattjobs.wpafb.af.mil/museum/engines/eng42a.htm > > > > V. > > > > > > > > Only for the fun, and may be seriously i can try to calculate it with the help of the new aeromatic propeller, i have implemented it locally. I need: Engine RPM -- Propeller diameter (inch or feet) -- Engine power ( HP or KW without boost). > -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] RE: cygwin simgear problem
There was a similar problem report not far ago. It seems cygwin switched recently from gcc 3.3 to, and that is the problem. Vivian, what is your own version of gcc ? -Fred Vivian Meazza wrote : > tom bonnell > > Not really, except to say that I've compiled the cvs version under > Cygwin successfully in the last couple of days. > > Do you have a reasonably up-to-date version of Cygwin? > > I take it that plib compiled correctly? > > You might like to try the cvs version. > > Vivian > > In the make process of simgear 3.8 undercygwin I get these errors. can > you help? > gcc 3.4.4-1 updated last Thursday. I've just downloaded simgear cvs/head, and compiled. No problems here. I had a problem: I thought possible file corruption, which is why I updated. It would certainly be worth trying going back to 3.3 and then re-downloading 3.4.4-1, which is what I did. I'm neither sure if that was the problem, nor if that solved it, but it all works here now. I downloaded cygwin from internet a day ago I used older version of cygwin and compiled the same simgear.tar withot having any problems. I make and install zlib(in simgear) plib1.8 and I think as you said the problem is caused from cygwin. What can i do TO MAKE it work?? thanks _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: New turbo/supercharger code
Vivian Meazza wrote: > Josh Babcock > > >>Melchior FRANZ wrote: >> >>>* Josh Babcock -- Saturday 25 June 2005 00:26: >>> >>> Weekly updates at http://jrbabcock.home.comcast.net/flightgear/superfort >>> >>> >>>I committed this, as it looks very nice and even flies, and there was a >> >>kind >> >>>of consense that this should be in cvs. I have yet to be able to land >> >>it, >> >>>though. Always goes into a deadly spin if I turn ... (There's some ugly >>>garbage hanging on the right main landing gear, and both don't retract.) >>> >>>m. >>> >>> >> >>Hmm, the right one should retract. The ugly junk is for testing, and >>will go away. Right now the stall speed is unusually high, and stalls >>can get pretty violent. The turn indicator is by far the most important >>instrument right now. I have not had a chance to fix this. >> > > > I've been having a look at the yasim config files. There are some odd > entries. I've tried to do a little fixing up, but with no real success. I > think you need to go to the new propeller definitions. > > I have a nagging memory that the Wright Cyclone R-3500 was fitted with > reduction gearing between the crankshaft and propeller, although I can't > find any reference to it right now. Do you have any details of the ratio? > It's needed to migrate to the new Yasim propeller definition. > > You could use the R-2600 ratio, I suppose: > > Propeller Reduction Gear Ration (crankshaft to propeller): 16:9 > > That comes from here: > > http://wrightpattjobs.wpafb.af.mil/museum/engines/eng42a.htm > > V. > > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > Yeah, they used 3350-23s originally. I know they are geared. The only references I have for that model engine state that it has a .355:1 gear ratio. Some later models had a .3475:1 ratio, but AFAIK none of them were ever used in the 29. Here's some references, none are what I would call really definitive. http://www.supercoolprops.com/ARTICLES/gwhitegearheads.htm http://www.sun-inet.or.jp/~ja2tko/eng/ok_b29.museum1.html http://definition-info.com/B-29.html Josh ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: New turbo/supercharger code
Josh Babcock > > Melchior FRANZ wrote: > > * Josh Babcock -- Saturday 25 June 2005 00:26: > > > >>Weekly updates at http://jrbabcock.home.comcast.net/flightgear/superfort > > > > > > I committed this, as it looks very nice and even flies, and there was a > kind > > of consense that this should be in cvs. I have yet to be able to land > it, > > though. Always goes into a deadly spin if I turn ... (There's some ugly > > garbage hanging on the right main landing gear, and both don't retract.) > > > > m. > > > > > > Hmm, the right one should retract. The ugly junk is for testing, and > will go away. Right now the stall speed is unusually high, and stalls > can get pretty violent. The turn indicator is by far the most important > instrument right now. I have not had a chance to fix this. > I've been having a look at the yasim config files. There are some odd entries. I've tried to do a little fixing up, but with no real success. I think you need to go to the new propeller definitions. I have a nagging memory that the Wright Cyclone R-3500 was fitted with reduction gearing between the crankshaft and propeller, although I can't find any reference to it right now. Do you have any details of the ratio? It's needed to migrate to the new Yasim propeller definition. You could use the R-2600 ratio, I suppose: Propeller Reduction Gear Ration (crankshaft to propeller): 16:9 That comes from here: http://wrightpattjobs.wpafb.af.mil/museum/engines/eng42a.htm V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Shadows
On Mon, 2005-06-20 at 18:53 +0200, Harald JOHNSEN wrote: > Ampere K. Hardraade wrote: > > >Finally, is there a potential for this technique of generating shadow to be > >used on generating the effects of spot lights (eg. landing light, taxi > >light, > >logo light, etc.)? > > > > > You are a genius, forget my previous reply. > We can't lighten pixels from the framebuffer because of the low > precision (8 bits) but we can of course darken them. > Algo (works better at full night) : > 1) render the scene and all non emissive geometry with a 'day' ambient term > 2) render all lights (or emissive geometry) and update the stencil > buffer ( stencil := 1) > 3) render a quad on screen to darken everything where stencil == 0 > > with 1 & 3 the scenery goes dark/black as usual > with 2 the scenery in light stay illuminated > Its quasi free, simple, support a million (fake) spot light ;) Oh does that sound like a bad hack. What happens to objects that have specular highlights? Would the illumination be as if the sun were shining rather than the spotlight? Lighting is important, but this doesn't seem like it's physically correct at all. OTOH, fake lighting is better than no lighting ;-) Paul ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: New turbo/supercharger code
Jon Berndt > > That all looks very good. Does your implementation of the Boost Control > just > > control the pressure, or does it act on the throttle as I understand was > the > > way it worked in the Merlin? In simulation terms the outcome is probably > the > > same. > > > > V. > > Hi, Vivian: > > That would be a question for Dave Luff, who wrote that engine model for > JSBSim. If I had > time I'd look at the FGPiston.cpp code, but I've got really limited time > today and > tomorrow; I'm getting the new JSBSim code integrated with FlightGear, > among other things > I've got to do. > > The last post I see from Dave was about 6 months ago on the JSBSim list. > Don't worry, it was only for interest. I can poke around in the code for myself. Thanks Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: New turbo/supercharger code
> That all looks very good. Does your implementation of the Boost Control just > control the pressure, or does it act on the throttle as I understand was the > way it worked in the Merlin? In simulation terms the outcome is probably the > same. > > V. Hi, Vivian: That would be a question for Dave Luff, who wrote that engine model for JSBSim. If I had time I'd look at the FGPiston.cpp code, but I've got really limited time today and tomorrow; I'm getting the new JSBSim code integrated with FlightGear, among other things I've got to do. The last post I see from Dave was about 6 months ago on the JSBSim list. Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: New turbo/supercharger code
Melchior FRANZ wrote: > * Josh Babcock -- Saturday 25 June 2005 00:26: > >>Weekly updates at http://jrbabcock.home.comcast.net/flightgear/superfort > > > I committed this, as it looks very nice and even flies, and there was a kind > of consense that this should be in cvs. I have yet to be able to land it, > though. Always goes into a deadly spin if I turn ... (There's some ugly > garbage hanging on the right main landing gear, and both don't retract.) > > m. > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > Hmm, the right one should retract. The ugly junk is for testing, and will go away. Right now the stall speed is unusually high, and stalls can get pretty violent. The turn indicator is by far the most important instrument right now. I have not had a chance to fix this. Josh ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: New turbo/supercharger code
* Josh Babcock -- Saturday 25 June 2005 00:26: > Weekly updates at http://jrbabcock.home.comcast.net/flightgear/superfort I committed this, as it looks very nice and even flies, and there was a kind of consense that this should be in cvs. I have yet to be able to land it, though. Always goes into a deadly spin if I turn ... (There's some ugly garbage hanging on the right main landing gear, and both don't retract.) m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: New turbo/supercharger code
Jon Berndt > > > Thanks, > > My question could be a question to Jon, Dave, and any JSB specialist. > > I just wonder, about, the opportunity to get profit of your work for > > developments on the JSB branch. The properties should be the same on > > the global FG level. > > Both FDM ->YASim ->JSBSim with a different "philosophic" approach should > > give the same end results. > > > > > -- > > Gerard > > See the FGPiston.h file in JSBSim. See the constructor in FGPiston.cpp for > exact specification in the new XML format (documentation pending). Here is > some data on what can be specified: > > Models Dave Luff's Turbo/Supercharged Piston engine model. > Additional elements are required for a supercharged engine. These can > be > left off a non-supercharged engine, ie. the changes are all backward > compatible at present. > > - NUMBOOSTSPEEDS - zero (or not present) for a naturally-aspirated > engine, > either 1, 2 or 3 for a boosted engine. This corresponds to the > number of > supercharger speeds. Merlin XII had 1 speed, Merlin 61 had 2, a > late > Griffon engine apparently had 3. No known engine more than 3, > although > some German engines apparently had a continuously variable-speed > supercharger. > > - BOOSTOVERRIDE - whether the boost pressure control system (either a > boost > control valve for superchargers or wastegate for turbochargers) can > be > overriden by the pilot. During wartime this was commonly possible, > and > known as "War Emergency Power" by the Brits. 1 or 0 in the config > file. > This isn't implemented in the model yet though, there would need to > be > some way of getting the boost control cutout lever position (on or > off) > from FlightGear first. > > - The next items are all appended with either 1, 2 or 3 depending on > which > boost speed they refer to, eg RATEDBOOST1. The rated values seems > to have > been a common convention at the time to express the maximum > continuously > available power, and the conditions to attain that power. > > - RATEDBOOST[123] - the absolute rated boost above sea level ambient > for a > given boost speed, in psi. Eg the Merlin XII had a rated boost of > 9psi, > giving approximately 42inHg manifold pressure up to the rated > altitude. > > - RATEDALTITUDE[123] - The altitude up to which rated boost can be > maintained. Up to this altitude the boost is maintained constant > for a > given throttle position by the BCV or wastegate. Beyond this > altitude the > manifold pressure must drop, since the supercharger is now at > maximum > unregulated output. The actual pressure multiplier of the > supercharger > system is calculated at initialisation from this value. > > - RATEDPOWER[123] - The power developed at rated boost at rated > altitude at > rated rpm. > > - RATEDRPM[123] - The rpm at which rated power is developed. > > - TAKEOFFBOOST - Takeoff boost in psi above ambient. Many aircraft > had an > extra boost setting beyond rated boost, but not totally uncontrolled > as in > the already mentioned boost-control-cutout, typically attained by > pushing > the throttle past a mechanical 'gate' preventing its inadvertant > use. This > was typically used for takeoff, and emergency situations, generally > for > not more than five minutes. This is a change in the boost control > setting, not the actual supercharger speed, and so would only give > extra > power below the rated altitude. When TAKEOFFBOOST is specified in > the > config file (and is above RATEDBOOST1), then the throttle position > is > interpreted as: > > - 0 to 0.95 : idle manifold pressure to rated boost (where attainable) > - 0.96, 0.97, 0.98 : rated boost (where attainable). > - 0.99, 1.0 : takeoff boost (where attainable). > > A typical takeoff boost for an earlyish Merlin was about 12psi, > compared > with a rated boost of 9psi. > > It is quite possible that other boost control settings could have been > used > on some aircraft, or that takeoff/extra boost could have activated by > other > means than pushing the throttle full forward through a gate, but this > will > suffice for now. > > Note that MAXMP is still the non-boosted max manifold pressure even > for > boosted engines - effectively this is simply a measure of the pressure > drop > through the fully open throttle. > That all looks very good. Does your implementation of the Boost Control just control the pressure, or does it act on the throttle as I understand was the way it worked in the Merlin? In simulation terms the outcome is probably the same. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-dev
Re: [Flightgear-devel] Re: New turbo/supercharger code
Vivian Meazza wrote: > > The link doesn't work. I think it might be time to consider giving aircraft > designers cvs access for their own work. > Sorry. There was a typo in the index.html file. Fixed. > > > Looks as if the pilot could adjust the wastegate settings in flight thus > controlling the turbo output. This will need a bit more investigation in > YASim. You are doing the B29 in YASim? > Yes. The YASim definition is very alpha right now though. Flyable, but the numbers are all wrong. I was having trouble getting it to converge so I gave it a break for a while to work on the 3D model. Josh ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] cygwin simgear problem
Fred > There was a similar problem report not far ago. It seems cygwin switched > recently from gcc 3.3 to, and that is the problem. > Vivian, what is your own version of gcc ? > > -Fred > > Vivian Meazza wrote : > > > tom bonnell > > > > Not really, except to say that I've compiled the cvs version under > > Cygwin successfully in the last couple of days. > > > > Do you have a reasonably up-to-date version of Cygwin? > > > > I take it that plib compiled correctly? > > > > You might like to try the cvs version. > > > > Vivian > > > > In the make process of simgear 3.8 undercygwin I get these errors. can > > you help? > > gcc 3.4.4-1 updated last Thursday. I've just downloaded simgear cvs/head, and compiled. No problems here. I had a problem: I thought possible file corruption, which is why I updated. It would certainly be worth trying going back to 3.3 and then re-downloading 3.4.4-1, which is what I did. I'm neither sure if that was the problem, nor if that solved it, but it all works here now. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] cygwin simgear problem
There was a similar problem report not far ago. It seems cygwin switched
recently from gcc 3.3 to gcc 3.4.4, and that is the problem.
Vivian, what is your own version of gcc ?
-Fred
Vivian Meazza wrote :
tom bonnell
Not really, except to say that I’ve compiled the cvs version under
Cygwin successfully in the last couple of days.
Do you have a reasonably up-to-date version of Cygwin?
I take it that plib compiled correctly?
You might like to try the cvs version.
Vivian
In the make process of simgear 3.8 undercygwin I get these errors. can
you help?
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/vector.tcc: In
member functio
n `void std::vector<_Tp,
_Alloc>::_M_fill_insert(__gnu_cxx::__normal_iterator
pename _Alloc::pointer, std::vector<_Tp, _Alloc> >, size_t, const _Tp&)':
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/vector.tcc:307:
error: expect
ed unqualified-id before '(' token
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/vector.tcc: In
member functio
n `void std::vector<_Tp,
_Alloc>::_M_range_insert(__gnu_cxx::__normal_iteratorypename _Alloc::pointer, std::vector<_Tp, _Alloc> >, _ForwardIterator,
_ForwardI
terator, std::forward_iterator_tag)':
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/vector.tcc:384:
error: expect
ed unqualified-id before '(' token
make[3]: *** [ephemeris.o] Error 1
make[3]: Leaving directory `/cygdrive/c/simgear/simgear/ephemeris'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/cygdrive/c/simgear/simgear'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/cygdrive/c/simgear/simgear'
make: *** [all-recursive] Error 1
_
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: New turbo/supercharger code
Josh Babcock > Vivian Meazza wrote: > > Josh Babcock > > > > > > > >>>Right now I've only researched the RR Merlin in any detail. Enough for > >> > >>our > >> > >>>current range of supercharged models. I don't know if Josh Babcock > needs > >>>anything special for the B29. > >>> > >> > >>I had done some research on the R-3350s, but it was a while ago. I do > >>know that the turbos are controled by an amplified rheostat, which I > >>think controls the the waste gate. > >> > >>Josh > >> > > > > > > Yes, that would be logical. > > > > Unless you have any turbo output pressure v height data, then I would > expect > > that the standard wastegate will model this well enough. Was there any > form > > of override which you would like to model? > > > > Are we going to get out hands on this model soon? I think there are > quite a > > few people looking forward to it, I know I am. > > > Weekly updates at http://jrbabcock.home.comcast.net/flightgear/superfort > I think Gerard was going to be commiting this, I'll have to check and > see what's up. The link doesn't work. I think it might be time to consider giving aircraft designers cvs access for their own work. > I'm not sure if that main control qualifies as an override. It's just a > dial that goes from 0 to 10 with a small mechanical safety switch for > going higher than 8. The pilot was supposed to st it to different > numbers at different power conditions and phases of the mission. 9 and > 10 were for emergencies. Looks as if the pilot could adjust the wastegate settings in flight thus controlling the turbo output. This will need a bit more investigation in YASim. You are doing the B29 in YASim? V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] cygwin simgear problem
tom bonnell
Not really, except to say that I’ve compiled the cvs
version under Cygwin successfully in the last couple of days.
Do you have a reasonably up-to-date version of Cygwin?
I take it that plib compiled correctly?
You might like to try the cvs version.
Vivian
In the
make process of simgear 3.8 undercygwin I get these errors. can you help?
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/vector.tcc:
In member functio
n `void std::vector<_Tp,
_Alloc>::_M_fill_insert(__gnu_cxx::__normal_iterator
pename _Alloc::pointer, std::vector<_Tp, _Alloc> >, size_t, const
_Tp&)':
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/vector.tcc:307: error:
expect
ed unqualified-id before '(' token
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/vector.tcc: In member
functio
n `void std::vector<_Tp,
_Alloc>::_M_range_insert(__gnu_cxx::__normal_iterator
ypename _Alloc::pointer, std::vector<_Tp, _Alloc> >, _ForwardIterator,
_ForwardI
terator, std::forward_iterator_tag)':
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/vector.tcc:384: error:
expect
ed unqualified-id before '(' token
make[3]: *** [ephemeris.o] Error 1
make[3]: Leaving directory `/cygdrive/c/simgear/simgear/ephemeris'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/cygdrive/c/simgear/simgear'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/cygdrive/c/simgear/simgear'
make: *** [all-recursive] Error 1
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] cygwin simgear problem
In the make process of simgear 3.8 undercygwin I get these errors. can you help?
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/vector.tcc: In member function `void std::vector<_Tp, _Alloc>::_M_fill_insert(__gnu_cxx::__normal_iteratorpename _Alloc::pointer, std::vector<_Tp, _Alloc> >, size_t, const _Tp&)':/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/vector.tcc:307: error: expected unqualified-id before '(' token/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/vector.tcc: In member function `void std::vector<_Tp, _Alloc>::_M_range_insert(__gnu_cxx::__normal_iteratorypename _Alloc::pointer, std::vector<_Tp, _Alloc> >, _ForwardIterator, _ForwardIterator, std::forward_iterator_tag)':/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/vector.tcc:384: error: expected unqualified-id before '(' tokenmake[3]: *** [ephemeris.o] Error 1make[3]: Leaving directory `/cygdrive/c/simgear/simgear/ephemeris'make[2]: *** [all-recursive] Error 1make[2]: Leaving
directory `/cygdrive/c/simgear/simgear'make[1]: *** [all] Error 2make[1]: Leaving directory `/cygdrive/c/simgear/simgear'make: *** [all-recursive] Error 1__Do You Yahoo!?Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
