Re: [Flightgear-devel] Terragear-cs genapts stopway bug...
Gijs de Rooy wrote: Note that there is a runway texture template that almost nobody knows about anymore: http://cvs.flightgear.org/viewvc/graphics/runway/runway_layers.xcf?revision=1.3root=TerraGearview=markup Erik Erik, I actually used that template to create the stopway texture you see in Ron's screenshot. However, it does not match the current runway textures. I was unable to recreate runway textures with that template. It looks like the noise changed in the textures, but not in the template... I think the 'rubber coating' layer messes up the looks of it since it is consistent across the length of the runway but would be silly for the stopways. Maybe it would be a good idea to look at the runway layout again and recreate the runway textures. Possibly with skidmarks in mind. Erik -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] --disable-sound
James Sleeman wrote: On 11/01/10 00:02, Erik Hofman wrote: Historically it just muted the sound. I've now updated the code to not initialize the sound manager until specifically requested (which can be at runtime, even when --disable-sound is specified). Thanks, that seems to allow it to run without sound :-) Now, next question, is there a way that once FG is running, having given it --disable-sound, that I can trigger the sound manager to kick in and re-enable sound. The Sound Configuration dialog doesn't do anything when --disable-sound is given (looks like it should, but it doesn't). Setting /sim/sound/working to 'true' should enable the sound manager at runtime. Erik -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] --disable-sound
Erik, Erik Hofman wrote: Setting /sim/sound/working to 'true' should enable the sound manager at runtime. While you are at it, is /sim/sound/enabled still supposed to have any effect or is/should it now being obsolete ? Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Terragear-cs genapts stopway bug...
Erik Hofman wrote: Maybe it would be a good idea to look at the runway layout again and recreate the runway textures. Possibly with skidmarks in mind. In the mean time I've added two stopway textures that might be good enough for now (pa_stopway.png and pc_stopway.png). Erik -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] --disable-sound
Martin Spott wrote: Erik, Erik Hofman wrote: Setting /sim/sound/working to 'true' should enable the sound manager at runtime. While you are at it, is /sim/sound/enabled still supposed to have any effect or is/should it now being obsolete ? That property is used for muting the sound at runtime (part of the soundmanager keeps running to update positions and such). Erik -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] --disable-sound
Erik Hofman wrote: Martin Spott wrote: While you are at it, is /sim/sound/enabled still supposed to have any effect or is/should it now being obsolete ? That property is used for muting the sound at runtime (part of the soundmanager keeps running to update positions and such). May I suggest to rename this property into something like mute, just to imcrease the comprehensibility ? Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] --disable-sound
Martin Spott wrote: Erik Hofman wrote: Martin Spott wrote: While you are at it, is /sim/sound/enabled still supposed to have any effect or is/should it now being obsolete ? That property is used for muting the sound at runtime (part of the soundmanager keeps running to update positions and such). May I suggest to rename this property into something like mute, just to imcrease the comprehensibility ? For backwards compatibility it would be better to leave it like it is. Erik -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] TerraGear terrafit python script
Hi all, Does someone have a working copy of the terrafit.py script? I have the one from the TerraGear 0.9.8 tar ball at terragear.org, but it isn't working on my system (Mac OS 10.4, using Unix command line, Python version 3.0.1). Python is not my language, so trying to get it working is getting a bit tedious. Could it be time to update the TerraGear source code to make it more readily buildable? Thanks Andrew -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] TerraGear terrafit python script
Andrew Gillanders wrote: Hi all, Does someone have a working copy of the terrafit.py script? I have the one from the TerraGear 0.9.8 tar ball at terragear.org, but it isn't working on my system (Mac OS 10.4, using Unix command line, Python version 3.0.1). Python is not my language, so trying to get it working is getting a bit tedious. Could it be time to update the TerraGear source code to make it more readily buildable? Have you tried with python 2.x? Jon -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Win32-built -Towards the new Release
Benoît Laniel Le samedi 09 janvier 2010 à 21:39 +, Heiko Schulz a écrit : Thanks for your work! Thanks for testing! Benoit Laniel's exe: - Yasim seems to have a bug- the Bell UH1 doesn't work and produces a lot of ugly Nan's which crashes FGFS Indeed. It seems to be a problem with nasal. I'll check that. Vivian Meazza's exe: - sound devices not visible (only readable hardware device/ software device) -sound doppler totally broken, especially on fly-by-view sound devices are visible here. Doppler is sort of working, but badly, and nothing like as well as we used to have. Or is this all because of different sources (official-CVS vs unofficial- GIT)? Official cvs-head here, although I have tried to use git in the past. I use flightgear CVS with openal-soft, I think Vivian Meazza uses creative's openal. I updated the snapshots and now have a functional (probably not bug free) terrasync with svn support built-in: http://blaniel.free.fr/pub/flightgear/snapshots/fgfs_win32_20100110.7z I'm using a fairly old terrasync built by Fred. It seems bug free, except on exit. I'm currently struggling to rebuild my machine after hdd failure. I can't access MSVC9 atm. I think I used openal-soft on recent builds, but I can't really remember. Vivian -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Terragear-cs genapts stopway bug...
Gijs de Rooy wrote: Erik, I actually used that template to create the stopway texture you see in Ron's screenshot. However, it does not match the current runway textures. Please note also that the piece of the runway which is mapped into blastway/stopway in Robin's definition might look quite different from the regular runway tarmac. According to my real-life experience the stopway is often not just made from a different material (probably just something 'cheaper'), they also don't have the habit of cleaning this part, so it looks dirty ;-) Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Ubuntu fatal error - rumble.wav?
On Sun, 2010-01-10 at 20:18 +0100, Erik Hofman wrote:
Geoff McLane wrote:
Hi all,
But in Ubuntu 8.04 LTS, now get an error exit when running the
default c172... it ran great a few days ago, when I reported
all seemed well... but now...
Running it under gdb, and setting a break point
at SGSoundMgr::load(), and on the 2nd time
through this function, got the trace attached...
Essentially from the lines of code -
555 data = alutLoadMemoryFromFile(samplepath.c_str(), format,
size, freqf );
556 freq = (ALsizei)freqf;
557 int error = alutGetError();
558 if (data == NULL || error != ALUT_ERROR_NO_ERROR) {
the 'data' is NULL, but even if it was not, additionally
'error' contains a value 518 (0x206)...
Again, I though I had read this before in a recent board
message, and thought a CVS 'fix' had been made, but now not
so sure...
At least it's not the latest CVS code, this code has been replaced by a
(supposedly) better check.
Erik
Hi Erik,
Thank you for the reply, but now I am even more
confused ;=()
This is the soundmgr_openal.cxx I have...
~/fg/fg7/simgear/source/simgear/sound$ cvs status soundmgr_openal.cxx
===
File: soundmgr_openal.cxx Status: Up-to-date
Working revision: 1.87
Repository revision:
1.87 /var/cvs/SimGear-0.3/source/simgear/sound/soundmgr_openal.cxx,v
Sticky Tag:(none)
Sticky Date: (none)
Sticky Options: (none)
And that contains the code, in function SGSoundMgr::load()
...
#if defined(ALUT_API_MAJOR_VERSION) ALUT_API_MAJOR_VERSION = 1
ALfloat freqf;
data = alutLoadMemoryFromFile(samplepath.c_str(), format, size,
freqf );
freq = (ALsizei)freqf;
int error = alutGetError();
if (data == NULL || error != ALUT_ERROR_NO_ERROR) {
string msg = Failed to load wav file: ;
msg.append(alutGetErrorString(error));
throw sg_io_exception(msg.c_str(), sg_location(samplepath));
return false;
}
#else
You mean ALUT_API_MAJOR_VERSION should NOT be defined,
or be less than 1???
The included file, through #include AL/alut.h, which in
my case is in /usr/include/AL/alut.h, contains :-
#define ALUT_API_MAJOR_VERSION 1
#define ALUT_API_MINOR_VERSION 1
Is this the WRONG alut.h??? But it all works fine
with the simple 'hello world' OpenAL sample code...
And doing 'make check' in SG/sound, openal_test1,
2, and 3, each seem to run ok...
And when I tried a compile using the 'alternative'
coded alutLoadWAVFile() I get a warning that this is
'depreciated', and get the SAME error exit
anyway... and the code changes, checking that
alutGetErrorString(error) returns a value is
only in this 'alternate' code...
As stated, getting confused... Is there anything
else I can try, check, install? As advised, it all
ran fine a week or so ago...
Regards,
Geoff.
gdb debug text: http://geoffair.net/tmp/gdb-02.txt
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Terragear-cs genapts stopway bug...
On Mon, 2010-01-11 at 18:58 +, Martin Spott wrote: Gijs de Rooy wrote: Erik, I actually used that template to create the stopway texture you see in Ron's screenshot. However, it does not match the current runway textures. Please note also that the piece of the runway which is mapped into blastway/stopway in Robin's definition might look quite different from the regular runway tarmac. I wonder if we should use the shoulder material if it is set? Or we could just always use asphalt to keep the dirty look? According to my real-life experience the stopway is often not just made from a different material (probably just something 'cheaper'), they also don't have the habit of cleaning this part, so it looks dirty ;-) Cheers, Martin. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Ubuntu fatal error - rumble.wav?
Geoff McLane wrote: Thank you for the reply, but now I am even more confused ;=() Ah wait, I looked at the code for a different ALUT version.. I must have looked at the wrong code because of it ran great a few days ago, when I reported all seemed well... but now... and the code I looked at was changed just a few days ago. I'm starting to wonder what has changed in the mean time.. need to look at that this week (I'm quite busy so i can't promise any time frame). I looks odd since this line 'int error = alutGetError();' should clear any error for the next call. Erik -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
