On 03/12/2010 05:13 PM, Tim Moore wrote:
>> 262383395d78565
OK!
Sign backs are all nice and gray now.
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactiv
On Sat, Mar 13, 2010 at 1:04 AM, John Denker wrote:
> On 03/12/2010 04:10 PM, Tim Moore wrote:
>
> > There shouldn't be any black or white
> > sign backs in the most recent code.
>
> Please say what commits constitute the appropriately
> recent code, so I don't need to grovel through the
> logs .
On 03/12/2010 04:10 PM, Tim Moore wrote:
> There shouldn't be any black or white
> sign backs in the most recent code.
Please say what commits constitute the appropriately
recent code, so I don't need to grovel through the
logs ... or at least so that I know what I'm looking
for when I grovel thr
On Fri, Mar 12, 2010 at 11:50 PM, John Denker wrote:
> On 03/12/2010 12:05 PM, Tim Moore wrote:
>
> >> I flew over there in the ufo and saw gray sign backs there...
>
> FWIW, if I limit the flight to the default screensize and
> default field of view, I find it difficult to reproduce
> this bug.
On 03/12/2010 12:05 PM, Tim Moore wrote:
>> I flew over there in the ufo and saw gray sign backs there...
FWIW, if I limit the flight to the default screensize and
default field of view, I find it difficult to reproduce
this bug.
On the other hand, if I expand the screen to HDTV size
and/or zoom
On Fri, Mar 12, 2010 at 7:43 PM, John Denker wrote:
> 2) The problem is not entirely gone. The window for
>> observing the bug is much smaller, but not zero.
>>
>> The symptom is the same: depending on camera tilt
>> angle, the backside of certain signs switches from
>> black to white.
>>
>
On Fri, Mar 12, 2010 at 7:43 PM, John Denker wrote:
> On 03/12/2010 06:54 AM, Tim Moore wrote:
> > I've checked in a fix for the sign-back problem. The airport sign code is
> > not fast graphics code and needs another look, but for the moment it
> works.
>
> 1) Thanks, the signs are much improved
On 03/12/2010 06:54 AM, Tim Moore wrote:
> I've checked in a fix for the sign-back problem. The airport sign code is
> not fast graphics code and needs another look, but for the moment it works.
1) Thanks, the signs are much improved.
2) The problem is not entirely gone. The window for
observin
I've checked in a fix for the sign-back problem. The airport sign code is
not fast graphics code and needs another look, but for the moment it works.
As for the other complaints...
On Thu, Mar 11, 2010 at 11:13 PM, Heiko Schulz wrote:
> Hi,
> >
> > FWIW, when I'm flying, I see the shading on the
On 03/11/2010 03:15 PM, Tim Moore wrote:
> The mesh representing the back of a sign is not complete; graphics state
> from other parts of the scenery are leaking into it. The particular effect
> depends on the global draw order, which does change as your viewing angle
> changes.
Thanks for the ra
On Thu, Mar 11, 2010 at 10:26 PM, John Denker wrote:
>
> For some tilt angles, the taxiway signs alongside taxiway
> charlie are dark, while at other title angles they are
> lit.
Not that it matters but I have reported this issue already:
http://www.mail-archive.com/flightgear-devel@lists.sourcef
On Thu, Mar 11, 2010 at 10:26 PM, John Denker wrote:
...
>
> Change the view angle, either by pitching the entire aircraft
> or by simply tilting the pilot's view angle relative to the
> aircraft.
>
> What is the expected output?
>
> Scenery should not change. The ray from each object to the
> c
Hi,
>
> FWIW, when I'm flying, I see the shading on the scenery
> change
> drastically during the flight as the plane turns and
> pitches. I think
> what's happened is instead of just changing the shading on
> the panel,
> we're changing the shading on the scenery too. FGFS
> didn't used to do
>
On Thu, Mar 11, 2010 at 4:47 PM, Heiko Schulz wrote:
> Wel,, I would see this as a bug, if the frontside with the letter can't be
> read then anymore. But your pics shows it can bes till, it is just the
> backside which changes the color.
>
> Not a serious bug or showstopper for
FWIW, when
> What steps will reproduce the
> problem?
>
> --lat=37.637855 --lon=-122.414915 --altitude=656
> --heading=113 --fdm=ufo
>
> aircraft is stopped. zero airspeed, zero rate of
> turn, etc.
>
> The choice of aircraft doesn't seem to matter; this
> is 100%
> reproducible chez moi using the defau
What steps will reproduce the problem?
--lat=37.637855 --lon=-122.414915 --altitude=656 --heading=113 --fdm=ufo
aircraft is stopped. zero airspeed, zero rate of turn, etc.
The choice of aircraft doesn't seem to matter; this is 100%
reproducible chez moi using the default c172p, the pa24-250,
e
16 matches
Mail list logo
