Referring to the version number discussion, I've been given to understand here
http://www.flightgear.org/forums/viewtopic.php?f=19t=20137#p185619
that there have been already core developers referring to the next release as
2.12 a while ago who would now be obviously pretty annoyed about it
Hi Thorsten,
Wherever I mentioned 2.12, it was because that's the logical follow up on 2.10.
If we didn't decide anything, we'd automatically end up with 2.12 instead of
3.0.
That's all. I wouldn't worry too much about someone who's telling what other
people think, without he himself taking
Hi,
I am a new player in FlightGear and I am suffering from the low FPS.
Is there a way to fix it? If you want information about the device, tell me.
Hope you answer me soon,
Omar/AAL0118
--
This SF.net email is sponsored
Hi all,
I've now implemented all what I wanted about FGCom.
Now FGCom built-in is stable and fully working.
As stated with James, it's planned to add the feature once 2.12 branch is
created.
Also Vivian will add the new dialog (
http://i83.servimg.com/u/f83/16/09/76/33/captur13.png ) in fgdata
The hang glider is using the UIUC fdm, right? Perhaps that is using a
float (6-7 digits of precision) to represent it's initial
conditions ... or somewhere in the startup pipeline or the flightgear
interface to the uiuc
model, the initial lon/lat is stored as a float?
Curt, you pointed
On 24 Jun 2013, at 07:53, Gijs de Rooy gijsr...@hotmail.com wrote:
Wherever I mentioned 2.12, it was because that's the logical follow up on
2.10. If we didn't decide anything, we'd automatically end up with 2.12
instead of 3.0.
That's all. I wouldn't worry too much about someone who's
snip
I apologize for missing the point.
No need to apoligize at all.
If anybody is annoying somebody, it's me with my scheduled emails about
release deadlines, my requests for following a specific release
procedure and for raising discussions about version numbers.
Some time ago, we agreed on
On Thu, Jun 20, 2013 at 11:57 AM, Renk Thorsten wrote:
- ALS now works much better with the random trees. I think
there's still work to be done with other shaders (presumably
the wake shader has still to be ported?)
Yes (if that is really a major holdup, I can probably do this within the
Hi All,
I spent a little time this weekend looking through the Rembrandt
shader code to gain some familiarity and (naively) see if I could find
any obvious performance improvement, in particular by unwrapping
loops/if tests, as Rembrandt is just a little too slow on my machine
to be usable.
Hello,
By the way , does the terrain object bug, has been fixed, can we land on
buildings and any others solid objects.
I for days (may be weeks) i won't have any access to Git , so i won't be
able to check it.
Thank
Ahmad
On 24 June 2013 23:14, James Turner zakal...@mac.com wrote:
On
It seems that we have a problem with the FG/JSBSim-interface or it's a
rounding error during JSBSim-initialisation?!
Summarizing my observations:
- immediately after FG is started the property browser shows the
correct values
- this values hold true as long as the splash-screen appears
-
11 matches
Mail list logo