BAe Panel Project Forum
»
Panel Support Forum
»
Jetstream 41 Board
»
Which parts is the most difficult in J41 Panel Development?
Themen-Einstellungen 
Thema abonnieren
Thema drucken
11.02.2008 23:37
|
|
Dear Sir,
Recently, I just call a old friend, he is a progammer and have his own company, I already ask his company to help me renew my J41 panel to match FSX. Actually, they didn't have experience on FS panel guages, usually they work project for office only but aure they know XLM and C++ code, I wish they could help! I think I ask them to modifly the FSX original XML file to become J41 panel guages, do you think it is good idea? But some people say that: 1) There's no security in XML, everyone else can easily see your gauge code, and can copy it. 2) There's nothing you can do in XML that can't also be done in C++. Where there are many things you can do in C++ not possible in XML. 3) C++ code because its compiled will generally be faster, whereas XML is processed by an interpreter at run-time which is a little slower. Though probably not so much slower most would notice, unless you got real complicated and detailed. As I know, the trubo-propeller engine power gauges, there are no any simple from MS FS, we should develope by ourself. I think most difficult of J41 are 4 gauges: - Engine power computer output with different temperature, - Auto Speed ISA , - Intergrated RPM with Mixture Lever - Warning_Panel What do you think? Thanks Gordon |
antworten
|
|
Hello Gordon,
"I think I ask them to modifly the FSX original XML file to become J41 panel guages, do you think it is good idea?" You could use the standard XML gauges as a base for the own programmed gauges. This makes the work much faster and gives you a lot of experience in programming gauges. "1) There's no security in XML, everyone else can easily see your gauge code, and can copy it." This is correct. There's no way to lock a XML gauge that it could not be altered or copied from others. "2) There's nothing you can do in XML that can't also be done in C++. Where there are many things you can do in C++ not possible in XML. There are just two things you could not do with XML gauges. The first thing is to implement sounds into gauges without using a C gauge. The second thing is that you could not write to ini files or read from ini files. This could be important when you want to program a FMS. "3) C++ code because its compiled will generally be faster, whereas XML is processed by an interpreter at run-time which is a little slower. Though probably not so much slower most would notice, unless you got real complicated and detailed." With a good and fast fast XML code you will not find any difference to C gauges regarding the speed. "Engine power computer output with different temperature," Yes, this is not easy to do. However FSX offers the way to control N1 with thrust. This makes it a bit easier. "Auto Speed ISA" It's not complicate but you need very much testflights and a lot of gauge reworks until you find the correct settings in the code. Take care about the aircraft weight which has a big effect on the necessary pitch. "Intergrated RPM with Mixture Lever" I think this is really the most complicated part. In three years I didn't find a way to realize it. Also I don't find a free- or payware aircraft which simulates a realistic single shaft TP engine. "Warning_Panel" This is no problem. A warning panel just scans given variables and so it's easy to do. Looking forward to your new work. Best Regards Matthias |
|
|
Dear Matthias,
Thank you so much for your kindly reply, your answer let me much understand my case! The bad new is my friend's company reply me, they are not used to XML and even C++, they are not in the Game field, they used to ASP for office only! I will try to looking for the other game progammer, may be post in some FS developer forum. Gordon Lee |