Re: [Flightgear-devel] 2.10.0 Changelog - help required
On Mon, Jan 21, 2013 at 08:12:27PM +, Olivier wrote: Hi James, De : James Turner zakal...@mac.com À : FlightGear developers discussions flightgear-devel@lists.sourceforge.net Envoyé le : Samedi 19 janvier 2013 15h35 Objet : Re: [Flightgear-devel] 2.10.0 Changelog - help required Thanks, I've committed these. Thanks to you for committing the French language files. However, the first work would be to synchronise the language files with the English language files, because if they are not synced, the new menu entries between 2.8 and 2.10 will appear in English in other languages, eg for the flight recorder. As stated here: https://www.gitorious.org/fg/fgdata/blobs/master/Translations/fr/sys.xml Last synchronized with English master resource on 2012-September-21 for FlightGear 2.9.0Olivier I added the missing strings manually and it worked. The thing I think does not work are accents in the splashscreen translations, Is this because of the different font? Also the translations for common aircraft menus worked only on the c172p from what I could see, not on the 777 for example. -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.0 Changelog - help required
On Saturday 19 January 2013 09:35:38 James Turner wrote: On 18 Jan 2013, at 20:58, James Turner zakal...@mac.com wrote: Whoop, that is bad. I'm happy to merge translation changes, will do French one tomorrow. Any other volunteers for other languages? Since I only speak English it would be better if two people did each - one to author, one to review. This is merged and pushed, and I am chasing people for updated Dutch translations. Any other language patches I will apply if emailed to me! Hi James, for 2.8 this was coordinated by ThorstenB in the forum [0]. You can find the updated spanish files here: https://www.dropbox.com/sh/j1c9077psmkyt5k/5Lp_xlnUiv/menu.xml https://www.dropbox.com/sh/j1c9077psmkyt5k/1BSeAiKyug/options.xml https://www.dropbox.com/sh/j1c9077psmkyt5k/cbjsL6Qq3p/sys.xml It was asked for review in the spanish forums [1] but I'm still waiting for confirmation. Thanks. [0] http://flightgear.org/forums/viewtopic.php?f=42t=16876 [1] http://flightgear.creatuforo.com/-temas31044.html#31044 -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122912 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Strange GPU behaviour
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 it's not to bad to use the nvidia installer instead of using fedora packaging. At least is not worst than using windows. [*] http://feedproxy.google.com/~r/Phoronix/~3/v4Bk8aNAMsA/vr.php -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Change in failures.nas
On Sunday 25 March 2012 05:20:03 ThorstenB wrote: Am 25.03.2012 00:46, schrieb Eugenio Mondini: I'd like to understand something that seems to affect only me. As you can see in the forum [0] after a recent fgdata update I couldn't use one plane because it checked against a property in failure-manager part of the tree, that was not appering for me. Once I understood more or less what was happening I reverted a part of the commit [1] only in the failures.nas file and it worked again. Oops, there was another change in my commit that wasn't supposed to be pushed. I somehow missed that. Try latest fgdata and see if it's back to normal now. The issue should have affected all aircraft using the failure module. Works perfect again, now. Sorry for the delay but I had network troubles. Thanks for your help. Thanks for reporting. cheers, Thorsten Thanks, Eugenio. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Change in failures.nas
Hi everyone. Thanks for the awesome sim you all make.
I'd like to understand something that seems to affect only me.
As you can see in the forum [0] after a recent fgdata update I couldn't use
one plane because it checked against a property in failure-manager part of the
tree, that was not appering for me. Once I understood more or less what was
happening I reverted a part of the commit [1] only in the failures.nas file
and it worked again.
This is what I reverted manually in my install:
--
diff --git a/Nasal/failures.nas b/Nasal/failures.nas
index ccf6f79..23cb738 100644
--- a/Nasal/failures.nas
+++ b/Nasal/failures.nas
@@ -177,12 +177,12 @@ var setAllMCBF = func(mcbf) {
}
}
-
# Initialization, called once Nasal and the FDM are loaded properly.
-_setlistener(/sim/signals/fdm-initialized, func {
+var fdm_init_listener = _setlistener(/sim/signals/fdm-initialized-once,
func {
+removelistener(fdm_init_listener); # uninstall, so we're only called once
srand();
-# Engines are added dynamically because there may be an arbritary number
+# Engines are added dynamically because there may be an arbitrary number
var i = 1;
foreach (var e; props.globals.getNode(/engines).getChildren(engine))
{
breakHash[e.getPath()] = { type: type.MTBF, failure: fail.ENGINE,
desc : Engine ~ i };
--
What could be the problem?
Thanks, Eugenio.
[0]
http://www.flightgear.org/forums/viewtopic.php?f=4t=13296p=153965#p153945
[1]
https://gitorious.org/fg/fgdata/commit/f1e4c6503643587a933e742fcfc15cb5af127802
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
