NeMoGas

You really don't get it do you? You have no idea how any of these servers work. It's all based on LUA script. You could set up a condition where once 5 crates are moved by slingload and unpacked it fixes the airbase instantly. You could also make a timer start once they are unpacked fixing the base in an hour. The request is for the ability to simply fix a runway. The details of how long, or under what conditions, or even if at all would be up to the mission designer.

Not sure what is funny about that? I never specified a time. But lets say that when the command is given that the runway is repaired instantly. That does not stop the mission designer from then deciding how long they think it should take from a gameplay perspective. It could be 1 second or 1 week. Do you even play MP? Do you understand how any of these missions are run? Do you also understand the issues specific to multiplayer? Would you rather JDAM, JSOW-C, RB15, and any other weapon capable of stopping players from playing be banned on these servers? Many servers already ban some of these weapons for this very reason. This is a real gameplay issues for some servers. If you don't like this because of realism then don't play where an option like this would exist. Just like servers with external views, labels, or other options enabled it could be allowed or not.

It could be instant or it could take a set amount of time. I guess it would depend on how ED would actually implement it. If they just gave the function to fix the airbase instantly then server owners and mission designers could decide what conditions need to be met and how long it would take. When we do get the dynamic campaign and if said campaign is usable in multiplayer this feature will be even more needed, even if it takes days, hours, minutes, or seconds.

This really should be a feature. It may not be realistic but neither is bombing a runway with RB15s that create massive phase shifting craters that cause your aircraft to fall through the earth. You drop a couple of those on the ramp and using a taxiway is not even a solution anymore. The solution then is to pick another airfield. But then what if that field gets the same treatment? Well then I guess you go down the list until they are all bombed. Then the solution is to disconnect and find somewhere else to play. Not a very good solution for server heath, and a solution no server owner wants to see. Realism can be taken to an extreme that makes no sense. How about you have to buy a new copy of whatever module you were shot down in? I bet ED would love that. Maybe even charge $25 million per copy? This is a video game at the end of the day and options like this are needed for many scenarios in the MP environment. An option to use or not use this feature would allow mission designers to make that decision for themselves.

I've been dropping GBU38 with a TMR of 10 seconds for a while now. Been capable of scoring hits from 27nm if no mountains are in the way. Also I noticed alignment seems to be unnecessary as well, but I just chocked that up to INS being WIP/nonexistent.

Fast align in DCS still gives you the maximum accuracy. In the top right corner of the CDU you will see the FOM (Figure Of Merit) for the DTSAS and GPS/INS. B1 indicates you are in blended GPS/INS mode with a FOM of 1 which = less than 26 meters if I recall correctly. A higher FOM equals more error. 1 to 9, with 9 being greater then 5000 meters.

From what I can tell zooming the TPOD in and out also elevates or depresses the radar.

Once I found where that LAU was it worked like a charm. Thanks again for the help LeCuvier. For anyone else who is like me and doesn't know where that LUA is, I found it in DCSWorld\Mods\aircraft\A-10C\Input\A-10C\joystick

Thanks a lot, I will give that a try. I indeed do use the CH Pro pedals.

So long story short my left toe brake wire snapped. I tried to bind my right pedal toe brake to the both brakes axis bind in controls. Well it does not allow this to function as it is grayed out. How am I supposed to bind this now, and why in the he** does ED have so many non-functional, un-bindable, controls in their mods? I mean I had to jump through hoops with LUA to get the cargo views working on the UH1 and now this. Can we please get a fix for this so I can stop swerving down the runway like a drunken monkey as I attempt to brake? Oh and this function works in the F18 as I was able to correct for my broken pedals. So why does it not work here in the A10C?

Last time I checked you do get a spike on the RWR when a Tunguska is shooting at you but won't get a launch warning. Perhaps because the radar is used to get target position updates and then correct the missile via radio command guidance.

I think the Tunguska is radio command guidance.

Only the SA342M has NVGs in DCS. You can however enable them in the other versions with a LAU edit.

Just the engage switch. All others off.

Thanks for the info guys.

I think I may have found my issue. It seems as if the F14 automatically trims itself out when the autopilot engage switch is turned on. Even with alt and heading hold off on the autopilot control panel.

So I have noticed when I turn all SAS channels off there seems to be no difference in flight characteristics vs all SAS channels on. However I did notice that if I put the autopilot engage switch below the SAS channel switches on, it seems to change the characteristics. This is with all the autopilot settings turned to off. It seems to damp the roll and also the pitch. I looked in the manual and the NATOPS, but it mentions nothing about this switch needing to be on for SAS to function. So the question is, is this a bug or am I missing something here?

So I have had this issue on more occasions then I can count. The issue is I lock a target in the HUD with an AIM9X using the uncage button. I fox the first missile and the second does not auto acquire the target. This seems to happen maybe 25% of the time, maybe more. I do not think it is a masking issue as the target is in the HUD, and I'm using wing tip mounted 9X's. Is this a bug, or intended? It has got me killed many times as I fight to relock the target.

When flying either the F18, A10C, or AV8B. Especially easy when they are in a hover trying to sling a crate.

I shoot down helicopters pretty often with Mavs.

Unfortunately I have disabled tracks since I play on MP and they become huge and unplayable, so I have none for this instance.

If you try to change scan from 2 to 4 bars, or any number while also trying to lock a point on the radar or a target the radar seems to break. It will scan the same area you attempted to lock endlessly for that selected weapon. When I would change weapons it would act as if it was scanning correctly again. Then if I changed back to the original weapon it goes back to scanning a small zone endlessly. I also noticed that the horizontal azimuth setting would show some odd numbers too.

So it seems this will work in a SP mission but not in MP. Also your view settings look different from mine for the F18C.

So I did everything in that thread and finally got it working after about an hour. I added the server.lau and edited it without a change. I then deleted the server.lau and copy pasted an edited backup in and it worked (it was exactly the same). Then today I jumped on and now it no longer works. Not sure what the issue is, but since I can't get the setting to stick I would still like it officially added some day.

Thanks I'll try that out.