Jump to content

Recommended Posts

Posted

Auto rudder isn't gonna save you when someone puts an R-77 up your ass.

RTX 2070 8GB | 32GB DDR4 2666 RAM | AMD Ryzen 5 3600 4.2Ghz | Asrock X570 | CH Fighterstick/Pro Throttle | TM MFDs | TrackIR 5

Posted
Auto rudder isn't gonna save you when someone puts an R-77 up your ass.

 

Bing bing bing, you just topped out on the "doesn't matter for the argument at hand but thanks for posting anyway" scale. ;)

  • Like 1

Good, fast, cheap. Choose any two.

Come let's eat grandpa!

Use punctuation, save lives!

Posted

I totally agree with David on this matter. Auto-Rudder is a great feature to help new guys get started but sould be allowed to be turned off by the server admin. That way everybody is on an even playing field.

Posted

+1 - no reason why the option can't be granted to the server host - if you are going to play on my court, I sshould have the option to set the rules... can't really complain about that can we?

ASUS Tuf Gaming Pro x570 / AMD Ryzen 7 5800X @ 3.8 / XFX Radeon 6900 XT / 64 GB DDR4 3200 

"This was not in the Manual I did not read", cried the Noob" - BMBM, WWIIOL

Posted
+1 - no reason why the option can't be granted to the server host - if you are going to play on my court, I sshould have the option to set the rules... can't really complain about that can we?

 

I believe the "if you are going to play on my court, I sshould [sic] have the option to set the rules" is called a server password. :lol:

 

But seriously, some people don't have rudder pedals or good options for controlling the rudder (see TM Warthog without pedals). Depending on how long it would take to implement, server side rules for auto rudder would probably not be worth it to anyone except those that think they will lose to someone that has it on in dogfights. I assume this is a rather small percentage. With EDGE, Nevada, and all the other projects going on right now they might be better priorities.

 

So the argument is you believe auto rudder is giving some people an advantage over manual pilots? It seems like the people that would join your server with auto rudder on would not join a server that specifically disallowed it. I'm not sure it would convince someone to change their play style specifically to join your own WWII combat server.

[sIGPIC][/sIGPIC]

Posted

well, i dont think that this is hard to do for ED.actually i think that this should be a really easy fix...

and we dont want anyone to change their playing style...BUT we want to have a fair playground.anybody who doesnt like that, doesnt have to join us, we have no problem with that.

Posted

I personaly think that it should be a server option cause us flyers who spend day, weeks trying to get coordinated get toasted by these cheaters in effect, if u dont have rudders i under stand.

487th Squadron

Section Leader

Posted
this is clearly a difficulty setting, and therefore should be an option determined by the server...

please make it, that servers have influence whether or not people are allowed to use auto rudder!

+1

"Screw you guys, i'm going home."

Posted
this is clearly a difficulty setting, and therefore should be an option determined by the server...

please make it, that servers have influence whether or not people are allowed to use auto rudder!

 

+1

  • Like 1
Posted

Groovy!

ASUS Tuf Gaming Pro x570 / AMD Ryzen 7 5800X @ 3.8 / XFX Radeon 6900 XT / 64 GB DDR4 3200 

"This was not in the Manual I did not read", cried the Noob" - BMBM, WWIIOL

  • 2 weeks later...
Posted

I'd like to see an option for limited rudder. If the user has anything mapped to rudder axis, don't allow rudder assistance. If they don't, allow limited assistance during ~1g flying.

  • 2 months later...
Posted

We are thinking about the possibility of a Online Air Race with TF-51D. It's quite urgent and important for the fairness.

 

Hope it can be done soon.

Thanks.

[sIGPIC][/sIGPIC]

Posted

^^according to Sithspawn, this is implemented now!so in theory, if you build a mission, and have the autorudder option disabled, it should be restricted on the server...in theory, i am not 100% sure about it.

Posted
^^according to Sithspawn, this is implemented now!so in theory, if you build a mission, and have the autorudder option disabled, it should be restricted on the server...in theory, i am not 100% sure about it.

 

But if the server's account don't have P-51D and FW-190D, how to force it?

[sIGPIC][/sIGPIC]

  • 3 weeks later...
Posted (edited)

Hi Everyone,

 

I don't know why the devs or the testers have not published this.

Here is the way to enforce the Special Options of all currently released modules on all clients on the server -

 

1. Create your mission, save it.

2. Go into the saved Miz file and open it with 7zip/winzip/winrar etc..

3. Export the file - options

4. Open the options file with Notepad++ or any other editor that can read and sort LUA.

5. This file is divided into 6 different option categories - difficulty,graphics,plugins,views,sound,miscellaneous.

 

file example -

 

options =

