Hi,
I used the preupgrade to FC12 from FC10 this Saturday on my ASUS
notebook (Intel core2 duo). This installed
openal-soft-1.10.622-2
openal-soft-devel-1.10.622-2 and
pulseaudio-0.9.21-1
I had to use OpenSceneGraph-2.9.5 as the svn up for osg broke fgfs link.
With the above I either get good
On Sun, Nov 29, 2009 at 12:54 AM, Jari Häkkinen wrote:
>
> I traced the problem to changeset 10838 in OSG. I cannot say what goes
> wrong but maybe one of the list readers do.
>
> http://www.openscenegraph.org/projects/osg/changeset/10838/OpenSceneGraph/trunk
Good job pinpointing the trouble!
Sin
I belive this is a change in the FG data format.
I recall that there was a change to the shaders that caused this about
two weeks ago.
try a refresh of the scenery data
Jason
On Sun, 2009-11-29 at 01:27 +0100, jean pellotier wrote:
> Jari Häkkinen a écrit :
> > On 2009-11-28 16.55, jean pellotie
Jari Häkkinen a écrit :
> On 2009-11-28 16.55, jean pellotier wrote:
>
>> Jari Häkkinen a écrit :
>>
>>> Hi all,
>>>
>>> I only get a blank single colour screen when I run fg (latest cvs/svn
>>> versions of plib/osg/simgear/fg). The colour changes with time settings,
>>> it is grey at noon,
On 2009-11-28 16.55, jean pellotier wrote:
> Jari Häkkinen a écrit :
>> Hi all,
>>
>> I only get a blank single colour screen when I run fg (latest cvs/svn
>> versions of plib/osg/simgear/fg). The colour changes with time settings,
>> it is grey at noon, bluish at dusk, and black in night time. I c
On 2009-11-28 23.01, Erik Hofman wrote:
> Jari Häkkinen wrote:
>> My comments was to elaborate on the consequences of the removed alut
>> support by Apple. It is dangerous to use any alut.h you find on the web.
>> As you point out using Creatives alut.h may make things simpler
>> (macports.org is a
Jari Häkkinen wrote:
> Hi again,
>
> Tanks for the pointers.
>
> My comments was to elaborate on the consequences of the removed alut
> support by Apple. It is dangerous to use any alut.h you find on the web.
> As you point out using Creatives alut.h may make things simpler
> (macports.org is an
Hi again,
Tanks for the pointers.
My comments was to elaborate on the consequences of the removed alut
support by Apple. It is dangerous to use any alut.h you find on the web.
As you point out using Creatives alut.h may make things simpler
(macports.org is another option). I used freealuts alu
Hi, maybe this one:
http://www.flyengravity.com/
Cheers
>
> Does anyone have any info on the cockpit panel shown at
> about time 1:18
> in that video?
>
> I'm wondering what they used for the various displays.
>
> If it's known an e-mail address for the builder would be
> appreciated!
>
> jj
Tatsuhiro Nishioka wrote:
Hi Jari,
First, I made patches for configure.ac in both SimGear and FlightGear
(except svn lib part) so please give it a try.
I tried your changes and they work well. However, I have a slightly
different strategy so I took your changes and adopted them to my
configu
Does anyone have any info on the cockpit panel shown at about time 1:18
in that video?
I'm wondering what they used for the various displays.
If it's known an e-mail address for the builder would be appreciated!
jj
http://kingmont.com
jj
On Sat, 2009-11-28 at 19:40 +, Heiko Schulz wrote
Hi,
found a video on Youtube, showing some scenes from the FSweekend.
And yes, we can see
FlightGear:http://www.youtube.com/watch?v=HCTo4Pfi1Mo&feature=related
It starts at 1:24 starring Durk Talsma!
There might be more videos as well!
Regards
HHS
> Hi All,
>
> Last weekend we've been organiz
Hi,
On Nov 28, 2009, at 7:16 PM, Tim Moore wrote:
> On 11/28/2009 05:25 AM, Tatsuhiro Nishioka wrote:
>> Hi Tim,
>>
>> As I said to you in IRC, I have a weird transparency problem with the
>> shaders enabled.
>> Here's the snapshot (helicopter view) with shaders.
>> http://macflightgear.sourcefo
Jari Häkkinen a écrit :
> Hi all,
>
> I only get a blank single colour screen when I run fg (latest cvs/svn
> versions of plib/osg/simgear/fg). The colour changes with time settings,
> it is grey at noon, bluish at dusk, and black in night time. I can see
> the top menu and I have sound. I get t
Hi all,
I only get a blank single colour screen when I run fg (latest cvs/svn
versions of plib/osg/simgear/fg). The colour changes with time settings,
it is grey at noon, bluish at dusk, and black in night time. I can see
the top menu and I have sound. I get the message saying which runway I
a
On Thu, 2009-11-26 at 19:55 +, Martin Spott wrote:
> Tim Moore wrote:
> > Update of /var/cvs/SimGear-0.3/source/simgear/scene/material
> > In directory baron.flightgear.org:/tmp/cvs-serv21713/simgear/scene/material
> >
> > Modified Files:
> >Effect.cxx
> > Log Message:
> [...]
> > +#
dave perry wrote:
> I have ATIS sound (at least at KBTL where I checked).
> Still no ident sounds for NDB, LOC, or VOR stations.
> Still now marker beacon sound.
Ah, found the problem; the sound group volume wasn't set at
initialization. Should be fixed now.
Erik
--
Erik Hofman wrote:
> Ron Jensen wrote:
>> Setting openal to not use pulse will not give these issues.
>
> Hm, that could be done for FlightGear. I´ve added support for using non
> default OpenAL output devices, but there's no code to use it that way
> yet. For example by using a command line opt
On 11/28/2009 05:25 AM, Tatsuhiro Nishioka wrote:
> Hi Tim,
>
> As I said to you in IRC, I have a weird transparency problem with the shaders
> enabled.
> Here's the snapshot (helicopter view) with shaders.
> http://macflightgear.sourceforge.net/wp-content/uploads/snapshots/3dclouds-effect-enable
> Hi,
>
> > Hi,
> >
> > I have just commited some changes to the xml autopilot.
> > Along with a tiny
> > bugfix
>
> Tiny? ;-)
Compared to the development going on in the view and sound system, this is
nothing ;-)
Torsten
---
Curt,
that sounds scary and reminds me of one oddity I notices some time ago.
That time only pid controller was affected, but I don't remember the details.
I think it was the integral sum that was not reset to zero. The current
implementation of the FGPIDController calculates differences to the
Ron Jensen wrote:
> Setting openal to not use pulse will not give these issues.
Hm, that could be done for FlightGear. I´ve added support for using non
default OpenAL output devices, but there's no code to use it that way
yet. For example by using a command line option or environment variable.
Tim Moore wrote:
> On 11/27/2009 10:08 AM, Erik Hofman wrote:
>> You could argue that the new sound code has little benefit over the
>> previous code (it does have the slight advantage of source management)
>> to make it necessary to include it in the next release already.
>>
> It's up to you. It
23 matches
Mail list logo
