[WISHLIST] for further C3 updates

[alexlee]

Hi,

After the wishlist for C3 disappeared after release I would like to start a new one. It follows the intention to give the developers some ideas.

Improvements I would like to see:

- Aerotow: Create TWO startlines so TWO planes can take of side by side at the same time -> this is also competition standard

- Aerotow: Towplanes don't go to the parking position, they go right ahead to the next glider and continue towing.

- Multiplayer: Give the oppertunity to remove jointime -> people can join a race in freeflight mode after the time window for the race has been started

- Ridge lift: Give it a little bit more power

- Performace: Get access to full video ram / 64 Bit

- Gliders: Upgrade JS3 and further modern planes with the option for selflaunch or substainer.

- Weather: Reduce lightning / Give the option to overcast

[JLN]

It would be interesting to have in the flight analysis penalty points detailed by origin.

[arneh]

- Ridge lift: Give it a little bit more power

A lot of good suggestions, but I don't agree with this one. Ridge lift is finally much more realistic in Condor 3, don't want to go back to the unrealistic strong ridge lift in Condor 2!

[Bre901]

A lot of good suggestions, but I don't agree with this one. Ridge lift is finally much more realistic in Condor 3, don't want to go back to the unrealistic strong ridge lift in Condor 2!

1000% agreed, ridge lift is fine now.
Condor2 had given very bad habits to some pilots.
But, thank goodness, flying like one should IRL is no longer a handicap

[6266]

- Aerotow: Create TWO startlines so TWO planes can take of side by side at the same time -> this is also competition standard

My 5 cent to this point:

That is easy requested but I guess that will be a huge mount of work. How should that work? Should every airport be changed that way, that a second start runway is defined? Or should it be defined in the flight plan, where this second runway is? Where is the parking and landing place for the tow planes of the second line? Take note that it will be different if it's f.x. standard class or open class. 30 m wingspan needs much more space. All these problems should be solved by the little developer group, only for to get the planes faster in the air, that means before the real fun, the flight, begins. All other developments (f.x. new planes) have to wait another year?

If that is done one day, it would be very nice, but isn't it only eye candy and really worth the dev time? A solution working immediately is to jump over the start procedure and start airborn. Of course I Iike realism too and use the tow at all my flights, but I fly alone or in little groups without waiting time.

Another suggestion to get maybe the same result with much less dev time could be to create a fast start mode. That means to keep the one start line, but jump over the process the tow plane rolling to the start position. First glider started, next tow plane is set in front of the next glider and starts immediately. If it's done that way, that in the time one glider starts today two gliders will start, you get the same result (faster start) without loosing too much realism.

[6266]

Here my wishes:

1. Control the tow plane

Two keys to change the tow direction by f.x. +/- 30 degrees on each press. After that correction the tow pilot decides the route as usual. That way you can say to the tow pilot f.x. that you don't want to fly through a mountain. If more planes get self launch possibility it's a disadvantage for those needing tow without controling it a bit

2. Bungee start

Needs 3 fields in fpl: Latitude, longitude and direction. At start the plane is set at the defined place in a mode that don't roll down the hill, start is then like a winch but only a few seconds. I'm sure all hang glider pilots will like that

3. Analog clock for the panel (low priority)

In the C3 cockpits often the animation for to look on the watch (key E by default) is not good any longer. Therefor I added the clock to my panels, it's better than pressing E, but the Grunau Baby with a digital clock is not really nice. An oldclock.c3d would be fine. But as I wrote, low priority

[alexlee]

A lot of good suggestions, but I don't agree with this one. Ridge lift is finally much more realistic in Condor 3, don't want to go back to the unrealistic strong ridge lift in Condor 2!

1000% agreed, ridge lift is fine now.
Condor2 had given very bad habits to some pilots.
But, thank goodness, flying like one should IRL is no longer a handicap

I am not talking about to go back to C2 model. But many people of our group said, it needs a little bit of a adjustment. Maybe an increase of probably 15-20%.

[alexlee]

- Aerotow: Create TWO startlines so TWO planes can take of side by side at the same time -> this is also competition standard

My 5 cent to this point:

