v81

Ability to modify airfield properties, lighting for example. The Su-25T training mission ' 04- Su-25T Landing - Difficult ' once worked ok but now that airport turn lighting on-on demand it's a no go. Fine if you're aware of the issue and how to use comms, but the target audience for the Su-25T is often the newcomer to DCS world as it's one of the 2 free aircraft. There could be other times or ways modifying airfield properties could come in handy that I've not even thought of yet. Maybe forcing a particular RWY to be the active. Just a random thought probably beyond the scope of this thread, add some female controllers. 3rd edit.. Ability to define flight pattern configuration?

Quick one. Any way to set an airport to have it's lights on at all times without player having to request approach?

Appreciate the response Ian, but the most annoying this is... 1)Affects all 2) Show stopper for new comers. 3) Multiple complaints 4) Easily reproduced 5) Easily fixed (wind mission time forward an hour or 2) 6) I've submitted a report through the official bug report form *including* a fixed .MIZ -- would have been well over a year ago now. There are probably process and procedures in place, but at some point someone at ED has to wake up and think hey, we know we're shipping faulty training missions and we've been handed a fix on a platter, let's use it. I've submitted sever other issues well over a year ago now, all with good notes, effecting all users that want to use training missions in DCS World and Flaming Cliffs, easily reproducible, often with a replacement .MIZ Many have been acknowledged, but nothing has been done. Trivial stuff like gate height in a Su-25T training mission, i assume it broke with the new caucuses map release (gates were set above MSL, my .MIZ sets them AGL and tweaks to ensure transition from gate to gate is smooth. Not a single gate needed moving except for a minor tweak to the last gate to line up with the target, just height adjustments. The issue in this thread, consider Joe Blow trying DSC World WILL encounter these issues. Makes it a bad intro to DCS, and will loose customers. I can understand these not getting priority if they needed investigating, but given i have submitted several tested fixes over a year ago some large gains can be made to put 90% of these issues to bed in less than an afternoon of work. Sure you could test them, validate them etc... but if time is an issue then let's just be realistic, DCS is shipping faulty missions, take a chance on dropping in untested but well documented replacements from an enthusiastic community. Risk assessment - worst case scenario, doing nothing means continuing with known faulty mission, if offered fix has some obscure fault then no net loss, best case, training mission is now able to be completed, new and/or returning users happy. If they still have the .MIZ see if you can get them to drag / drop / ship it in the next release. As far as communications go it would be great to see a new ticketing system where we can see bugs submitted by others. Even git hub would be better than what er have. There is an enthusiastic community that would be more than happy to both report on, attempt fix for and test these training missions at no cost to DCS. The bugs themselves don't bother me so much as the trivial nature of fixing them being passed over.

Probably not it as you mention other keys not working, but Track-IR is known to mess with F7 and F9 i think.

Was looking for something in my post history and came back across this. Based on what we're hearing of 3rd gen Ryzen, the new flaws in intel CPUs and the bricing of both it would be very fair that for just about all scenarios now AMD might indeed have the better offering. If anyone is reading this as of June 2019 that my current stand.

The choice of CPU will be insignificant as far as eye candy goes. That is almost exclusively up to the GPU Things like AA/AF HDR etc.. etc.. add no appreciable load to the CPU, the real true and honest answer is it doesn't really matter! The 3770K is fine, albeit beginning to age. If you do anything that take significant advantage of multiple threads (ie, not DCS) then consider Ryzen for value. If you want the best of single threaded performance (ie, DCS) with a few more cores for the handful of tasks that can use them i'd suggest sticking with Intel. I don't favour either brand. A mate recently did an i3 8350K / GTX1070 build with brilliant results, was the best combo to fit the budget, and i think we was much better off with the 1070 then a 1060 or 1050 and a couple more CPU cores. Previous to 8th gen i'd have never suggested an i3, but now they run 4 real cores at good clocks they are actually a solid gaming choice. If you have more money to spare go the i5 K series SKU. Overclocked or not the K SKUs benefit from higher base and turbo clocks, handy for DCS. As for the eye candy, it's almost entirely up to the GPU, spend as high as you can there. That is the most practical answer i can give. Only get the i9 if you can already afford an RTX-2080Ti. If the hint of fast Ryzen chips is indeed true this could also be an option.

Might not be the right place, but have a friend just got FC3 and is having trouble getting the Autopilot to remain on with his MS force feedback stick. The checkbox in the settings is checked. The autopilot appears to set ok but the force feedback moves the stick triggering the AP to shut off.

