HILOK

couldn't find the right option to answer: love them, but would still vote for this feature to be an option. in other words: i think reflections and dirt are essential to an immersive look & feel, but should be improved.

it has been too sensitive even before, in my opinion. btw, the manual states: "Lateral stick displacement greater than 0.5 inch causes the autopilot to decouple from the steering mode". it would seem logical to me that this behavior also transfers to engagement criteria. but also if this is not the case, this is a simulator, and given the limitations of game controllers, there should be a higher tolerance to 'centered stick' for AP engagement, rather than have everyone set a dead zone, which is even more unrealistic and has a negative effect on manual flight precision.

thanks, guys, good work!

make mouse buttons for select and pan consistent between mission editor and f10-map

maybe what has everyone confused is, we would expect that the AZ/EL FOV box should grow (while keeping its edges proportional to the scan area set), when moving the radar TDC up (=forward =further away), and the box should shrink (to a point ideally), when moving the radar TDC down (closer to the nose). then again, that would not make any sense, as the B-scope of the radar page does not depict a cone, but instead is stretched out left and right, as the TDC comes closer to the aircraft's nose. in other words the EZ/AL page reflects the radar page's distorted view.

DCS world manual from 2020 can be found here (suppose it's the most recent one): https://www.digitalcombatsimulator.com/upload/iblock/ed6/87v22jwd1xh51i3rgki944xsf503istq/DCS_User_Manual_EN_2020.pdf but this is mainly about the core program and mission editor. as others have pointed out, when it comes to aircraft specifics, i'd recommend starting with chucks guides. good reading

ok, and can you load a separate profile for each a/c into the arduino/dcs-bios ?

i am not sure i understand. you have to bind the switches once for each aircraft anyway, either in dcs or in bios, right? (just curious, not using dcs bios yet, obviously )

i can assure you, this is not how good encoders work, definitely not in airplanes: 1 'bump' equals exactly 1 input in fine mode (slow turning), and they (mostly) work in two modes, coarse and fine, otherwise it would take forever to dial in a specific value. i had similar issues as those you mention, which i would describe as spikes, with my old goflight gear, and was able to mostly resolve those using contact spray.

ha! never thought about that... to each his own

reading over some of the comments, i am not sure, if this is about how to customize kneeboards in DCS, rather than the wish of some players for a quick and easy start into a new module...as accessibility to the game seems to be a concern to ED, that thread could be of interest to them anyway, since nobody mentioned this before: kneeboard builders such as https://forum.dcs.world/topic/108023-kneeboard-builder-windows-app/ or https://www.digitalcombatsimulator.com/en/files/3315463/ allow you to edit each A/C's basic kneeboard. there are plenty great checklists to be downloaded in the user files btw "real" kneeboards have been replaced by tablets or EFBs as far as i am aware of. either strapped on your thigh or mounted below the side window in airliners. as their volume is virtually infinite, they include all OMs, checklists, and charts. etc. personally, i like to use a tablet fixed to my thigh in DCS, but if you're in VR that's another story.

dcs briefing room (still beta) is able to generate random SAR/CSAR missions for you including briefing, kneeboard etc. it's very nice https://github.com/akaAgar/briefing-room-for-dcs

that would be absolutely awesome, also for the modern era, and should realistically include reflections from other parts such as building windows. maybe MT would allow modeling this in the future using raytracing techniques.

looks very nice, thanks

RL avionics often use proportional "steps", depending on how fast you turn an encoder. for instance, if you need to select a reciprocal heading you would not have to actually produce 180 "bumps" using the knob. instead, turning it fast would make it step by 10s, and slow turning would revert to step 1. thanks to that mechanic, after some getting used to, almost any setting can be achieved with 2 - 3 well proportioned turns. (the software FSUIPC for the MS flight suite mimics this quite effectively to some extent) i dont think this mechanic has been implemented into DCS yet, not for the mouse wheel either. at least not for every module consistently, as you can easily see, when trying to set your altimeter or heading in the huey. i also think this would be great for proper use of hardware encoders, mostly for cockpit functions that use an encoder and/or have a wide input range, e.g. altimeter QNH setting, HDG bug, radio FRQ selector, trimmer wheel; it would usually not be useful for knobs that control a relatively small range and incorporate stop ends like volume, lighting knobs, etc. therefore making it a user option in the control settings (as with the axis "slider" function) seems a good idea to me.

then it should be safe to delete these, right?

the map looks fabulous. thank you very much for putting so much heart & soul into this! probably too late for initial release, but thought i'd mention it anyway for your consideration (dunno if you guys are already aware of that): one very distinctive feature of cairo at night (and probably the whole region) are lots and lots of green lit mosques.

very good points. and if the flight model was accurate enough, we could just use graphs from the original OM, which i personally always prefer

bear in mind that settings are very individual, because they are not only subjective, but also depend on the jet seat version. i am using the old '908' currently. anyway here you go

@Tim_Fragmagnet thank you so much for all your dedication, patience and perseverance

+1 lecuvier's solution is great, and a mod manager solves the dcs update problem. but wouldn't it be much more convenient, if a simple optional single-press command could be introduced globally (same for all a/c) by ED?

+1

thanks, but according to @BIGNEWY's reply, i am not sure, if ED is planning to implement it. and i dont consider this to be just a "wish list item" usually this is how it works. that's why the a/c must be moving through the air to get a readout. and hopefully yes, that would be a good opportunity to implement it

that's a very very good idea! agree -matching airport layout incl elevations and beacon locations would be a plus in order to have one airport chart serving both maps

agree with the reasoning of @=BoB= David and @AKULA_OPTIMUS and if i may add: the INS wind in HSI>DATA>A/C would be very nice too, and should be an easy task to implement.