David 05.10.2024 18:53:49

 Makes perfect sense 

 My pleasure is in the challenge of doing the best I can given the constraints of a lfight...no matter what the task, weather, or plane might be. That may sound non-committal, but I don't mind the current rules and the way VS24 has been managed. As you know, my multi-player availability is a bit variable and the once per month is more likely for me...but I'm only one! It is definitely hard to find a reasonable time for all when you are crossing many time zones!

I had forgotten about our "Out" tasks, thank you for the reminder! I agree, not good, or recommended, for multi-player. If we would use similar time/scoring rules for "Out" tasks that we have now for the "usual" tasks, we would just need to fly fast to score our best since overtime is not penalized heavily. But maybe we forget the "Out" task because of the difficulty in making rules for it...we like to keep it simple, don't we? Isn't that why we are vintage flyers? ;-) 

Thank you both for your feedback. Good that you both like OneDesign, then we will continue with it. The suggested planes are worth to take. I think it should be usually not often used planes, because they aren't really competitive. Baby, K8 and Libelle matching good, Ka6 is (one of) the best in it's category, I like it very good, but I wouldn't take it for the OneDesign. If we hope to get more pilots with the OneDesign I think we should take a free plane. I hoped we could get someone with the SGS1-26. It wasn't the case, but it was and still is fun nevertheless. So my suggested plane for next year is only 20 years old, much younger than a Vintage glider, and not in a category this year: Diana 2. What is your opinion about using that plane? Not really a vintage plane but flying in vintage style without pda. Of course I will accept a no.

To the distance task. I like it too. We have had two such task types before, "Free" and "Out". I disabled them because on multi player it's better to have a task type with a defined final airport for the virtual barbecue. I would like to reactivate "Out", but have to think about the rules. With two different tasks each month (OneDesign and the "usual") we can use the task with the defined final for multiplayer, while the other task is an Out task. The other reason for the disabling was the landing method. I didn't liked the way we flew before with no time for a nice landing. The end of the flight of the new "Out" could be the last point, when you are minimum 200 m over the height of the landing point, that means if you are below 200 m without climbing again, your flight is over and you have time, space and height enough for a good landing. Time calculation like AAT as in all other tasks. I think it's a good rule, but it will work only in flat land. If you land on an airport on a ridge and you flew along the ridge not higher than 200 m over the landing airport, you get no distance. But on the other side, I wouldn't make an "Out" task in the mountains or with mountain weather, so it will be no problem.

Multi player more often sounds good, but I'm sorry for not being able to do that. I really like the multi player flights, but it influences my real life. So dinner has to be done in time and some other of those things always are to do has to be finished, so we are getting a little bit stressed that day at home. It's really ok one time in a month, but not more often. I can think of an other multi player flight maybe in a good American time, but I only can host the server and the radio. It will be frustrating if it's not running and you don't get me out of the bed to fix it.

About the task with the specified turn points I'm thinking some times, but haven't come to a good rule until now. If we take a classic Condor task you have a start gate and the waiting time until the gate is open. Advantage is you get a signal if you did a correct picture of the turn points. I don't like that waiting time. Without that waiting time you don't get the signal, and I don't like a flight with a missing turn point. Flying a fantastic triangle but missing tp1 by a few meters is not really good. A solution could be turn point helpers with a low turn point helpers range (minimum over 0 is1 km). If you see the turn point helper, the turn point is accepted. The rule will be then that you have to be in a circle around the turn point with a radius of 1 km for to get the turn point accepted. Hm, but turn point helpers I didn't like either. Maybe one day I find a solution for that.

So far my thoughts, let's discuss about it

I also like OneDesign.

On task types...I believe the currently defined tasks types provide a good variety and allow for creativity in flights. The only task type I can think to add is a predefined racing task, which would have specified turnpoints and could either have a return to the takeoff point or end at a specified target location. I know the distance task was removed from competition as it was hard on crews and pilots because of long-distance retrieves...but in Condor, maybe a straight out "go as far as you can in 90 minutes" type of task might be something to try.

I also continue thinking about other suggestions, but you have done a great job with the evolution to VS24 this year, thank you!

Thinking about ways to attract more pilots. Also maybe multi player more often.

 Still thinking

I'm thinking about next season. Are there any suggestions or wishes?

Is the OneDesign worth to continue? 

What about the fixed task, is it interesting to use it for all categories or is the current rule with the free choice of the place better?

Any ideas about new task types?

Ideas to use of ballast, maybe to define in tasks, that f.x. ballast is allowed in Cirrus or not allowed in LS3? 

Or best to keep it like it is? I'm open and thankful for every idea or comment