Ok, so I went ahead and did a build of the latest and greatest...looks
(and sounds) really good. I love when when features are implemented
faster than I can ask for them! ;)
A couple observations:
1. Cannot adjust volume of atis(comm radios) from sound config dialog.
Not a "major" issue I guess s
Hi,
Jari Häkkinen wrote:
> Terragear complains about missing directory in the subversion repository:
>
> URL
> 'http://terrascenery.googlecode.com/svn/trunk/data/Scenery/Objects/e010n50/e014n54'
>
> doesn't exist
>
> Can someone please add it?
We don't have any objects available in this are
or just set the amb color to the same as rgb in the .ac file.
On 12/2/09, Curtis Olson wrote:
> Thanks Vadym and Erik, hopefully this does the trick.
>
> Curt.
>
>
> On Wed, Dec 2, 2009 at 8:46 AM, Vadym Kukhtin wrote:
>
>> 2009/12/2 Curtis Olson :
>>
>> > non-illuminated sides. Is there a howt
Thanks Vadym and Erik, hopefully this does the trick.
Curt.
On Wed, Dec 2, 2009 at 8:46 AM, Vadym Kukhtin wrote:
> 2009/12/2 Curtis Olson :
>
> > non-illuminated sides. Is there a howto posted somewhere that explains
> how
> > to fix this?
>
> Some time ago I found this in devel-list:
>
> #!
2009/12/2 Curtis Olson :
> non-illuminated sides. Is there a howto posted somewhere that explains how
> to fix this?
Some time ago I found this in devel-list:
#! /bin/sh
for f in "$@" ; do
sed -i.before-color-change
's,\(MATERIAL.*\)rgb\(.*\)amb\(.*\)emis\(.*\)spec\(.*\)shi\(.*\)trans\(.*\)$
Curtis Olson wrote:
> I've been playing around with the Rascal aircraft model, but it appears
> that it's never had it's materials updated and thus looks very dark on
> the non-illuminated sides. Is there a howto posted somewhere that
> explains how to fix this?
There's even a script floating
I've been playing around with the Rascal aircraft model, but it appears that
it's never had it's materials updated and thus looks very dark on the
non-illuminated sides. Is there a howto posted somewhere that explains how
to fix this?
Thanks,
Curt.
--
Curtis Olson: http://baron.flightgear.org/~
On Wed, Dec 2, 2009 at 8:29 AM, Csaba Halász wrote:
> On Wed, Dec 2, 2009 at 2:07 PM, Jacob Burbach wrote:
>> On Wed, Dec 2, 2009 at 7:52 AM, Erik Hofman wrote:
>>> You really should use CVS..
>>>
>>
>> I do. :) Though I do so selectively as to keep it usable for me and to
>> avoid conflicts wit
On Wed, Dec 2, 2009 at 12:57 AM, Tim Moore wrote:
> Just to be clear, are you running with
> CullThreadPerCameraDrawThreadPerContext,
> or what? How many of each?
>
Hi Tim,
I was running with AutomaticSelection and only had a single display enabled:
--prop:/sim/rendering/multithreading-mode=Au
On Wed, Dec 2, 2009 at 2:07 PM, Jacob Burbach wrote:
> On Wed, Dec 2, 2009 at 7:52 AM, Erik Hofman wrote:
>> You really should use CVS..
>>
>
> I do. :) Though I do so selectively as to keep it usable for me and to
> avoid conflicts with my personal modifications. So no, I'm not 100%
> inline wit
On Wed, Dec 2, 2009 at 7:52 AM, Erik Hofman wrote:
> You really should use CVS..
>
> Erik
I do. :) Though I do so selectively as to keep it usable for me and to
avoid conflicts with my personal modifications. So no, I'm not 100%
inline with current cvs, including I haven't yet merged in the new
s
Jacob Burbach wrote:
> This sounds really good, so the code to make independant groups with
> different devices is therejust needs an interface configurable
> through gui to manage it. It would be awesome to have the sound config
> dialog show a master volume slider for each group, as well as a
>> First, we really need better control of sound levels and balancing
>> between different sound sources. It is often impossible to hear ATIS
>> over the aircraft sounds for example. Having one master volume control
>> and volume properties on the radios is not enough. I think breaking it
>> into d
Stuart Buchanan wrote:
>
> So, the following arguments would all work:
>
> --aircraft=dhc2w
> --aircraft=dhc2W
> --aircraft=DHC2W
>
> Of course, if you think that dhc2-ski is better than dhc2s, then
that's > obviously your decision, but that's a different issue to the
one John brought up.
>
> -
On 2 Dec 2009, at 09:19, Stuart Buchanan wrote:
> Of course, if you think that dhc2-ski is better than dhc2s, then that's
> obviously your decision, but that's
> a different issue to the one John brought up.
Agreed on all counts - I will fix the case-sensitivity, but other issues are up
to the
syd adams wrote:
> Do what ?
> This was brought up in the past , and I suggested changing it to
> dhc2-wheels , etc ...
> but dont remember getting much feedback about it ... and I dont have
> much patience if those people pointing out "bugs" cant follow through
> and assist in coming up with a so
Do what ?
This was brought up in the past , and I suggested changing it to
dhc2-wheels , etc ...
but dont remember getting much feedback about it ... and I dont have
much patience if those people pointing out "bugs" cant follow through
and assist in coming up with a solution if they are able.
I'll
James Turner wrote:
> On 2 Dec 2009, at 07:40, Erik Hofman wrote:
>
>>> Secondly, I think it would be beneficial to have the ability to
>>> specify a sound device for a certain group. So you could, for example,
>>> send aircraft sounds to your speakers, and radio sounds to a headset.
>> Could be d
On 2 Dec 2009, at 07:40, Erik Hofman wrote:
>> Secondly, I think it would be beneficial to have the ability to
>> specify a sound device for a certain group. So you could, for example,
>> send aircraft sounds to your speakers, and radio sounds to a headset.
>
> Could be done with the current cod
On 2 Dec 2009, at 06:34, Ron Jensen wrote:
> | 39 – model capitalization –
> | observed: 19 Dec 2008
> | again: 31 Oct 2009
> |For example: when specifying the option --aircraft=dhc2W, the
> |"dhc" must not be capitalized, while the "W" must be capitalized.
>
> The value used for -
20 matches
Mail list logo
