[Flightgear-devel] CMake problem

2012-11-23 Thread Renk Thorsten
I'm just trying to get a working devel environment on my new machine, and I've succeeded in compiling simgear, but flightgear refuses the cmake configuration. Basically I want to have the simgear libs inside a user directory and not system-wide. So what I did is cloning the repositories,

Re: [Flightgear-devel] CMake problem

2012-11-23 Thread Adrian Musceac
On Friday, November 23, 2012 14:33:58 Renk Thorsten wrote: I'm just trying to get a working devel environment on my new machine, and I've succeeded in compiling simgear, but flightgear refuses the cmake configuration. Basically I want to have the simgear libs inside a user directory and not

Re: [Flightgear-devel] CMake problem

2012-11-23 Thread Geoff McLane
On Fri, 2012-11-23 at 12:33 +, Renk Thorsten wrote: cmake ../../flightgear -DSIMGEAR_DIR:PATH=/home/fgfs/FGLib Hi, Try - $ export SIMGEAR_DIR=/home/fgfs/FGLib \ cmake ../../flightgear In FG/CMakeModules/FindSimGear.cmake you will find HINTS $ENV{SIMGEAR_DIR} Note the 'ENV', so it

Re: [Flightgear-devel] CMake problem

2012-11-23 Thread James Turner
On 23 Nov 2012, at 12:33, Renk Thorsten wrote: When I change to my flightgear build directory and do cmake ../../flightgear Use the same CMAKE_INSTALL_PREFIX for everything, and it will all work out. No need to set SIMGEAR_DIR or anything. If you *have* set SIMGEAR_DIR or other

Re: [Flightgear-devel] CMake problem

2012-11-23 Thread Renk Thorsten
If you *have* set SIMGEAR_DIR or other settings, I'd recommend erasing your build directory and running cmake from clean - it 'remembers' previous values in the build dir's cache. Ah, that's how it's supposed to be... I've now hacked my way through by adding the path explicitly to

Re: [Flightgear-devel] Which navradio code is considered standard?

2012-11-23 Thread Adrian Musceac
On Thursday, November 22, 2012 21:44:03 ThorstenB wrote: navradio is the current/old standard, newnavradio is the new module. Most aircraft use navradio, few newnavradio. I'm not sure if there is a plan to switch/replace the old radio at some point, and whether the new module was compatible

Re: [Flightgear-devel] Which navradio code is considered standard?

2012-11-23 Thread James Turner
On 23 Nov 2012, at 13:47, Adrian Musceac wrote: Ok, here is a comparison using the classic navradio code before and after adding radio propagation calculations: Suggestion: make a runtime switch, to build the 'new' nav-radio when the old one is asked for - this can be done via some logic in

Re: [Flightgear-devel] Which navradio code is considered standard?

2012-11-23 Thread Adrian Musceac
On Friday, November 23, 2012 15:56:01 James Turner wrote: Hi James, Suggestion: make a runtime switch, to build the 'new' nav-radio when the old one is asked for - this can be done via some logic in the instrument manager. This of course assumes the visible interface, i.e read / written

Re: [Flightgear-devel] drawing the flight pass in the scenery

2012-11-23 Thread Adrian Musceac
On Friday, October 26, 2012 13:56:02 Marcel Baltzer wrote: Hello folks, I just freshly started using flightgear for a university project and I was wondering, if there is an easy method to hard code a subsystem that displays a calculated route into the scenery or marks objects in the

[Flightgear-devel] Strange GPU behaviour

2012-11-23 Thread Renk Thorsten
I guess I need some help here... I've finally managed to compile FG on the new computer, then copy my FGData here, and... it works. But the framerate is abysmally bad. It doesn't seem to be Flightgear though... When I open the NVIDIA X Server Settings while FG is running, I can see the

Re: [Flightgear-devel] Strange GPU behaviour

2012-11-23 Thread Emilian Huminiuc
Hi, You might want to take a look here: http://ubuntuforums.org/showthread.php?s=92e1641ae03fc09b4a10e772e569987bt=1478192page=2 I'm not sure if the settings suggested there still work with current drivers, but it's a start. Cheers Emilian

Re: [Flightgear-devel] Strange GPU behaviour

2012-11-23 Thread Alexis Bory
Le 23/11/2012 20:03, Renk Thorsten a écrit : I guess I need some help here... I've finally managed to compile FG on the new computer, then copy my FGData here, and... it works. But the framerate is abysmally bad. Hi Thorsten, Just to say that if you have a serious cloud coverage (with or

Re: [Flightgear-devel] Strange GPU behaviour

2012-11-23 Thread Alexis Bory
Le 23/11/2012 22:54, Alexis Bory a écrit : Here, core i7-3Ghz-16 MB RAM, GTX 680-2MB VRAM, 1920*1200px, BTW: - Linux 3.2.0-33 64 bits - NVidia driver: 304.64 -- Monitor your physical, virtual and cloud infrastructure

Re: [Flightgear-devel] Strange GPU behaviour

2012-11-23 Thread Eugenio Mondini
On Friday 23 November 2012 16:03:30 Renk Thorsten wrote: The driver is the 304.60 native NVIDIA driver obtained from rpmfusion as recommended by Fedora. I've read[*] that the new driver version 310 brings the improvements nvidia made in collaboration with valve, maybe you could try that if

[Flightgear-devel] Cyborg-X.xml changes

2012-11-23 Thread Nigel Mackay
1) Fixed hat-switch axis numbering under Windows. 2) Modifier switches stored value in property-tree with js[0] specifically in path. Changed to ordinary Nasal variable. Can someone please commit? Macnab ?xml version=1.0 encoding=UTF-8? !--Joystick binding definitions for Saitek Cyborg X and