Give us an idea of what you working on.
Thanks
Alan.
Keep up the good work!
WHAT ARE YOU WORKING ON MICHEAL - Let us know!!
16 posts
• Page 1 of 2 • 1, 2
by Robsony » Mon Mar 17, 2003 4:26 pm
Lots of usefull ideas are coming out of these discussion boards. But as yet we have no feedback from the developers as to what is being developed!!!!
Give us an idea of what you working on.
Thanks
Alan.
Keep up the good work!
Give us an idea of what you working on.
Thanks
Alan.
Keep up the good work!
- Robsony
- Posts: 1
- Joined: Mon Mar 17, 2003 4:24 pm
by Michael_Moeller » Wed Mar 19, 2003 10:16 am
here a short list of what we are working on at the moment:
completely new graphic engine with Direct3D IM (DirectX 9.0), hopefully we can solve this way the following things:
-> no more problems with newer graphics cards as the ATI Radeons
-> open the way for multiplayer version (drawing more than one model, compact and hashable model-file format, that means just one file)
-> nicer graphic effects like environment mapping for the models (to have metal-like surfaces that reflect), a particle engine to add smoke, ... and there are many ideas around what could be added beside this: bump mapped water (pixel shader), shoft edged shadows, shadow volume (self shadowing of the models)
-> new landscape file-format: support for .x files (or similar)
-> skybox: for real sky texturing (with the sun and all)
a completely new simulation engine for the airplanes:
-> a real ground simulation, though that it is possible to train landings
-> better stalling effects, etc to be able to fly more acrobatics
-> opening the possibility to add some real wind with turbulence (this is not possible with the flight model used in 2.0 Beta 7)
-> with a new engine model is should be possible to have a more realistic thrust generation ...
many smaller details like a new camera moving engine, to have a better view on the runway etc.
you see the list is long (and I must have forgotten the one or other thing ...), and there are still missing some larger parts of code ... thoug it will still take a while before we can put all together once more, into a new release ...
Michael Möller
completely new graphic engine with Direct3D IM (DirectX 9.0), hopefully we can solve this way the following things:
-> no more problems with newer graphics cards as the ATI Radeons
-> open the way for multiplayer version (drawing more than one model, compact and hashable model-file format, that means just one file)
-> nicer graphic effects like environment mapping for the models (to have metal-like surfaces that reflect), a particle engine to add smoke, ... and there are many ideas around what could be added beside this: bump mapped water (pixel shader), shoft edged shadows, shadow volume (self shadowing of the models)
-> new landscape file-format: support for .x files (or similar)
-> skybox: for real sky texturing (with the sun and all)
a completely new simulation engine for the airplanes:
-> a real ground simulation, though that it is possible to train landings
-> better stalling effects, etc to be able to fly more acrobatics
-> opening the possibility to add some real wind with turbulence (this is not possible with the flight model used in 2.0 Beta 7)
-> with a new engine model is should be possible to have a more realistic thrust generation ...
many smaller details like a new camera moving engine, to have a better view on the runway etc.
you see the list is long (and I must have forgotten the one or other thing ...), and there are still missing some larger parts of code ... thoug it will still take a while before we can put all together once more, into a new release ...
Michael Möller
- Michael_Moeller
- Posts: 88
- Joined: Thu Feb 28, 2002 10:38 am
by Norbert » Mon Mar 31, 2003 8:05 pm
Hello Michael!
Robsony made a very good question. Since loading your latest alpha version FMS_A.7.5.1 - which contained only a few changes - obviously was created in february 2002. So I am impatiently waiting for further releases which perhaps finally would fulfill my special (?) expectations.
I am very enjoyed that you decided to continue developping under Direct3D (instaed of OpenGL) because OpenGL does not run with my graphic card. Since Microsoft did its great flightsimulator also with Direct3D, it MUST be possible to develop another good simulator without OpenGL (even if some other programmer may say, Direct3D is a bad platform). Thanks for this decision.
I do not have any problems with the graphic performance. I do not conditionally need a smoke trace or similar trifels, which probably may cost a lot of calculation power, in relation to its use. I am very pleased with all details of landscape, sky and models, because these things are not so important when training or optimizing self-constructed models as I do.
In contrary, I find it much more important to improve the aerodynamic behavior of the models under FMS to fly finally as realistic as in reality. Until now, under FMS this expectation is not fullfilled. In the following I listed some of those weak points which I think they have to be improved urgently.
1. Running the model on the ground:
1.1
Problem with starting low powered models:
Until now there is a great discontinuity of behavior between running the model on the ground and free flying, especially with light and low-powered models: when starting, the model "sticks" to the ground although it may have enough speed. In this situation slowly pulling the elevator will only lower the tail but instantly reduce speed (perhaps below minimum speed to fly), but will not lift off (even if the model would fly at the same speed with lower power, once it is in the air). Only fast, strong (and short) pulling of the elevator can "tear up" the model from ground - but this is not a realistic way to start from a smooth runway (where ground effect even will help to lift off)!
1.2
Steering with the rudder on the ground:
Steering the model on the ground is still hardly possible. Especially with a slowly rolling model (where aerodynamic forces are nearly zero and inertia forces are still low) it should be possible to move the model just like a car. It should move just as if a wheel is mounted under the rudder (or under the bow) and steered with the same angle as the rudder. At higher speeds this slowly should change into the normal aerodynamic behavior, calculated from aerodynamic forces, inertia und the rest of lateral friction between wheels and ground. It should be regarded that in most cases the angle of the rudder-mounted wheel is much higher than the effective rudder-angle calculated from the .par-file, because in most cases rudder is combined with a fixed damping area.
By the way, in the air a model with an actuated rudder will not only slide (put the nose a little bit to one side - but continue flying into the same direction as before) as it is implemented under FMS until now. The model REALLY will slowly bank (change the course), even without any coupling across the V-form-Faktor (in the .par-file). This is a consequence of the angle between the fuselage's side-areas and the rudder which forms a vaulted profile and causes some "torque coefficient".
1.3
Different friction coefficients depending on the kind of ground surface:
On the smooth surface of a runway there should be only low frontal friction (but fully lateral, to enable steering on the ground as mentioned before). In contrast to this, on all green ground surfaces, frontal friction should be higher and lateral friction should be lower (because wheels normally are jumping over the grass). On water only models with floats should be able to land (what about to let slowly sink any other models?). Landing on ice or snow should be followed by crash with any model without skids.
1.4 Different speed limits on different ground surfaces:
Until now there is a speed limit when running the model on the ground. Instead of this I would like to have different speed limits depending on the kind of surface (especially on the runway it should be possible to run with unlimited speed to train touch & go; only vertical speed should lead to crash, if exceeded). Speed on other surfaces should be limited, perhaps to a constant factor above minimum speed, which can be easyly calculated from weight, wing area and maximum lift-coefficient.
2. Improvements in aerodynamic behavior:
2.1
Reaction of tail unit only statically caculated?
I have the impression that the reaction of rudder, elevator or aileron is only a function of the primary angle of attack (before starting rotation) and not calculated under dynamic conditions. When any rudder surface is turned against the actual air-stream, at first it causes a force, depending on speed, surface area and angle of attack. This force works against the inertia of the actual axis and then starts to accelerate the model around this axis. But as soon as this rotation starts, the effective angle of attack to the rudder is reduced because of the rotating speed and therefore a new resulting force must be calculated, and so on.
Now it seems to me, that within FMS this continued calculation (depending on the actual rotating speed) is not implemented. Otherwise I cannot explain some very strange behaviors when "playing" with coefficients in the .par-file. For instance, with a very strong engine it is easy to produce loops which are very much tighter than they physically could be, limited by the angle between wings and elevator and the distance between them (this construction describes a circle with the minimum diameter, which never could be tighter; any inertia force only could widen the resultant loops). Nevertheless, under FMS I had models with looping circles smaller than the models themselves - they could rotate around the wing's axis as if the wingtips are put in a bearing!
2.2
Flying on knife's edge (Messerflug):
Once, I read in this forum, flying on knife's edge could be performed by hanging the model onto the propeller and using a very strong engine (adjusted within the .par-file). I find, this is not a realistic simulation. In reality when banking at high speed there is a lot of lift by the fuselage's side surface, used to keep the model in the air without hanging on a propeller. Under FMS, it should be calculated in this way, too.
2.3
Rudder and elevator reaction with regard to the propeller's beam:
Although I am not a friend of extreme acrobatics, e.g. torque rolls, I think, they should be possible, too. Is it only my awkwardness or is it simply impossible to perform torque rolls under FMS? For me it seems that rudder and elevator are not functioning at all as soon as the model's speed becomes nearly zero (as it is normal when hovering under the propeller). Not only therefore the simulator should always calculate with the real speed of the propeller's beam (instead of a simple thrust). In reality great differences in reaction to rudder and elevator can exist depending on the engine's actual power. This generally should be implemented under FMS (and torque roll will run, too). The engine's torque (power, devided by the engine's speed) and the damping area of the wings can be used to calculate the rotating speed at torque roll and the small torque around the length axis at normal fligth.
2.4
Using real propeller's jet data instead of simple thrust:
In reality the propeller's thrust is not a constant force as it is written in the .par-file! Somewhat simplyfied (and normally with a propeller which has a gradient not too high), the function looks like a negative square function with maximum thrust at zero speed and zero thrust at its "jet speed" (which can be calculated from the propeller's gradient and its rotation speed). Similar to this under FMS the thrust for all propeller models at least should be calculated depending on the actual model-speed. This would help optimizing the propeller dimensions for a real existing model. Even with jet-enginges it would be useful to calculate thrust from the difference between jet-speed (which is not unlimited) and the model's speed. The calculation should be done from the actual engine's speed which results in lower jet-speeds when the engine's power is reduced.
3. Pilot's view?
Sometimes, I wish to sit within the model (oh no - I only wish to have the pilot's view
). This can have some advantages against simple following the model, especially within loops (where the graphic sometimes is confusing) and tight turns (where the graphic simply is too slow). Therefore this is not only an important "fun-option" to me.
4. Repeat function and free setting of any start-situation?
Sometimes it is useful to repeat the last seconds (up to 60) of the simulation and - perhaps - during this stop repeating and continuing with normal flight. Additionally I would like to have free and easy programmable start situations (Model speed, direction, height and pilot's position) as this is implemented in Microsoft's flight simulator. Is this possible?
Dear Michael, I would enjoy if you work on some of these points, too, and give us a positive answer.
And thanks to you for all the good work with FMS you have done for us until now!
Best regards,
Norbert Graubner
Robsony made a very good question. Since loading your latest alpha version FMS_A.7.5.1 - which contained only a few changes - obviously was created in february 2002. So I am impatiently waiting for further releases which perhaps finally would fulfill my special (?) expectations.
I am very enjoyed that you decided to continue developping under Direct3D (instaed of OpenGL) because OpenGL does not run with my graphic card. Since Microsoft did its great flightsimulator also with Direct3D, it MUST be possible to develop another good simulator without OpenGL (even if some other programmer may say, Direct3D is a bad platform). Thanks for this decision.
I do not have any problems with the graphic performance. I do not conditionally need a smoke trace or similar trifels, which probably may cost a lot of calculation power, in relation to its use. I am very pleased with all details of landscape, sky and models, because these things are not so important when training or optimizing self-constructed models as I do.
In contrary, I find it much more important to improve the aerodynamic behavior of the models under FMS to fly finally as realistic as in reality. Until now, under FMS this expectation is not fullfilled. In the following I listed some of those weak points which I think they have to be improved urgently.
1. Running the model on the ground:
1.1
Problem with starting low powered models:
Until now there is a great discontinuity of behavior between running the model on the ground and free flying, especially with light and low-powered models: when starting, the model "sticks" to the ground although it may have enough speed. In this situation slowly pulling the elevator will only lower the tail but instantly reduce speed (perhaps below minimum speed to fly), but will not lift off (even if the model would fly at the same speed with lower power, once it is in the air). Only fast, strong (and short) pulling of the elevator can "tear up" the model from ground - but this is not a realistic way to start from a smooth runway (where ground effect even will help to lift off)!
1.2
Steering with the rudder on the ground:
Steering the model on the ground is still hardly possible. Especially with a slowly rolling model (where aerodynamic forces are nearly zero and inertia forces are still low) it should be possible to move the model just like a car. It should move just as if a wheel is mounted under the rudder (or under the bow) and steered with the same angle as the rudder. At higher speeds this slowly should change into the normal aerodynamic behavior, calculated from aerodynamic forces, inertia und the rest of lateral friction between wheels and ground. It should be regarded that in most cases the angle of the rudder-mounted wheel is much higher than the effective rudder-angle calculated from the .par-file, because in most cases rudder is combined with a fixed damping area.
By the way, in the air a model with an actuated rudder will not only slide (put the nose a little bit to one side - but continue flying into the same direction as before) as it is implemented under FMS until now. The model REALLY will slowly bank (change the course), even without any coupling across the V-form-Faktor (in the .par-file). This is a consequence of the angle between the fuselage's side-areas and the rudder which forms a vaulted profile and causes some "torque coefficient".
1.3
Different friction coefficients depending on the kind of ground surface:
On the smooth surface of a runway there should be only low frontal friction (but fully lateral, to enable steering on the ground as mentioned before). In contrast to this, on all green ground surfaces, frontal friction should be higher and lateral friction should be lower (because wheels normally are jumping over the grass). On water only models with floats should be able to land (what about to let slowly sink any other models?). Landing on ice or snow should be followed by crash with any model without skids.
1.4 Different speed limits on different ground surfaces:
Until now there is a speed limit when running the model on the ground. Instead of this I would like to have different speed limits depending on the kind of surface (especially on the runway it should be possible to run with unlimited speed to train touch & go; only vertical speed should lead to crash, if exceeded). Speed on other surfaces should be limited, perhaps to a constant factor above minimum speed, which can be easyly calculated from weight, wing area and maximum lift-coefficient.
2. Improvements in aerodynamic behavior:
2.1
Reaction of tail unit only statically caculated?
I have the impression that the reaction of rudder, elevator or aileron is only a function of the primary angle of attack (before starting rotation) and not calculated under dynamic conditions. When any rudder surface is turned against the actual air-stream, at first it causes a force, depending on speed, surface area and angle of attack. This force works against the inertia of the actual axis and then starts to accelerate the model around this axis. But as soon as this rotation starts, the effective angle of attack to the rudder is reduced because of the rotating speed and therefore a new resulting force must be calculated, and so on.
Now it seems to me, that within FMS this continued calculation (depending on the actual rotating speed) is not implemented. Otherwise I cannot explain some very strange behaviors when "playing" with coefficients in the .par-file. For instance, with a very strong engine it is easy to produce loops which are very much tighter than they physically could be, limited by the angle between wings and elevator and the distance between them (this construction describes a circle with the minimum diameter, which never could be tighter; any inertia force only could widen the resultant loops). Nevertheless, under FMS I had models with looping circles smaller than the models themselves - they could rotate around the wing's axis as if the wingtips are put in a bearing!
2.2
Flying on knife's edge (Messerflug):
Once, I read in this forum, flying on knife's edge could be performed by hanging the model onto the propeller and using a very strong engine (adjusted within the .par-file). I find, this is not a realistic simulation. In reality when banking at high speed there is a lot of lift by the fuselage's side surface, used to keep the model in the air without hanging on a propeller. Under FMS, it should be calculated in this way, too.
2.3
Rudder and elevator reaction with regard to the propeller's beam:
Although I am not a friend of extreme acrobatics, e.g. torque rolls, I think, they should be possible, too. Is it only my awkwardness or is it simply impossible to perform torque rolls under FMS? For me it seems that rudder and elevator are not functioning at all as soon as the model's speed becomes nearly zero (as it is normal when hovering under the propeller). Not only therefore the simulator should always calculate with the real speed of the propeller's beam (instead of a simple thrust). In reality great differences in reaction to rudder and elevator can exist depending on the engine's actual power. This generally should be implemented under FMS (and torque roll will run, too). The engine's torque (power, devided by the engine's speed) and the damping area of the wings can be used to calculate the rotating speed at torque roll and the small torque around the length axis at normal fligth.
2.4
Using real propeller's jet data instead of simple thrust:
In reality the propeller's thrust is not a constant force as it is written in the .par-file! Somewhat simplyfied (and normally with a propeller which has a gradient not too high), the function looks like a negative square function with maximum thrust at zero speed and zero thrust at its "jet speed" (which can be calculated from the propeller's gradient and its rotation speed). Similar to this under FMS the thrust for all propeller models at least should be calculated depending on the actual model-speed. This would help optimizing the propeller dimensions for a real existing model. Even with jet-enginges it would be useful to calculate thrust from the difference between jet-speed (which is not unlimited) and the model's speed. The calculation should be done from the actual engine's speed which results in lower jet-speeds when the engine's power is reduced.
3. Pilot's view?
Sometimes, I wish to sit within the model (oh no - I only wish to have the pilot's view
). This can have some advantages against simple following the model, especially within loops (where the graphic sometimes is confusing) and tight turns (where the graphic simply is too slow). Therefore this is not only an important "fun-option" to me.
4. Repeat function and free setting of any start-situation?
Sometimes it is useful to repeat the last seconds (up to 60) of the simulation and - perhaps - during this stop repeating and continuing with normal flight. Additionally I would like to have free and easy programmable start situations (Model speed, direction, height and pilot's position) as this is implemented in Microsoft's flight simulator. Is this possible?
Dear Michael, I would enjoy if you work on some of these points, too, and give us a positive answer.
And thanks to you for all the good work with FMS you have done for us until now!
Best regards,
Norbert Graubner
Norbert Graubner[br]Im Kalkofen 9[br]D-55268 Nieder-Olm
- Norbert
- Posts: 12
- Joined: Wed Sep 05, 2001 12:08 pm
- Location: Nieder-Olm, Germany
by Roman Moeller » Wed Apr 02, 2003 10:08 am
Hello Norbert,
as I'm working on the simulation part of FMS, I will give some details of the new simulation routine. The simulation was completely rewriten and is not a expansion of the old simulation. Therefore, the parameter file is completely different (and much longer).
Remarks to the points mentioned above:
1.1
The new simulation uses "drag points" and wheels, which define the geometry of the physical model. The intersection of these points with the world-geometry is calculated and a spring-damping model (Feder-Dämpfer-Modell) is applied. So the model "stands" on its real wheels and can no longer dive into the ground.
1.2
Steering on the ground is now possible. A channel can be applied to each wheel.
1.3
This point is not yet implemented, because it is not easy to add a "friction coefficient texture" to the world geometry.
1.4
A Speedlimit is no loner needed. Now a crash is calculated based on the force acting on the wheels and drag points. If you touch the ground soft enough the model will not crash. But I have to say that landing without crashing the model is now more difficult than before.
2.1
The aerodynamic model is now based on wing-elements which can be added to the model (Rudder and elevator are also wing-elements now), but still static, which means that they have no dynamic in the sence of a differential equation. On each wing-element a lift and drag polar is applied. The angle of attack is calculated including rotational effects, downwash from an other wing-element and increased speed of a propeller.
2.3
Is done.
2.4
Now the thrust is depending on the flight speed, and simple propeller geometry (diameter, pitch and chordlength). Here I used a simple formula, but maybe I will improve that point.
3
Maybe I will add that.
4
Maybe I will add that.
Best regards,
Roman Möller
as I'm working on the simulation part of FMS, I will give some details of the new simulation routine. The simulation was completely rewriten and is not a expansion of the old simulation. Therefore, the parameter file is completely different (and much longer).
Remarks to the points mentioned above:
1.1
The new simulation uses "drag points" and wheels, which define the geometry of the physical model. The intersection of these points with the world-geometry is calculated and a spring-damping model (Feder-Dämpfer-Modell) is applied. So the model "stands" on its real wheels and can no longer dive into the ground.
1.2
Steering on the ground is now possible. A channel can be applied to each wheel.
1.3
This point is not yet implemented, because it is not easy to add a "friction coefficient texture" to the world geometry.
1.4
A Speedlimit is no loner needed. Now a crash is calculated based on the force acting on the wheels and drag points. If you touch the ground soft enough the model will not crash. But I have to say that landing without crashing the model is now more difficult than before.
2.1
The aerodynamic model is now based on wing-elements which can be added to the model (Rudder and elevator are also wing-elements now), but still static, which means that they have no dynamic in the sence of a differential equation. On each wing-element a lift and drag polar is applied. The angle of attack is calculated including rotational effects, downwash from an other wing-element and increased speed of a propeller.
2.3
Is done.
2.4
Now the thrust is depending on the flight speed, and simple propeller geometry (diameter, pitch and chordlength). Here I used a simple formula, but maybe I will improve that point.
3
Maybe I will add that.
4
Maybe I will add that.
Best regards,
Roman Möller
- Roman Moeller
- Site Admin
- Posts: 40
- Joined: Tue Jan 09, 2001 3:51 pm
by Norbert » Wed Apr 02, 2003 3:33 pm
Hello Roman,
thanks a lot for all points you mentioned. This would fulfill most of my expectations. So I am waiting impatiently and with much anticipated joy for the next release.
Best regards
Norbert
thanks a lot for all points you mentioned. This would fulfill most of my expectations. So I am waiting impatiently and with much anticipated joy for the next release.
Best regards
Norbert
- Norbert
- Posts: 12
- Joined: Wed Sep 05, 2001 12:08 pm
- Location: Nieder-Olm, Germany
by steve5006 » Tue Apr 08, 2003 12:14 am
I had a few suggestions for new things to add
--> Retracts because I have a few models that I added that the makers made two models one with the gear down and the other with it up
--> Flaps- They'd make landings easier
--> Tail draggers- maybe they could actually drag their tails when they're going slow instead of having them up full time
--> Retracts because I have a few models that I added that the makers made two models one with the gear down and the other with it up
--> Flaps- They'd make landings easier
--> Tail draggers- maybe they could actually drag their tails when they're going slow instead of having them up full time
- steve5006
- Posts: 2
- Joined: Fri Mar 28, 2003 2:27 am
by fmsiscool123 » Wed May 07, 2003 7:41 pm
we need
more realistic engine sounds
da 150
electric etc
and tyhe stall effect needs to be nulled when hovering vertically
more realistic engine sounds
da 150
electric etc
and tyhe stall effect needs to be nulled when hovering vertically
- fmsiscool123
- Posts: 3
- Joined: Tue May 06, 2003 9:23 pm
by Chris Stoddart » Thu May 08, 2003 1:24 pm
The list of additions coming in the next version of FMS is exciting.
May I add a request? I would like to be able drive the controls (throttle, elevator, ailerons, rudder) from a script file/program which "reads" the time from a clock in the simulation. The purpose of this is to use FMS to simulate free flight models such as class F1A/F1B/F1C. The scripting could be hosted using the Windows Script Host. I have seen and use a non-model airplane related application written in Delphi that implements scripting this way.
If scripting is added it might also be possible to simulate automatic guidance systems is the appropriate parameters are made available to be read.
Thanks,
Chris Stoddart
May I add a request? I would like to be able drive the controls (throttle, elevator, ailerons, rudder) from a script file/program which "reads" the time from a clock in the simulation. The purpose of this is to use FMS to simulate free flight models such as class F1A/F1B/F1C. The scripting could be hosted using the Windows Script Host. I have seen and use a non-model airplane related application written in Delphi that implements scripting this way.
If scripting is added it might also be possible to simulate automatic guidance systems is the appropriate parameters are made available to be read.
Thanks,
Chris Stoddart
- Chris Stoddart
- Posts: 19
- Joined: Mon Aug 13, 2001 12:15 pm
by snafu » Fri May 23, 2003 7:45 pm
Basically what everyone else said and I want it now.
Seriously, a nice list of enhancements you have there, can't wait. In addition to the request for retracts & flaps etc are animated control surfaces planned?
Also probably getting into the realms of check back in a few years but..... the ability to "spawn" objects from the main model with there own characteristics such as Rockets & Bombs would be awesome.
Fantasic product, looking forward to the next release.
TTFN
snafu
Seriously, a nice list of enhancements you have there, can't wait. In addition to the request for retracts & flaps etc are animated control surfaces planned?
Also probably getting into the realms of check back in a few years but..... the ability to "spawn" objects from the main model with there own characteristics such as Rockets & Bombs would be awesome.
Fantasic product, looking forward to the next release.
TTFN
snafu
When the only thing left on the altimeter is the makers name You know your in trouble
- snafu
- Posts: 13
- Joined: Wed Nov 27, 2002 12:03 am
by Sturdy Birdy 10 » Thu Jun 26, 2003 9:23 pm
Hi
Michael I have some ideas for you. How about if you make an add on for FMS. This add on should be a controller on the screen when you move a trimmer or a the joy stick on the controller and the controller shows the move you did on the screen. Also make that controller teach you how to fly by giving you lessons. You should also make the program more realistic. for example in real rc flying you have to put gas in the plane. so if you do this for fms make the person put gas in the plane.
Sturdy Birdy 10
Michael I have some ideas for you. How about if you make an add on for FMS. This add on should be a controller on the screen when you move a trimmer or a the joy stick on the controller and the controller shows the move you did on the screen. Also make that controller teach you how to fly by giving you lessons. You should also make the program more realistic. for example in real rc flying you have to put gas in the plane. so if you do this for fms make the person put gas in the plane.
Sturdy Birdy 10
- Sturdy Birdy 10
- Posts: 40
- Joined: Sat Jun 14, 2003 11:02 am
by dieter » Sat Jul 05, 2003 9:54 pm
i know thats not the question you want to hear, but i think many people are thinking about that (please don't be angry):
will the new fms be free ??? ?
sorry, but making planes for real flying is expensive enough and so i'm really happy, that it is free.
so a big thanks to all, who are working on fms!!!!! and i hope it will be free in future.
will the new fms be free ??? ?
sorry, but making planes for real flying is expensive enough and so i'm really happy, that it is free.
so a big thanks to all, who are working on fms!!!!! and i hope it will be free in future.
- dieter
- Posts: 4
- Joined: Mon Jun 16, 2003 10:26 am
by overhead » Mon Jul 07, 2003 10:47 pm
Hi.
I have been practicing my heli flying using FMS and I really like the image and feel. What the heli flyers really need is a heading hold gyro feature. Most all pilots these days are using them. The types of maneuvers being done these days requires a heading hold gyro. Sure hope you will be adding this function in the new version.
Just a freindly note.
Dennis
I have been practicing my heli flying using FMS and I really like the image and feel. What the heli flyers really need is a heading hold gyro feature. Most all pilots these days are using them. The types of maneuvers being done these days requires a heading hold gyro. Sure hope you will be adding this function in the new version.
Just a freindly note.
Dennis
Dennis
- overhead
- Posts: 55
- Joined: Wed Apr 17, 2002 12:49 am
- Location: Winnipeg, Manitoba, CANADA
16 posts
• Page 1 of 2 • 1, 2
Who is online
Users browsing this forum: No registered users and 40 guests