That is easy requested but I guess that will be a huge mount of work. How should that work? Should every airport be changed that way, that a second start runway is defined? Or should it be defined in the flight plan, where this second runway is? Where is the parking and landing place for the tow planes of the second line? Take note that it will be different if it's f.x. standard class or open class. 30 m wingspan needs much more space. All these problems should be solved by the little developer group, only for to get the planes faster in the air, that means before the real fun, the flight, begins. All other developments (f.x. new planes) have to wait another year?

If that is done one day, it would be very nice, but isn't it only eye candy and really worth the dev time? A solution working immediately is to jump over the start procedure and start airborn. Of course I Iike realism too and use the tow at all my flights, but I fly alone or in little groups without waiting time.

Another suggestion to get maybe the same result with much less dev time could be to create a fast start mode. That means to keep the one start line, but jump over the process the tow plane rolling to the start position. First glider started, next tow plane is set in front of the next glider and starts immediately. If it's done that way, that in the time one glider starts today two gliders will start, you get the same result (faster start) without loosing too much realism.

Of course two start lines depends on the airfield and the wingspan. I am not a programmer so can't tell if this is hard to realize. Going over to airborne start will never be realized in MO because it's unrealistic. I was asked many times and the answer is no. And also the takeoff is fun and also some kind of challenge. The idea with two start lines came from a member of our club. This year we organized the junior qualifying in club class and standard class for the german national champion ships. Our airfield is small but we managed two start lines like we used to do in (real) Marburg Open.

[6266]

Going over to airborne start will never be realized in MO because it's unrealistic. I was asked many times and the answer is no. And also the takeoff is fun and also some kind of challenge.

I like stubborn people, because I am certainly even more so, so a big +1 from me . My point only was, to get the same result with maybe less changes. If I f.x. see at Lesce, there is space for a second start line on the grass, but the start point has to be more back for to have a longer runway. At the same time the start point on the asphalt runway has to be back too, for not to have planes starting on grass behind the waiting line on asphalt. This all to coordinate in the flight plan is for sure a bigger job. IRL you only say it has to be and it will be.

If the change has to be done in the landscapes you will wait very long until that is done, and on every new airport you will use, you have to ask the landscape creator for an update with all consequences. In my opinion this is to inflexible and I would like to have such definitions in the fpl.

Lesce.png (224.55 KiB) Viewed 1582 times

[arneh]

If the change has to be done in the landscapes you will wait very long until that is done, and on every new airport you will use, you have to ask the landscape creator for an update with all consequences. In my opinion this is to inflexible and I would like to have such definitions in the fpl.

The Landscapes already specify the dimensions of the runway, with width and length. Condor could use the entire width to have several lines if the runway is wide enough, otherwise 1 line.
It could just divide the available runway width into how many lines can fit there. Say the runway is 50m wide. Leave 10m for tow planes to land, that leaves 40m for launch lines. If you have 15m or 18m gliders you could have 3 lines in that space (with overlapping wings). Open class with EB29 you could only fit one line.
Have a 150m wide runway, like some grass runways? You could have 8 lines of EB29s. And since they can self launch too, you could have everyone up in no time Although probably with quite a few collisions on take off if everyone is self launching at the same time

[6266]

The Landscapes already specify the dimensions of the runway, with width and length. Condor could use the entire width to have several lines if the runway is wide enough, otherwise 1 line.

Lesce is defined with 60 m width, that means there could be 3 start lines, where the outer start lines will use asphalt and grass, I don't believe it's so easy, but a clear definition for the other start lines is needed

[Aquila]

Default glider settings that get saved in the fpl.

[k6chris]

Allow C3 to start straight into a FPL named in the launch command, rather than having to go through the menu structure. A must for those of use who want to use C3 in a simulator environment. Please, please, PLEASE!

[victord33]

Here are mine:

• Option to hide the pilot or set his opacity to 0 if the animations are critical to the flight model.
• Improved support for controllers (ex: the WinWing Ursa Minor works better in 4x32 mode, but some buttons are still unavailable or doubled)

[ryanto]

After the flight, in the window "flight analysis" : it would be nice if that window could be adjusted in size, and if we could zoom and move the map with the mouse.