{

["difficulty"] =

{

["fuel"] = false,

["easyRadar"] = false,

["miniHUD"] = false,

["birds"] = 0,

["optionsView"] = "optview_onlymap",

["permitCrash"] = false,

["immortal"] = false,

["easyCommunication"] = false,

["cockpitVisualRM"] = false,

["easyFlight"] = false,

["radio"] = false,

["labels"] = false,

["tips"] = true,

["map"] = true,

["cockpitLanguage"] = "english",

["units"] = "imperial",

["userSnapView"] = false,

["reports"] = true,

["externalViews"] = true,

["iconsTheme"] = "nato",

["padlock"] = false,

["weapons"] = false,

["setGlobal"] = false,

["geffect"] = "realistic",

}, -- end of ["difficulty"]

["playerName"] = "New callsign",

["graphics"] =

{

["OculusRift"] = false,

["multiMonitorSetup"] = "1camera",

["color"] = "32",

["preloadRadius"] = 150000,

["heatBlr"] = 0,

["scenes"] = "medium",

["water"] = 0,

["fullScreen"] = false,

["disableAero"] = false,

["visibRange"] = "Medium",

["treesVisibility"] = 6000,

["aspect"] = 1.3333333333333,

["haze"] = 1,

["HDR"] = 0,

["TranspSSAA"] = false,

["textures"] = 2,

["cockpitShadows"] = false,

["width"] = 1024,

["effects"] = 3,

["shadowTree"] = false,

["civTraffic"] = "",

["sync"] = true,

["lights"] = 2,

["height"] = 768,

["shadows"] = 2,

["clutterMaxDistance"] = 0,

["MSAA"] = 1,

}, -- end of ["graphics"]

["plugins"] =

{

["CA"] =

{

["kompass_options"] = 1,

["ground_target_info"] = false,

["ground_aim_helper"] = false,

["ground_automatic"] = false,

["ground_platform_shake"] = false,

}, -- end of ["CA"]

["F-86F"] =

{

["landSeatAdjustF86"] = false,

}, -- end of ["F-86F"]

["FW-190D9"] =

{

["autoRudder"] = false,

}, -- end of ["FW-190D9"]

["UH-1H"] =

{

["UHRudderTrimmer"] = false,

["autoPilot"] = false,

["altUHTrimmingMethod"] = false,

["weapTooltips"] = false,

["UHTrackIRAiming"] = false,

}, -- end of ["UH-1H"]

["Ka-50"] =

{

["altTrimmingMethod"] = false,

}, -- end of ["Ka-50"]

["Mi-8MTV2"] =

{

["altMi8TrimmingMethod"] = false,

["controlHelperMi8"] = false,

["weapTooltipsMi8"] = false,

["Mi8RudderTrimmer"] = false,

}, -- end of ["Mi-8MTV2"]

["P-51D"] =

{

["assistance"] = 0,

["autoRudder"] = false,

}, -- end of ["P-51D"]

["TF-51D"] =

{

["assistance"] = 0,

}, -- end of ["TF-51D"]

}, -- end of ["plugins"]

["views"] =

{

["cockpit"] =

{

["mirrors"] = false,

["reflections"] = false,

["russianHud"] = false,

["avionics"] = 0,

}, -- end of ["cockpit"]

}, -- end of ["views"]

["sound"] =

{

["headphones"] = 0,

["cockpit"] = 0,

["GBreathEffect"] = true,

["world"] = 0,

["volume"] = 0,

["radioSpeech"] = true,

["music"] = -100,

["subtitles"] = true,

["gui"] = 0,

}, -- end of ["sound"]

["miscellaneous"] =

{

["headmove"] = false,

["f5_nearest_ac"] = false,

["f11_free_camera"] = true,

["f10_awacs"] = true,

["Coordinate_Display"] = "MGRS",

["accidental_failures"] = false,

["force_feedback_enabled"] = false,

["synchronize_controls"] = false,

["show_pilot_body"] = false,

}, -- end of ["miscellaneous"]

} -- end of options

 

 

 

6. We need to focus on the plugins category, it has all the special options for the modules -

 

 ["plugins"] = 
   {
       ["CA"] = 
       {
           ["kompass_options"] = 1,
           ["ground_target_info"] = false,
           ["ground_aim_helper"] = false,
           ["ground_automatic"] = false,
           ["ground_platform_shake"] = false,
       }, -- end of ["CA"]
       ["F-86F"] = 
       {
           ["landSeatAdjustF86"] = false,
       }, -- end of ["F-86F"]
       ["FW-190D9"] = 
       {
           ["autoRudder"] = false,
       }, -- end of ["FW-190D9"]
       ["UH-1H"] = 
       {
           ["UHRudderTrimmer"] = false,
           ["autoPilot"] = false,
           ["altUHTrimmingMethod"] = false,
           ["weapTooltips"] = false,
           ["UHTrackIRAiming"] = false,
       }, -- end of ["UH-1H"]
       ["Ka-50"] = 
       {
           ["altTrimmingMethod"] = false,
       }, -- end of ["Ka-50"]
       ["Mi-8MTV2"] = 
       {
           ["altMi8TrimmingMethod"] = false,
           ["controlHelperMi8"] = false,
           ["weapTooltipsMi8"] = false,
           ["Mi8RudderTrimmer"] = false,
       }, -- end of ["Mi-8MTV2"]
       ["P-51D"] = 
       {
           ["assistance"] = 0,
           ["autoRudder"] = false,
       }, -- end of ["P-51D"]
       ["TF-51D"] = 
       {
           ["assistance"] = 0,
       }, -- end of ["TF-51D"]
   }, -- end of ["plugins"]

 

7. Now for the TF-51D/P-51D/FW-190D9 , we can enforce the Auto Rudder (autoRudder) and Takeoff Assistance (assitance) options.

 

I hope this helps you guys,

Enjoy :)

Edited by xcom
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...