Agreed, the move the the new engine seems to have co-incidence with a number of issues. Ordinarily i think this is to be expected, and that the all of the, ED/DCS branded aircraft, and all of the ED/DCS designed training and quick start missions be reviewed and confirmed working and up to standard. Unfortunately none of this happened. Just about every aircraft has bugs since the new engine, some more severe than others. The same goes for the training missions I've been over recently, also full of issues. Many of the issues are so bad the break the training mission rendering it unable to be completed without modifying the mission files. Whilst most of us have a good feel of how to work, or work around these issues, the bugs and and broken training missions will put off a lot of new players.

In the first takeoff the aircraft seemed to do well without you in it. Maybe re-calculate MTOW and check the figures for the pilot?

Not meaning to offend anyone, but clear and simple things are being missed. Things reported multiple times, things that are a 5 minute fix, things that are important. My first comments on the SU-25T training missions being broken go back 2+ years and are posted in an appropriate section of the forum. I could contribute a lot more info about bugs but not seeing a dev ever acknowledge or replay to any of the issue threads is a bit of a putoff. In a recent thread i re-visited the SU25T training and know being a little more confident in the editor tested and verified a few fixes. I listed these fixes, and the thread is yet to get a reply. Even if the task is palmed off to blind freddy, making these changes and pushing them out in a rush would be better then nothing. Surely someone knows that many of the training missions are broken, but it isn't considered important. I stand by my comment that ED is losing business to this, not a huge deal to me personally, but we're also losing potential new users to fly with and expand the community. There probably a few people a day giving up on DCS because flying the SU-25T training makes no sense, and they simply might not be aware it's broken, as are several other training missions. Like i said, no offense, but whatever sifting is being done is missing some long standing and glaring issues.

As other have said this is very far from the truth. Also as said due to forum rules other games / sims cannot be named. There is 1 civil aviation sim that struggles badly even on the finest of fine hardware. DCS runs nicely on my i5-6600K, 16GB GTX1070 @1440p at medium-high settings whilst maintaining a 40 FPS minimum, averaging 60+ and some times passing 100FPS. Exception would be the Las Vegas strip where dips to 30 FPS happen. Trimming settings a little allows reaching the frames required for VR reasonably well. With a 1080Ti i could bring that minimum FPS up a bit and maybe add a little eye candy, but that card wasn't available when i got the 1070.

No luck finding that tutorial. Searched the thread for all posts by you but still couldn't find it. Maybe i missed it, would be great if you could link it. Possibly even add it to your signature? :edit: Looking at setting up the Flaps switch on the Warthog Throttle for the SU-25T and SU-27 Would appear there is a command to toggle flaps up and down, and a command to set flaps to landing. It appears i might be missing separate ability to have flaps in the up and mid positions.

Seems i'm here every so often reporting issues with the SU-25T It would be in ED's interests to have this working as for many it is the first aircraft they will test and try before deciding for commit more time and money to the sim. Here we go... 1) Lights from outside the cockpit seem to leak through panels sometimes. eg: turning nav lights on when dark illuminates the pit. 2) Cockpit lights too dim 3) Excessive cockpit rattle at taxi speed. 4) Training mission "Landing - Hard" no runway lights, impossible contrast / gamma Interesting to note that if the aircraft is touching the ground runway lights can be seen Affects all caucuses runways I've seen, but a bad intro for a newbie to have it in a training mission. 5) Excessively long dialogues in some training missions The detail is appreciated, but when you stuff up and attempt a training mission for the 5th time waiting through unskippable dialogues is a hassle. - Fix = Make them skippable 6) Cannon mission... a) Gates don't line up properly with target as well as they used to, leaves you having to make insane last minute corrections. - Fix = correct route, possibly set gate height as AGL instead of MSL b) Flares are dropped way too late - Fix = Trigger Flare dropper earlier, i did this by moving trigger zone to closer to player WP 3. c) Flares dropped in wrong location - Fix = move weapon release to correct location d) Flares dropped too high - Fix = reduce alt of flare dropper by 500ft or so. 7) Shkval mission - unable to lock targets, worked on previous versions (many threads on this issue) - Fix = Preferred - work on locking code, work around, set time closer to midday. 8) ECM training - Voice says lights should appear for ECM and IR strobe, but this does not happen, may be a case of active pause stopping the lights from appearing. Please consider getting these issues sorted ED. It will improve quality of product, quality of life and new user experience.

