Tim Moore wrote:
> You're seeing it in the pa24-250. The depth sort can go awry with
> nearly-coplanar polygons. Furthermore, it's too expensive to sort every
> polygon,
> so the sort is based on sets of polygons which just make the sorting
> ambiguity
> worse. The plib version doesn't sort a
James Turner wrote:
> On 16 Sep 2008, at 07:05, Erik Hofman wrote:
>
>>> ALPHA_TEST is slow on modern hardware, which is why I was hoping to
>>> not have it
>>> be on by default in the scene graph. Oh well. I'll leave this
>>> reverted for now
>>> and think about turning it on only for states
Erik Hofman wrote:
> dave perry wrote:
>
>> After updating SimGear and fgfs source from cvs this morning, the 3D
>> instruments in the pa24-250 and pa28-161 disappear and reappear
>> depending on the the viewing angle. This was not the case with cvs from
>> a week ago. After seeing this ano
dave perry wrote:
> After updating SimGear and fgfs source from cvs this morning, the 3D
> instruments in the pa24-250 and pa28-161 disappear and reappear
> depending on the the viewing angle. This was not the case with cvs from
> a week ago. After seeing this anomaly, I updated OpenSceneGra
On Sat, 2008-09-13 at 15:48 -0600, Ron Jensen wrote:
> On Sat, 2008-09-13 at 14:18 -0600, dave perry wrote:
> > After updating SimGear and fgfs source from cvs this morning, the 3D
> > instruments in the pa24-250 and pa28-161 disappear and reappear
> > depending on the the viewing angle. This wa
On Sat, 2008-09-13 at 14:18 -0600, dave perry wrote:
> After updating SimGear and fgfs source from cvs this morning, the 3D
> instruments in the pa24-250 and pa28-161 disappear and reappear
> depending on the the viewing angle. This was not the case with cvs from
> a week ago. After seeing thi
After updating SimGear and fgfs source from cvs this morning, the 3D
instruments in the pa24-250 and pa28-161 disappear and reappear
depending on the the viewing angle. This was not the case with cvs from
a week ago. After seeing this anomaly, I updated OpenSceneGraph from
today's svn and rec
Hi,
Thanks Curt,
You wrote half of what I really want to say.
As I only wrote one extreme aspect of my thought,
Many objections can be expected, but that's OK.
Actually I do agree with sharing files because of productivity,
ease in fixing bugs, availability of latest functions, etc.
however, th
* Curtis Olson -- Sunday 09 December 2007:
> a change to a common object breaks your aircraft. Newer aircraft
> may not work with older versions of FlightGear that don't have the
> shared pieces you expect.
Newer aircraft usually don't work with older releases, anyway. There's
too much changing.
On Dec 9, 2007 9:21 AM, Melchior FRANZ <> wrote:
> * Tatsuhiro Nishioka -- Sunday 09 December 2007:
> > For downloadable add-on aircraft, 3D instruments should be stored
> > inside each downloadable aircraft package even these can be duplicated.
>
> NO! $FG_ROOT/Aircraft/{Generic,Instruments,Instr
* Tatsuhiro Nishioka -- Sunday 09 December 2007:
> For downloadable add-on aircraft, 3D instruments should be stored
> inside each downloadable aircraft package even these can be duplicated.
NO! $FG_ROOT/Aircraft/{Generic,Instruments,Instruments-3d} are to
be shipped with the release. They are mea
Tatsuhiro Nishioka wrote:
> Hi Syd,
>
> For downloadable add-on aircraft, 3D instruments should be stored
> inside each downloadable aircraft package even these can be duplicated.
> I also think that each downloadable aircraft should be independent from
> both base package and other aircraft even t
Hi Syd,
For downloadable add-on aircraft, 3D instruments should be stored
inside each downloadable aircraft package even these can be duplicated.
I also think that each downloadable aircraft should be independent from
both base package and other aircraft even these share the same panel,
sound, etc
On Sunday 09 December 2007 07:22, Syd&Sandy wrote:
> Hi everyone ,
> I ran into another issue , just wondering what everyone else's opinion
> is
> on the matter. I,ve been updating the Bravo , and the Primus 1000
> instruments and controllers are in the Aircraft/Instruments-3d folder. I
> as
Hi everyone ,
I ran into another issue , just wondering what everyone else's opinion
is on the matter.
I,ve been updating the Bravo , and the Primus 1000 instruments and controllers
are in the Aircraft/Instruments-3d folder. I assumed that this is the place all
3d instruments should go .
>
> was it 10 or 12 engines???
oups - was 12...
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing
On 2/19/06, Torsten Dreyer <[EMAIL PROTECTED]> wrote:
> > Hi Torsten you dont have to create 2 separate 3d RPM gauges.
> > The xml file loads the .ac model , so create two separate RPM xml files,
> > one file driven by engine 1 , the other by engine 2 , but both files
> > using the same 3d mode
> Hi Torsten you dont have to create 2 separate 3d RPM gauges.
> The xml file loads the .ac model , so create two separate RPM xml files,
> one file driven by engine 1 , the other by engine 2 , but both files
> using the same 3d model
Yep - that's what I will do.
I hope I will never model t
Hi Torsten you dont have to create 2 separate 3d RPM gauges.
The xml file loads the .ac model , so create two separate RPM xml files,
one file driven by engine 1 , the other by engine 2 , but both files
using the same 3d model
Syd
-
On Tuesday 14 February 2006 06:28, Mathias Fröhlich wrote:
> Since we now have that feature, I would like to introduce mouse click
> actions for 3D instruments without panel using that code. I believe that
> this will give the 3D instruments a big push ...
Hi Matthias,
This is very good news I th
20 matches
Mail list logo
