What version number will we give to the new
release? Are we ready for a 3.0 or is it 2.12?
Looking through my list of goals for the last coding period:
* Get a high-quality model shader running under Atmospheric Light Scattering
This is now available, working for random buildings and for
Thorsten
Sent: 18 June 2013 07:40
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] reminder: entering feature freeze now
What version number will we give to the new release? Are we ready for
a 3.0 or is it 2.12?
Looking through my list of goals for the last coding
On 18 Jun 2013, at 09:38, Vivian Meazza vivian.mea...@lineone.net wrote:
We still
cannot select the Screenshot Directory from the gui. I think that all argues
for 2.12.
Hmm, that is 'just a bug' which will be fixed during the release cycle, I just
keep forgetting about it since there's no
James
I have a fix to make it compile.
In SVNRepository.hxx, change names off 1st two elements in enum ResultCode
e.g.
enum ResultCode {
ERROR_NONE = 0,
ERROR_UNFOUND,
ERROR_SOCKET,
ERROR_XML,
ERROR_TXDELTA,
ERROR_IO,
ERROR_CHECKSUM
};
Also change these names in
A nice list and it's all worthwhile improvement, but it's all tinkering
around the edges of existing stuff. There's no step change which would
justify 3.0 IMO. For that we need something major, like new terrain
(850) or Rembrandt as the default.
*shrugs*
This would depend on if you're a
What is the most important ?
1/ To have a working stable Program whose the major options ( ALS,
REMBRANDT) remains options since conflicting each other.
2/ To have a working stable Program which include as a standard one of
these two options, which would definitively push on the back the
Hello, James
Back to the topic.
Thanks for the fix , right now we can use again the Autopilot with the GPS.
However the altitude is lost at each WP loading, set to Zero.
We could, before, keep on the original defined AP altitude, all over the
trip.
I know it was not realistic.
May be that
3/ To wait for better development reaching the target to have REMBRANDT
and
ALS working well all together, and definitively included within FG.
(...)
The basic content remains the same, some Aircrafts are flying with
Rembrandt not with ALS , others are flying with ALS not with Rembrandt
No one else has mentioned this so maybe its time for a make clean , but
this is what Im seeing after the recent tree updates :
http://imagebin.org/261806
--
This SF.net email is sponsored by Windows:
Build for Windows
Syd,
We fixed that bug a while back, I hope J. Could you rebuild with the latest
FG/SG and try again with the latest FGDATA? I really hope that fixes it!
Vivian
From: syd adams [mailto:adams@gmail.com]
Sent: 18 June 2013 19:16
To: FlightGear developers discussions
Subject:
On Tue, Jun 18, 2013 at 8:22 PM, Vivian Meazza wrote:
Syd,
We fixed that bug a while back, I hope J. Could you rebuild with the latest
FG/SG and try again with the latest FGDATA? I really hope that fixes it!
Me too!
Syd - if it doesn't fix it, can you let me know the following:
1) Are you
ALS already has an ON/OFF selection button.
Wouldn't it be useful for Rembrandt to also have such a button, thus being able
to switch it on or off either without restarting the sim?? It would skip all
the inconvenience of restarting the sim for activating Rembrandt.
Thank you! :)/Kle
-
From:
12 matches
Mail list logo