Can confirm, setting mission time to 11:45am resolved the issue. This mission worked OK previously, but getting a lock is so incredibly difficult it's pretty much broken in it's current state. Temp fix, edit the mission and set time closer to middle of day. I stand by saying that ED should be fixing things like this. Broken training missions can be a huge put off to potential new players.

I don't care too much about the resolution, it's the bugs that need fixing to make it properly usable at all times of day. 3 quick ones... 1) The light from the beacon leaks into the bottom of the pit 2) The AutoPilot buttons/lights are broken 3) Other external lighting (eg, floodlights at FARPS) leak in through solid panels. Higher res would be nice, but can we just get a working pit please ED ?

Appreciate the assistance LeCuvier Still struggling with a few, now on the Ka-50 We have a 2 pos toggle for the K-041 Targeting system, we built this command and placed it in the DCS World OpenBeta\Mods\aircraft\Ka-50\Cockpit\Scripts\default.lua file... <code>{down = 3525, up = 3525, cockpit_device_id = 59 , valuedown = 1.0, valueup = 0.0, name = ('K041 Power 2pos'), category = ('Ins Targeting Mode Controls Panel PVR')},</code> We sourced the number 3525 from 'command_defs.lua' "Plane_K041_Power = 525," We sourced the device from 'devices.lua' "devices["K041"] = 59" When bound to the switch noting at all happens... any thoughts? Any pointers on how i could become more self sufficient regarding that, don't want to be hassling you lot all the time, though i think the discussion has been pretty healthy and I've learned a bit ! Bonus question - I see "value_down = 1.0, value_up = 0.0" what are these numbers, and how are they determined?

Cheers, this worked for me.

Here too, looks to be broken. I started learning my way around the LUA configs, i'll see if i can knock together an interim solution. No luck, have submitted a ticket - #79106

Came just now after having issues in the Ka-50 and found this thread. ED please implement a fix to get the module usable in it's stock state again. I can appreciate not wanting to go to a significant effort if a full re-do is on the horizon Bottom line however is you can't leave a paid product broken.

I've hit my next roadblock. {down = iCommandPlaneAHCPHUDModeDayNight, name = _('HUD Mode switch Day/Night'), category = _('Armament HUD Control Panel')}, Is there a way to have the mode as 'day' with button 'down' and 'night' with button up? for example.. {down = iCommandPlaneAHCPHUDModeDay, up = iCommandPlaneAHCPHUDModeNight,name = _('HUD Mode switch Day/Night ON/OFF sw'), category = _('Armament HUD Control Panel')}, I made up the commands Day and Night separately, not sure this will work... is there a list of valid commands somewhere?

This is awesome info, and even better than i'd hoped for. I thought i'd have to write a line & assign a button number for each button (switch). Being able to create new command options is brilliant and just what we need. I'll get started and let you know how it works out. Much appreciated.:thumbup: ::edit:: Works perfectly, and now we have a better understanding. Again much appreciated.

