Re: [Flightgear-devel] Improved 737-300 with 3D-cockpit first WIP-release
2007/12/12, Heiko Schulz [EMAIL PROTECTED]: --- Ladislav MichnoviÄ#65533; [EMAIL PROTECTED] schrieb: 2007/12/9, Heiko Schulz [EMAIL PROTECTED]: Hi, There were some bugs causing a segfault. should be fixed now: http://www.hoerbird.net/737-300.v12.09.2007.tar.gz Hi. I've tried it but I'm little disappointed. There is already some older model of 737-300 in the data and it's more nicer that this from the tarball 737-300.v12.09.2007.tar.gz. The cockpit looks less nice, it lacks painting and last not least I'm missing those side wings on main wing which are only on model 300 AFAIK. This should be fixed. Bye. Regards Ladislav Sorry, my answer was a little bit harsh, but I'm working in freetime and the developement of this present cockpit of the boeing 737 was very hard because of problems keeping with the CVS-version. I apologize for my criticism. I didn't want to say you're doing your work bad. Your work on this plane is praiseworthy. I just wonder that the new version of 737-300 is not an upgrade of the previous model. But you probably doing it from scratch. It is difficult to make a cockpit of an aircraft, which was the second one! who came to FGFS and was still not correct in dimensions and has the wrong cockpit! (the 737-300 had never a glascockpit!) The 737-300 is like their sisters -400 and 500 also known as classic - usually it never had Winglets ( what you called as side wings). But some airlines added a kit with winglets to their 737-300 today, but when the 737-300 originally was developed, there wasn't winglets. Yes I meant the winglets. I did know how it is called in English. I flew with 737-300 and it has winglets. It seems not every 737-300 has winglets, only models built in this century. I think they look nice. If you could, please add them to the FG model. So don't be disapointed- if you want a better one, help or make a own better one! :-) I'm sorry, but I don't know how to do it. Regards Ladislav. Regards HHS - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] screenshots (and snapshots)
For a new release, especially one with version number 1.0, we
should provide some new screenshots for the website. Normally,
Curt would ask for that, but as he is/was away for a few days,
I start with this reminder. Screenshots should ...
- use maximum quality (antialiasing!)
- disable gui parts (menu/frame rate counter, unless that's what
you want to demonstrate, of course)
- ideally (but not necessarily) show something that is new in this
release: one of the aircraft shipped in the default package for
the first time, or a new feature (or at least something that is
in context with a new feature, so that a subscription text can
explain the feature)
Please don't just make random snapshots of random flights, but
aim for a good view angle, appropriate weather effects (not only
default weather, unless that's the most appropriate :-), ideal
sun angle (shadow angle - self-shadowing), etc. Look at some
of the last screenshots, most of which were quite good.
The contents of a screenshot shouldn't be (totally) cheated. That
is: one should be able to see the same scene with a default fgfs
if the weather, daytime etc. is the same (and one has a graphics
card good enough for real-time antialiasing). But some cheating is
acceptable, if it follows this principle. It's OK to use terrain/objects
that aren't in the default tiles (e.g. using KNID is fine), as
long as that's available from Jon's ObjectDB. It's *not* OK to show,
for example, a Jeep in a Hercules, as this isn't something we can
do with a flyable Hercules.
Unfortunately, my FX5500 isn't good enough for live antialiasing,
so I use an acceptable cheating method: from a local key binding
(Meta-d) I call a function dump_aircraft_snapshot() that saves
a snapshot, similar to what ac_state.nas does. This allows me to
make a normal (aliasing) flight with my target aircraft. When I
found a nice situation, I pause fgfs, then press the snapshot key,
and get a snapshot file, e.g ~/.fgfs/snapshot-KNID-A-10-1.xml
(automatically inserting the nearest airport and aircraft, as well
as an index number that prevents overwriting old files).
Now I turn on full anti-aliasing, and run fgfs again with
$ fgfs --aircraft=ufo ~/.fgfs/snapshot-KNID-A-10-1.xml
And now the A-10 hangs there like it did in the prior run, and
I can use the UFO to find a good viewing angle, good sun angle,
good weather etc. With full antialiasing that's still sluggish,
but workable.
Here's the result of a quick test with the A-10 near KNID. It
isn't spectacular, but you can see that there's full antialiasing
and still a nice shadow effect. This would have been quite hard
(though possible!) with a real A-10 flight.
http://members.aon.at/mfranz/a10.jpg [32.9 kB]
m.
var uniquefilename = func(format) {
for (var i = 1; i; i += 1) {
var name = sprintf(format, i);
if (io.stat(name) == nil)
return name;
}
}
var dump_aircraft_snapshot = func {
var ac = getprop(/sim/aircraft);
var apt = airportinfo().id;
var filename = uniquefilename(snapshot- ~ apt ~ - ~ ac ~ -%d.xml);
var save = props.Node.new({ filename: filename });
var data = save.getNode(data, 1);
var lat = getprop(/position/latitude-deg);
var lon = getprop(/position/longitude-deg);
var alt = getprop(/position/altitude-ft);
var m = data.getNode(sim/presets, 1);
m.getNode(latitude-deg, 1).setDoubleValue(lat);
m.getNode(longitude-deg, 1).setDoubleValue(lon);
m.getNode(altitude-ft, 1).setDoubleValue(alt);
var m = data.getNode(position, 1);
m.getNode(latitude-deg, 1).setDoubleValue(lat);
m.getNode(longitude-deg, 1).setDoubleValue(lon);
m.getNode(altitude-ft, 1).setDoubleValue(alt);
var m = data.getNode(models/model, 1);
m.getNode(path, 1).setValue(getprop(/sim/model/path));
m.getNode(latitude-deg, 1).setDoubleValue(lat);
m.getNode(longitude-deg, 1).setDoubleValue(lon);
m.getNode(elevation-ft, 1).setDoubleValue(alt);
m.getNode(heading-deg,
1).setDoubleValue(getprop(/orientation/heading-deg));
m.getNode(pitch-deg,
1).setDoubleValue(getprop(/orientation/pitch-deg));
m.getNode(roll-deg,
1).setDoubleValue(getprop(/orientation/roll-deg));
var g = props.globals;
props.copy(g.getNode(sim/model, 1), data.getNode(sim/model, 1));
props.copy(g.getNode(surface-positions, 1),
data.getNode(surface-positions, 1));
props.copy(g.getNode(controls, 1), data.getNode(controls, 1));
props.copy(g.getNode(engines, 1), data.getNode(engines, 1));
props.copy(g.getNode(rotors, 1), data.getNode(rotors, 1));
props.copy(g.getNode(gear, 1), data.getNode(gear, 1));
data.getNode(sim/model).removeChild(path, 0);
fgcommand(savexml, save);
print(snapshot written to , filename);
}
Re: [Flightgear-devel] CVS: data/Airports apt.dat.gz,1.7,1.8
Hi Arvid! AnMaster wrote: Durk Talsma wrote: My understanding is that a full world-wide scenery rebuild is taking place right now, courtesy of the Custom Scenery Project. The purpose of the rebuild is mainly to incorporate the latest apt.dat modifications and the latest commits to the object database. Resolution of the scenery should be approximately the same as the current scenery, but using the latest improvements to terragear, recently made by Ralf Gerlich. Nice. Where can I get this scenery? As I run a terrasync mirror I need to be able to download it to the server before the release to avoid problems. I guess I would need about a day or so to download the new scenery to the server. Martin and I have been working late since Wednesday to get that build going. It's the first time that we're doing this so we have no idea how long it is going to take, but we'll do our best to get it done on time. The process is running now and it's done when it's done. Cheers, Ralf - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] screenshots (and snapshots)
On ven 14 décembre 2007, gerard robin wrote: On ven 14 décembre 2007, Melchior FRANZ wrote: For a new release, especially one with version number 1.0, we should provide some new screenshots for the website. Normally, Curt would ask for that, but as he is/was away for a few days, I start with this reminder. Screenshots should ... SNIP Here's the result of a quick test with the A-10 near KNID. It isn't spectacular, but you can see that there's full antialiasing and still a nice shadow effect. This would have been quite hard (though possible!) with a real A-10 flight. http://members.aon.at/mfranz/a10.jpg [32.9 kB] m. yeah, i have one,:) It could be a tale the Alouette and the Cow http://pagesperso-orange.fr/GRTux/Alouette_III-img4.jpg (only a joke) Regards More serious, if the request is not Model productive only i can propose that one. It will need to remove the frame rate. Real weather (sorry no clouds here). http://pagesperso-orange.fr/GRTux/Lynx-img4.jpg Regards -- Gérard http://pagesperso-orange.fr/GRTux/ Less i work, better i go - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] screenshots (and snapshots)
On ven 14 décembre 2007, Melchior FRANZ wrote: For a new release, especially one with version number 1.0, we should provide some new screenshots for the website. Normally, Curt would ask for that, but as he is/was away for a few days, I start with this reminder. Screenshots should ... SNIP Here's the result of a quick test with the A-10 near KNID. It isn't spectacular, but you can see that there's full antialiasing and still a nice shadow effect. This would have been quite hard (though possible!) with a real A-10 flight. http://members.aon.at/mfranz/a10.jpg [32.9 kB] m. yeah, i have one,:) It could be a tale the Alouette and the Cow http://pagesperso-orange.fr/GRTux/Alouette_III-img4.jpg (only a joke) Regards -- Gérard http://pagesperso-orange.fr/GRTux/ Less i work, better i go - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] BUG(S) with new(?) KSFO scenery in cvs
Durk Talsma wrote: On Friday 14 December 2007 00:02, Stewart Andreason wrote: Also, at KOAK Oakland, I have also seen a 747 sitting on top of a 737 on top of some third plane at N37*43.34 W122*13.12 When you see stacked aircraft, that's usually a sign of overflow (i.e. more aircraft present than there are parkings available. If you see it, can you let me know around what time of day it occurs? So that I can have a look and see what kind of parkings need to be added. I assume that this is at KSFO? No, Oakland at the above lat/lon. Time of day between 10am and 3pm Pacific time. PST I'll watch for it again. Stewart - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] screenshots (and snapshots)
gerard robin Sent: 14 December 2007 15:31 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] screenshots (and snapshots) On ven 14 décembre 2007, Melchior FRANZ wrote: For a new release, especially one with version number 1.0, we should provide some new screenshots for the website. Normally, Curt would ask for that, but as he is/was away for a few days, I start with this reminder. Screenshots should ... SNIP Here's the result of a quick test with the A-10 near KNID. It isn't spectacular, but you can see that there's full antialiasing and still a nice shadow effect. This would have been quite hard (though possible!) with a real A-10 flight. http://members.aon.at/mfranz/a10.jpg [32.9 kB] m. yeah, i have one,:) It could be a tale the Alouette and the Cow http://pagesperso-orange.fr/GRTux/Alouette_III-img4.jpg (only a joke) Hey - a cow!!! First time I've seen one. Not bad at all :-) Vivian - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] screenshots (and snapshots)
On ven 14 décembre 2007, Vivian Meazza wrote: gerard robin Sent: 14 December 2007 15:31 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] screenshots (and snapshots) On ven 14 décembre 2007, Melchior FRANZ wrote: For a new release, especially one with version number 1.0, we should provide some new screenshots for the website. Normally, Curt would ask for that, but as he is/was away for a few days, I start with this reminder. Screenshots should ... SNIP Here's the result of a quick test with the A-10 near KNID. It isn't spectacular, but you can see that there's full antialiasing and still a nice shadow effect. This would have been quite hard (though possible!) with a real A-10 flight. http://members.aon.at/mfranz/a10.jpg [32.9 kB] m. yeah, i have one,:) It could be a tale the Alouette and the Cow http://pagesperso-orange.fr/GRTux/Alouette_III-img4.jpg (only a joke) Hey - a cow!!! First time I've seen one. Not bad at all :-) Vivian Yes nice cow, but you know very well :) Unfortunately without shadow , i just remember that the shadow don't apply to random objects. -- Gérard http://pagesperso-orange.fr/GRTux/ Less i work, better i go - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] OT: Malolo 1
As some of you may know, I'm not able to dedicate 100% of my life to the FlightGear project and I happened to be out of town this whole week. Here's a nice news story about one of the projects I'm involved with that aired on a local Honolulu news station last evening. There is a two minute video clip that you can watch of the actual broadcast ... just ignore the initial ad, and don't worry if the clip starts out talking about storm inspections, that only lasts for a couple seconds before it kicks into the real story. I'm the one holding the R/C transmitter in the clips, wearing a white Malolo1 t-shirt and shorts. http://www.khnl.com/Global/story.asp?S=7496023nav=menu55_2_2 I have been putting together the flight sensor package and the autopilot for the airframe. I am also the chief test pilot. On Wednesday morning we were able to charter a small boat and get permission to go out into a Navy operations area and do some over water test flights. We were able to successfully launch Malolo1 off the pitching boat, I was able to pilot it around the area manually, and then we were able to bring it in for a safe water landing and pluck it out of the ocean. We then were able to swap batteries and be back in the air for a second flight within 10 minutes. I have a couple dramatic pictures of the water launch/recover which I'll try to upload and post later. The Malolo1 is ideally suited for performing localized uav operations off of a small boat where a net or rope recovery is not possible. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/http://baron.flightgear.org/%7Ecurt/ Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Improved 737-300 with 3D-cockpit first WIP-release
--- Ladislav MichnoviÄ#65533; [EMAIL PROTECTED] schrieb: 2007/12/12, Heiko Schulz [EMAIL PROTECTED]: --- Ladislav MichnoviÄ#65533; [EMAIL PROTECTED] schrieb: 2007/12/9, Heiko Schulz [EMAIL PROTECTED]: Hi, There were some bugs causing a segfault. should be fixed now: http://www.hoerbird.net/737-300.v12.09.2007.tar.gz Hi. I've tried it but I'm little disappointed. There is already some older model of 737-300 in the data and it's more nicer that this from the tarball 737-300.v12.09.2007.tar.gz. The cockpit looks less nice, it lacks painting and last not least I'm missing those side wings on main wing which are only on model 300 AFAIK. This should be fixed. Bye. Regards Ladislav Sorry, my answer was a little bit harsh, but I'm working in freetime and the developement of this present cockpit of the boeing 737 was very hard because of problems keeping with the CVS-version. I apologize for my criticism. I didn't want to say you're doing your work bad. Your work on this plane is praiseworthy. I just wonder that the new version of 737-300 is not an upgrade of the previous model. But you probably doing it from scratch. It is difficult to make a cockpit of an aircraft, which was the second one! who came to FGFS and was still not correct in dimensions and has the wrong cockpit! (the 737-300 had never a glascockpit!) The 737-300 is like their sisters -400 and 500 also known as classic - usually it never had Winglets ( what you called as side wings). But some airlines added a kit with winglets to their 737-300 today, but when the 737-300 originally was developed, there wasn't winglets. Yes I meant the winglets. I did know how it is called in English. I flew with 737-300 and it has winglets. It seems not every 737-300 has winglets, only models built in this century. I think they look nice. If you could, please add them to the FG model. So don't be disapointed- if you want a better one, help or make a own better one! :-) I'm sorry, but I don't know how to do it. Regards Ladislav. Regards HHS - Hi, I have to be sorry, I was the one who was harsh. It is not from scratch- I used the cvs-present model. I only did the nose new and cut windows into the fuselage. I adjusted the length and the width of the fuselage and put the complete wing afterwards (what was difficault because of the animation). That was nessecary because the model-dimensions wasn't right. The outside cockpit section is still the same, I only add the glases. What was more difficult was to enbed the cockpit... I was surprised about your post, because you did not mention that I forgot to add the turbine blades... For the painting I have a Lufthansa, United Airlines ( new colors) and KLM in the pipeline. Indeed some 737-300 today have this winglets- there is a company who make this (it is not from Boeing!)- yes - the winglets looks good, but I would like this one without, representing the original one. But I also have the other one -400/500 and the NG's in the pipelines, so there will be maybe next year sometime the whole 737-fleet in FlightGear. Regards HHS still in work: http://www.hoerbird.net/galerie.html But already done: http://www.hoerbird.net/reisen.html Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s mit dem neuen Yahoo! Mail. www.yahoo.de/mail - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] screenshots (and snapshots)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Some questions: * What resolution should be used? I normally run with maximized window. For true full screen my monitor produces 1400x1280 however. However I don't like full screen. * I can run with 2x antialias in real time (the max in nvidia settings, 16x, is insanely slow). Should I use the snapshot way with 16x antialias? * Should I enable Anisotropic Filtering? * What about the texture sharpening feature? Normally I fly with 2x antialias, 2x Anisotropic Filtering, texture sharpening on. Regards, Arvid Norlander Melchior FRANZ wrote: For a new release, especially one with version number 1.0, we should provide some new screenshots for the website. Normally, Curt would ask for that, but as he is/was away for a few days, I start with this reminder. Screenshots should ... - use maximum quality (antialiasing!) - disable gui parts (menu/frame rate counter, unless that's what you want to demonstrate, of course) - ideally (but not necessarily) show something that is new in this release: one of the aircraft shipped in the default package for the first time, or a new feature (or at least something that is in context with a new feature, so that a subscription text can explain the feature) Please don't just make random snapshots of random flights, but aim for a good view angle, appropriate weather effects (not only default weather, unless that's the most appropriate :-), ideal sun angle (shadow angle - self-shadowing), etc. Look at some of the last screenshots, most of which were quite good. The contents of a screenshot shouldn't be (totally) cheated. That is: one should be able to see the same scene with a default fgfs if the weather, daytime etc. is the same (and one has a graphics card good enough for real-time antialiasing). But some cheating is acceptable, if it follows this principle. It's OK to use terrain/objects that aren't in the default tiles (e.g. using KNID is fine), as long as that's available from Jon's ObjectDB. It's *not* OK to show, for example, a Jeep in a Hercules, as this isn't something we can do with a flyable Hercules. Unfortunately, my FX5500 isn't good enough for live antialiasing, so I use an acceptable cheating method: from a local key binding (Meta-d) I call a function dump_aircraft_snapshot() that saves a snapshot, similar to what ac_state.nas does. This allows me to make a normal (aliasing) flight with my target aircraft. When I found a nice situation, I pause fgfs, then press the snapshot key, and get a snapshot file, e.g ~/.fgfs/snapshot-KNID-A-10-1.xml (automatically inserting the nearest airport and aircraft, as well as an index number that prevents overwriting old files). Now I turn on full anti-aliasing, and run fgfs again with $ fgfs --aircraft=ufo ~/.fgfs/snapshot-KNID-A-10-1.xml And now the A-10 hangs there like it did in the prior run, and I can use the UFO to find a good viewing angle, good sun angle, good weather etc. With full antialiasing that's still sluggish, but workable. Here's the result of a quick test with the A-10 near KNID. It isn't spectacular, but you can see that there's full antialiasing and still a nice shadow effect. This would have been quite hard (though possible!) with a real A-10 flight. http://members.aon.at/mfranz/a10.jpg [32.9 kB] m. - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHYu0zWmK6ng/aMNkRChOiAKC11LovPok1vVfiAKA563nNrxuDKACgoJep zQzH8oKzepE5BGy3AUnX2ZQ= =20qJ -END PGP SIGNATURE- - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] screenshots (and snapshots)
Hi there, Cool, I'm gonna take some cool shots. BTW, why don't we provide some more attractive media on the website. How about some short movies like seahawk taking off from Nimitz? Two aircraft passing by in MP session also would be very attractive to users. Best, Tat On Dec 14, 2007, at 9:43 PM, Melchior FRANZ wrote: For a new release, especially one with version number 1.0, we should provide some new screenshots for the website. Normally, Curt would ask for that, but as he is/was away for a few days, I start with this reminder. Screenshots should ... - use maximum quality (antialiasing!) - disable gui parts (menu/frame rate counter, unless that's what you want to demonstrate, of course) - ideally (but not necessarily) show something that is new in this release: one of the aircraft shipped in the default package for the first time, or a new feature (or at least something that is in context with a new feature, so that a subscription text can explain the feature) Please don't just make random snapshots of random flights, but aim for a good view angle, appropriate weather effects (not only default weather, unless that's the most appropriate :-), ideal sun angle (shadow angle - self-shadowing), etc. Look at some of the last screenshots, most of which were quite good. The contents of a screenshot shouldn't be (totally) cheated. That is: one should be able to see the same scene with a default fgfs if the weather, daytime etc. is the same (and one has a graphics card good enough for real-time antialiasing). But some cheating is acceptable, if it follows this principle. It's OK to use terrain/objects that aren't in the default tiles (e.g. using KNID is fine), as long as that's available from Jon's ObjectDB. It's *not* OK to show, for example, a Jeep in a Hercules, as this isn't something we can do with a flyable Hercules. Unfortunately, my FX5500 isn't good enough for live antialiasing, so I use an acceptable cheating method: from a local key binding (Meta-d) I call a function dump_aircraft_snapshot() that saves a snapshot, similar to what ac_state.nas does. This allows me to make a normal (aliasing) flight with my target aircraft. When I found a nice situation, I pause fgfs, then press the snapshot key, and get a snapshot file, e.g ~/.fgfs/snapshot-KNID-A-10-1.xml (automatically inserting the nearest airport and aircraft, as well as an index number that prevents overwriting old files). Now I turn on full anti-aliasing, and run fgfs again with $ fgfs --aircraft=ufo ~/.fgfs/snapshot-KNID-A-10-1.xml And now the A-10 hangs there like it did in the prior run, and I can use the UFO to find a good viewing angle, good sun angle, good weather etc. With full antialiasing that's still sluggish, but workable. Here's the result of a quick test with the A-10 near KNID. It isn't spectacular, but you can see that there's full antialiasing and still a nice shadow effect. This would have been quite hard (though possible!) with a real A-10 flight. http://members.aon.at/mfranz/a10.jpg [32.9 kB] m. snapshot.nas- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] screenshots (and snapshots)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This may be a duplicated, didn't manage to get through first time. Some questions: * What resolution should be used? I normally run with maximized window. For true full screen my monitor produces 1400x1280 however. However I don't like full screen. * I can run with 2x antialias in real time (the max in nvidia settings, 16x, is insanely slow). Should I use the snapshot way with 16x antialias? * Should I enable Anisotropic Filtering? * What about the texture sharpening feature? Normally I fly with 2x antialias, 2x Anisotropic Filtering, texture sharpening on. Regards, Arvid Norlander Melchior FRANZ wrote: For a new release, especially one with version number 1.0, we should provide some new screenshots for the website. Normally, Curt would ask for that, but as he is/was away for a few days, I start with this reminder. Screenshots should ... - use maximum quality (antialiasing!) - disable gui parts (menu/frame rate counter, unless that's what you want to demonstrate, of course) - ideally (but not necessarily) show something that is new in this release: one of the aircraft shipped in the default package for the first time, or a new feature (or at least something that is in context with a new feature, so that a subscription text can explain the feature) Please don't just make random snapshots of random flights, but aim for a good view angle, appropriate weather effects (not only default weather, unless that's the most appropriate :-), ideal sun angle (shadow angle - self-shadowing), etc. Look at some of the last screenshots, most of which were quite good. The contents of a screenshot shouldn't be (totally) cheated. That is: one should be able to see the same scene with a default fgfs if the weather, daytime etc. is the same (and one has a graphics card good enough for real-time antialiasing). But some cheating is acceptable, if it follows this principle. It's OK to use terrain/objects that aren't in the default tiles (e.g. using KNID is fine), as long as that's available from Jon's ObjectDB. It's *not* OK to show, for example, a Jeep in a Hercules, as this isn't something we can do with a flyable Hercules. Unfortunately, my FX5500 isn't good enough for live antialiasing, so I use an acceptable cheating method: from a local key binding (Meta-d) I call a function dump_aircraft_snapshot() that saves a snapshot, similar to what ac_state.nas does. This allows me to make a normal (aliasing) flight with my target aircraft. When I found a nice situation, I pause fgfs, then press the snapshot key, and get a snapshot file, e.g ~/.fgfs/snapshot-KNID-A-10-1.xml (automatically inserting the nearest airport and aircraft, as well as an index number that prevents overwriting old files). Now I turn on full anti-aliasing, and run fgfs again with $ fgfs --aircraft=ufo ~/.fgfs/snapshot-KNID-A-10-1.xml And now the A-10 hangs there like it did in the prior run, and I can use the UFO to find a good viewing angle, good sun angle, good weather etc. With full antialiasing that's still sluggish, but workable. Here's the result of a quick test with the A-10 near KNID. It isn't spectacular, but you can see that there's full antialiasing and still a nice shadow effect. This would have been quite hard (though possible!) with a real A-10 flight. http://members.aon.at/mfranz/a10.jpg [32.9 kB] m. - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHYwIhWmK6ng/aMNkRCqKrAKC1wGpsvLK9y1eDAA96u0Cdk8autgCgk11c AovwexPE4FTXkOkgAC0DVUk= =bfWG -END PGP SIGNATURE- - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] screenshots (and snapshots)
On Dec 14, 2007 3:54 PM, Tatsuhiro Nishioka wrote: BTW, why don't we provide some more attractive media on the website. How about some short movies like seahawk taking off from Nimitz? Two aircraft passing by in MP session also would be very attractive to users. For large files like video, I'd prefer to have them uploaded to a service like youtube that supports a wide variety of platforms and then post the link or embed the link on ourweb site. I believe we've referenced videos from our gallery in the past so I'd be happy to do it again. Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Pitts Transparency patch
Hi All, I've noticed a small bug in the pittss1c - viewed from the front, half of the fuselage is transparent when seen through the prop disk. The patch below fixes this by moving the Propdisk to the end of the .ac file. Please could someone apply the patch below to CVS. Thanks -Stuart Index: s1c.ac === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/pittss1c/Models/s1c.ac,v retrieving revision 1.1 diff -u -r1.1 s1c.ac --- s1c.ac10 Nov 2007 17:18:48 -1.1 +++ s1c.ac14 Dec 2007 23:33:11 - @@ -7,464 +7,6 @@ MATERIAL Material.002 rgb 0.103215 0.103215 0.103215 amb 0.5 0.5 0.5 emis 0 0 0 spec 0.360406 0.360406 0.360406 shi 32 trans 0.388511 OBJECT world kids 27 -OBJECT poly -name PropDisk -data 12 -Cylinder.002 -crease 30.00 -numvert 66 -0.289481 0.469547 -0.471136 -0.289481 0.36858 -0.553997 -0.289481 0.253387 -0.615568 -0.289481 0.128397 -0.653484 -0.289481 -0.001589 -0.666286 -0.289481 -0.131575 -0.653483 -0.289481 -0.256566 -0.615568 -0.289481 -0.371757 -0.553996 -0.289481 -0.472724 -0.471135 -0.289481 -0.85 -0.370168 -0.289481 -0.617156 -0.254977 -0.289481 -0.655071 -0.129986 -0.289481 -0.667874 0 -0.289481 -0.655072 0.129985 -0.289481 -0.617156 0.254976 -0.289481 -0.85 0.370168 -0.289481 -0.472725 0.471134 -0.289481 -0.371758 0.553996 -0.289481 -0.256567 0.615567 -0.289481 -0.131576 0.653483 -0.289481 -0.001591 0.666286 -0.289481 0.128395 0.653484 -0.289481 0.253386 0.61557 -0.289481 0.368578 0.553999 -0.289481 0.469545 0.471138 -0.289481 0.552406 0.370172 -0.289481 0.613979 0.254981 -0.289481 0.651895 0.129991 -0.289481 0.664698 5e-006 -0.289481 0.651897 -0.129981 -0.289481 0.613982 -0.254972 -0.289481 0.552412 -0.370164 -0.289481 -0.001588 0 -0.289481 -0.001588 0 -0.289481 0.552412 -0.370164 -0.289481 0.613982 -0.254972 -0.289481 0.651897 -0.129981 -0.289481 0.664698 5e-006 -0.289481 0.651895 0.129991 -0.289481 0.613979 0.254981 -0.289481 0.552406 0.370172 -0.289481 0.469545 0.471138 -0.289481 0.368578 0.553999 -0.289481 0.253386 0.61557 -0.289481 0.128395 0.653484 -0.289481 -0.001591 0.666286 -0.289481 -0.131576 0.653483 -0.289481 -0.256567 0.615567 -0.289481 -0.371758 0.553996 -0.289481 -0.472725 0.471134 -0.289481 -0.85 0.370168 -0.289481 -0.617156 0.254976 -0.289481 -0.655072 0.129985 -0.289481 -0.667874 0 -0.289481 -0.655071 -0.129986 -0.289481 -0.617156 -0.254977 -0.289481 -0.85 -0.370168 -0.289481 -0.472724 -0.471135 -0.289481 -0.371757 -0.553996 -0.289481 -0.256566 -0.615568 -0.289481 -0.131575 -0.653483 -0.289481 -0.001589 -0.666286 -0.289481 0.128397 -0.653484 -0.289481 0.253387 -0.615568 -0.289481 0.36858 -0.553997 -0.289481 0.469547 -0.471136 -numsurf 64 -SURF 0x10 -mat 1 -refs 3 -1 0.0 0.0 -0 0.0 0.0 -32 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -2 0.0 0.0 -1 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -3 0.0 0.0 -2 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -4 0.0 0.0 -3 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -5 0.0 0.0 -4 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -6 0.0 0.0 -5 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -7 0.0 0.0 -6 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -8 0.0 0.0 -7 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -9 0.0 0.0 -8 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -10 0.0 0.0 -9 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -11 0.0 0.0 -10 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -12 0.0 0.0 -11 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -13 0.0 0.0 -12 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -14 0.0 0.0 -13 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -15 0.0 0.0 -14 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -16 0.0 0.0 -15 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -17 0.0 0.0 -16 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -18 0.0 0.0 -17 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -19 0.0 0.0 -18 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -20 0.0 0.0 -19 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -21 0.0 0.0 -20 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -22 0.0 0.0 -21 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -23 0.0 0.0 -22 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -24 0.0 0.0 -23 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -25 0.0 0.0 -24 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -26 0.0 0.0 -25 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -27 0.0 0.0 -26 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -28 0.0 0.0 -27 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -29 0.0 0.0 -28 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -30 0.0 0.0 -29 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -31 0.0 0.0 -30 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -32 0.0 0.0 -0 0.0 0.0 -31 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -33 0.0 0.0 -34 0.0 0.0 -65 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -33 0.0 0.0 -35 0.0 0.0 -34 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -33 0.0 0.0 -36 0.0 0.0 -35 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -33 0.0 0.0 -37 0.0 0.0 -36 0.0 0.0 -SURF 0x10 -mat 1 -refs 3 -33 0.0 0.0 -38 0.0 0.0 -37
Re: [Flightgear-devel] screenshots (and snapshots)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I made some screenshots of A-10, A-6E, Lightning and Concorde. I uploaded them to http://rage.kuonet.org/~anmaster/flightgear/screenshots/1.0/ I might add more if I get time. The settings using in nvidia-settings: Antialias: 4x, 9-tap Gaussian Anisotropic Filtering: 8x Texture Sharpening: Yes All screenshots have been looselessly compressed with optipng before uploading (http://optipng.sourceforge.net/) at max level. Regards, Arvid Norlander Melchior FRANZ wrote: For a new release, especially one with version number 1.0, we should provide some new screenshots for the website. Normally, Curt would ask for that, but as he is/was away for a few days, I start with this reminder. Screenshots should ... - use maximum quality (antialiasing!) - disable gui parts (menu/frame rate counter, unless that's what you want to demonstrate, of course) - ideally (but not necessarily) show something that is new in this release: one of the aircraft shipped in the default package for the first time, or a new feature (or at least something that is in context with a new feature, so that a subscription text can explain the feature) Please don't just make random snapshots of random flights, but aim for a good view angle, appropriate weather effects (not only default weather, unless that's the most appropriate :-), ideal sun angle (shadow angle - self-shadowing), etc. Look at some of the last screenshots, most of which were quite good. The contents of a screenshot shouldn't be (totally) cheated. That is: one should be able to see the same scene with a default fgfs if the weather, daytime etc. is the same (and one has a graphics card good enough for real-time antialiasing). But some cheating is acceptable, if it follows this principle. It's OK to use terrain/objects that aren't in the default tiles (e.g. using KNID is fine), as long as that's available from Jon's ObjectDB. It's *not* OK to show, for example, a Jeep in a Hercules, as this isn't something we can do with a flyable Hercules. Unfortunately, my FX5500 isn't good enough for live antialiasing, so I use an acceptable cheating method: from a local key binding (Meta-d) I call a function dump_aircraft_snapshot() that saves a snapshot, similar to what ac_state.nas does. This allows me to make a normal (aliasing) flight with my target aircraft. When I found a nice situation, I pause fgfs, then press the snapshot key, and get a snapshot file, e.g ~/.fgfs/snapshot-KNID-A-10-1.xml (automatically inserting the nearest airport and aircraft, as well as an index number that prevents overwriting old files). Now I turn on full anti-aliasing, and run fgfs again with $ fgfs --aircraft=ufo ~/.fgfs/snapshot-KNID-A-10-1.xml And now the A-10 hangs there like it did in the prior run, and I can use the UFO to find a good viewing angle, good sun angle, good weather etc. With full antialiasing that's still sluggish, but workable. Here's the result of a quick test with the A-10 near KNID. It isn't spectacular, but you can see that there's full antialiasing and still a nice shadow effect. This would have been quite hard (though possible!) with a real A-10 flight. http://members.aon.at/mfranz/a10.jpg [32.9 kB] m. - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHYyR+WmK6ng/aMNkRCv2aAJwP1x2zVhIeEoGxoi/ZeyrSDWFP4ACghSSS 4/D7ClOdhjii5xQMwjeyRw0= =xWqY -END PGP SIGNATURE- - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] screenshots (and snapshots)
Hi, Ouch, Antialiasing doesn't work on Mac... I need someone who understand OpenGL on Mac better than me. Best, Tat On Dec 15, 2007, at 9:49 AM, AnMaster wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I made some screenshots of A-10, A-6E, Lightning and Concorde. I uploaded them to http://rage.kuonet.org/~anmaster/flightgear/screenshots/1.0/ I might add more if I get time. The settings using in nvidia-settings: Antialias: 4x, 9-tap Gaussian Anisotropic Filtering: 8x Texture Sharpening: Yes All screenshots have been looselessly compressed with optipng before uploading (http://optipng.sourceforge.net/) at max level. Regards, Arvid Norlander - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
