ADHS

Hello. Try: SAVE STATIC TEMPLATE menu or if you confortable with LUA, pass it manualy in the Group template. Thank you.

.getHeight

I can read it. Check if you have special view formating. Or else hover the mouse over the thread and you will ba able to read the text. Thank you.

Hello. I agree with your point. The only that i can add is that in lately years, updates have fixed many of the problems that for years were stood unresolved. If this was a KA-52, glady to wait so this to comes out of the "Early Access" status, even for a decade. But for this one, i do believe that is an extension of BS2 just for AH-64D to have a more equal opponent. Thank you.

Hello. Reading available slots in multiplayer servers, i've noticed that too many servers have replace (and many have exclude) BS2 with the new BS3. Just keep in mind that BS3 already have too many issues that they have to be fixed. Thank you.

Try get the rellated code number from the Cyrilic keyboard.

Hello. I've ask for similar but doesn't matter. I agree with your wish. Thank you

Hello. For now: Logitech profiler -> Bands . Thank you.

Merry Christmas Ok, glad you make it. I am using OBeta, and by replacing one file you can avoid re-installing.

Thank you, also.

Hello, Merry Christmas and Happy new Year, in advance. What is your current selection in: WINDOWS \ DISPLAY \ SETTINGS \ Multiple Displays \ field ? Seems that you are not using the required windows monitors condition that DCS needs, so to work with. In the worst, you may need to "live with it" by redirecting to "Monitor 2" before you run DCS and after quit DCS, switch it back. If you can please upload a screenshot (PrtScr) of your DCS \ SYSTEM settings. My DCS: UH-1H Huey Cockpit is in Russian --> DCS \ OPTIONS \ GAMEPLAY \ Avionics Language ---> English. Thank you. PS: Line 6: You don't bother me, glad to help a fellow choopie. All good.

Hello and thank you for your help.

Hello and Merry Christmas. Thank you, see you there.

Hello again. Of what i've tested with bombs,guided etc there is no standard. Everything varies. And need for each type to setup other setup. I've added a wish (for DCSanta). Merry Christmas guys.

Hello and thank you for your reply/idea to help. This is a problem that goes many years in the past. When there were no HOTAS, with knobs. Now, there are and we can have them. Even the most cheap joystick have knobs. BS3 doesn't. (In my opinion) i don't like to use external apps or mods to fix something brand new that i bought. If my new refrigerator have problem, i won't accept to fix it. I would ask for a replacement with another NEW, that is not problematic. Here is a bit different. We all buy "early access". Means that we accept that is not final. Besides BS1 and A-10, the most that took a module to get out from early access was ten years. So: Usually, after every DCS update, most of the external mods even my own custom scripts have problems and need re-programming. And this will getting worst once DCS deside to upgrade it's core to multithread. Means that we've got to forget all of what we know. Personally i prefer to create a common secure Logitech profile for all of my modules or even to overwrite the Config after every update. Thank you.

Hello. Did anyone noticed that SPEED (HUD) is not updating till you release TRIM key/stick? I am using keyboard (away from gear) and i was wondering if after the last update indeed there is problem also with HOTAS. Thank you.

as i say: Once i've got help, i owe to say thank you or it didn't worked. Την ΣΥΜΠΕΡΙΦΟΡΑ και την ΑΝΘΡΩΠΙΑ την μαθαίνεις απο την οικογένειά σου.

Hello, and sorry that it didn't, but it will. Check: Your settings in special menu for KA-50. There you can alter the way how your trim will work and which hardware will affect. For trim section i use the 1st one (x56 here). Check that you have assign the TRIM on and TRIM reset. Also use RCTRL+ENTER will popup your HOTAS window that will visually present if the trim have been set or not. Thank you.

Hello. In your log, initiator is nil. Sure CRASH is covering the DEAD event, by NIL-ing all available information from initiator. if _Event.initiator then .... local alaCATE = _Event.initiator:getCategory() if alaCATE <= 1 then .... I have solve my problems (for Client+AI) by using UNIT_LOST instead of DEAD. If i may suggest, try test: CRASH in a seperate check, but after UNIT_LOST. Avoid check both with OR in the same line. Thank you.

Hello. Director will override your trim. Try with all modes on except Director and Q = off. Thank you.

Hello. Try a clean ME mission just with a KA-50 to see if it is a server/weather/procedures problem. Thank you.

Hello. Backup the "MonitorSetup" directory. Delete everything IN there. Start DCS. Exit DCS Paste back the backup folder. PS: If ask you something and you can't click it, press ENTER or use the TAB to move through selections,

I had the same. After get the LEAVE, check it alone without OR with another event. Are you checking multiply events in the handler ?

Hello. As i am now away from my flying gear, i was playing with ME and testing all availabe AI aircrafts in muti-role scenarios. What i've realize was that there are too many restrictions and too many differences among the types, no matter if i choose them to be under the same task/role. As a user, i was expecting once i've setup a route with waypoints tasks/advanced commands/actions, all the available aircrafts that i would choose or if i later switch between them for this role, to follow and execute the same thing. But saddly they didn't. Each aircraft needs "special treatment" to execute director's role. And this is a logical problem that i insist you have to fix it, as all these people out there that are creating missions or those that they are running missions in their own servers: are supporting DCS. From the time that there are TASKS, no need to hide aircraft types, as all of them (in reallity) can execute from guns to bombing roles. From the time that there are TASKS, no need to bring the user to calculate the altitube, the distance, the angle, the type of weapon, the when and after etc, so the required task result to happen. Give to him options to choose and alter the events. But keep him away from all these factors that (supposed) are under the headline of a choosen TASK. A TASK that all AIs should understand and just do what they have to do. Let them to execute the mission TASK, not the user. Gladly to create DCS missions. "Multithread" modern tools, are required. Thank you.

Usefull proposition, wish could be done someday, practical/handy instead to see buldings in the air flying together with the airplanes. But It is a 2D top view enviroment that transcodes data to a *.miz file. If it was a seperate application from DCS (as was in past) i think, it would be done already.