Hi all, Working on AHCP panel with a friend, have it working as a joystick nicely, just need to get DCS to default to centre positions when the 3 way switches are in neither the up nor down position. Example... A toggle switch with 3 positions up = JOY_BTN1 = Master ARM centre = no button down = JOY_BTN2 = Master Train I have come up with the following... {combos = {{key = 'JOY_BTN1'}} ,down = iCommandPlaneAHCPMasterArm,up = iCommandPlaneAHCPMasterSafe,name = ('Master switch ARM'), category = ('Armament HUD Control Panel')}, {combos = {{key = 'JOY_BTN2'}} ,down =iCommandPlaneAHCPMasterTrain,up = iCommandPlaneAHCPMasterSafe,name = ('Master switch TRAIN'), category = ('Armament HUD Control Panel')}, I tried replacing some code in the file " A-10C_AHCP {3D04EBA0-A2F5-11e8-8002-444553540000}.diff.lua " from my save games dir with the above code, but broke DCS to the point where no key on the keyboard and no button on any joystick worked, mouse did work for all but pan/tilt/zoom. Here is my file with the basic buttons configured, can anyone offer any suggestions??? local diff = { ["keyDiffs"] = { ["d1374pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN1", }, }, ["name"] = "Master switch ARM", }, ["d1376pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN2", }, }, ["name"] = "Master switch TRAIN", }, ["d1377pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN3", }, }, ["name"] = "GUN/PAC switch ARM", }, ["d1379pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN4", }, }, ["name"] = "GUN/PAC switch GUNARM", }, ["d1380pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN5", }, }, ["name"] = "LASER switch ARM", }, ["d1382pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN6", }, }, ["name"] = "LASER switch TRAIN", }, ["d1383pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN7", }, }, ["name"] = "TGP switch ON/OFF", }, ["d1384pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN8", }, }, ["name"] = "ALT SCE switch BARO", }, ["d1386pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN9", }, }, ["name"] = "ALT SCE switch RADAR", }, ["d1387pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN10", }, }, ["name"] = "HUD Mode switch Day/Night", }, ["d1388pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN11", }, }, ["name"] = "HUD Mode switch NORM/STBY", }, ["d1389pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN12", }, }, ["name"] = "CICU switch ON/OFF", }, ["d1390pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN13", }, }, ["name"] = "JTRS switch ON/OFF", }, ["d1391pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN14", }, }, ["name"] = "IFFCC switch ON", }, ["d1393pnilunilcdnilvdnilvpnilvunil"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN15", }, }, ["name"] = "IFFCC switch OFF", }, ["d350pnilu351cdnilvdnilvpnilvunil"] = { ["name"] = "Weapon release", ["removed"] = { [1] = { ["key"] = "JOY_BTN2", }, }, }, ["d554pnilu638cdnilvdnilvpnilvunil"] = { ["name"] = "Gun Trigger", ["removed"] = { [1] = { ["key"] = "JOY_BTN1", }, }, }, ["d562pnilu606cdnilvdnilvpnilvunil"] = { ["name"] = "HOTAS Nosewheel Steering Button", ["removed"] = { [1] = { ["key"] = "JOY_BTN4", }, }, }, ["d957pnilu958cdnilvdnilvpnilvunil"] = { ["name"] = "Stick to trimmer control mode", ["removed"] = { [1] = { ["key"] = "JOY_BTN3", }, }, }, ["dnilp210u214cdnilvdnilvpnilvunil"] = { ["name"] = "View Up Right slow", ["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_UR", }, }, }, ["dnilp211u214cdnilvdnilvpnilvunil"] = { ["name"] = "View Down Right slow", ["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_DR", }, }, }, ["dnilp212u214cdnilvdnilvpnilvunil"] = { ["name"] = "View Down Left slow", ["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_DL", }, }, }, ["dnilp213u214cdnilvdnilvpnilvunil"] = { ["name"] = "View Up Left slow", ["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_UL", }, }, }, ["dnilp32u214cdnilvdnilvpnilvunil"] = { ["name"] = "View Left slow", ["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_L", }, }, }, ["dnilp33u214cdnilvdnilvpnilvunil"] = { ["name"] = "View Right slow", ["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_R", }, }, }, ["dnilp34u214cdnilvdnilvpnilvunil"] = { ["name"] = "View Up slow", ["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_U", }, }, }, ["dnilp35u214cdnilvdnilvpnilvunil"] = { ["name"] = "View Down slow", ["removed"] = { [1] = { ["key"] = "JOY_BTN_POV1_D", }, }, }, ["dnilp36unilcdnilvdnilvpnilvunil"] = { ["name"] = "View Center", ["removed"] = { [1] = { ["key"] = "JOY_BTN5", }, }, }, }, } return diff

Hey buddy, good news, Between ED/DCS and one of the server admins @ AEF 161 we've got it figured. Fault was a snapviews.lua file *serverside* that overrode users settings. Still unsure what caused it, but it has been fixed. Cheers.

Ok, problem solved. The problem was indeed due to snapviews.lua .... but with a twist. It was a snapviews.lua file withing the miz file on the server side. Just to be clear, server side. I had no idea such a thing could happen. Messaging DCS support with this thread lead to a reply suggesting something like that. And only now, a few minutes ago i got a message from one of our server admins that he's been experiencing the issue too, and confirmed the cause to be just as ED support said. So if anyone else ends up with this issue, and you have no snapviews lua file, try different servers / miz's and if you fin it's limited to a particular server / mission then this could be the answer. David and everyone else who contributed, you help is appreciated.

Thanks for David, gettign later here and only just checked for updates, will try what you've posted with a fresh brain. As it stands i have checked a few things and here are some facts. The issue only affects 1 particular MP server. Playing on any other server, no issue. Playing SP, no issue. I've found i can cause a SnapViews.lua file to be created by creating said views, but once the file is created deleting does not give a default head position in the circumstances causing the fault (particular aircraft/server).