nomdeplume

For ground crew you could also try just using the comms menu directly rather than a HOTAS MIC switch (default key is \ i.e. backslash). This has always worked reliably for me. So long as the ground crew can "hear" you they'll respond - which means either set the interphone dial to INT (and power to that system on), or have the engines off and the canopy open. Another thing is that it might be mission setup; a while ago they changed how airbases are assigned to coalitions and if you're playing an old mission that wasn't updated then it might be that the base is considered neutral and therefore the ground crew won't have any interest in you.

Yeah, sorry, I forget that people actually play the FC aircraft. :)

FWIW you already can reload/refuel with your engines on. You'll need to use the intercom for the crew chief to be able to hear you, though. Basically the game pretends that if you're parked then the crew chief plugs in his headset so you can make requests over the intercom. Not sure how/if it works for FC3 aircraft though.

It's normal, they remain at the same size regardless of how far you are from them. That's why you can see them and the terrain at the same time, instead of having to keep shifting your focus. You might want to look at the zoom settings instead, which adjusts your field of view and therefore makes things seem larger or smaller on your screen.

You need to wait a few seconds before the goal will be applied - you can look at the debrief log (default key is apostrophe ' I think) within the mission to see if it has yet, where it says "Mission results" (the 'score' shown is for destroying units but not used by the campaign system). Edit: attached a tiny "campaign" that works for me. TestCampaign.zip

Pretty sure this problem only affected fixed-wing aircraft - I think the initial issue was bigger but that was resolved during the open beta period, it just an issue with fixed-wing aircraft not being able to have triggered commands run. Many many missions require activating groups by triggers and they didn't break all of those missions. If you need another pair of eyes on the issue you might like to post in the Mission Builder's Corner.

Awesomesauce! Thanks, Grimes! :)

No mention of the start trigger for planes in the 1.2.8 preliminary changelog. Any of the testers able to see if it's actually been fixed and just not mentioned in the changelog? See also: http://forums.eagle.ru/showthread.php?t=118666

The GBU-10/-12 have two release solution modes, one which provides for ballistic delivery (basically putting it on the target like a dumb bomb) and the other one for guided delivery which puts the bomb past the target - the idea being that the seeker will pick up guidance and use the extra energy the bomb has to guide to the correct point. I believe the default setting for these bombs is the guided mode (otherwise known as Optimal Release Point), so if you just do a CCIP release the bomb will actually land beyond the expected point of impact. To correct that, either start lasing earlier to catch the bomb before it gets past the point it can actually detect the reflection, or switch the release solution mode in the DSMS. For the former method to work, the bomb's seeker needs to be pointing in at least roughly the right direction - a steeper dive angle at release will help with that. If you release the bomb on a fairly flat trajectory, it can sail right over the target without ever being able to detect the laser. The release solution is briefly mentioned on page 555 of the manual but it doesn't seem to go into any depth on the topic. You can cycle the delivery solution at the bottom-left the weapon profile settings in the DSMS. (At least, I think this is how it works, or used to; I haven't done a CCIP delivery of an LGB for a long time, and it seems really counter-intuitive for the CCIP pipper to indicate a point where the bomb won't actually hit unless it's guided. But I guess it does make sense if the system expects it to be guided, which is basically what you're telling it when you have the ORP solution selected.)

Could you post a track of it? Maybe just a minute or two from an air start? If other people can/cannot replicate it when viewing your track it might help narrow down what the issue is.

Have you tried raising the seat instead?

If it's not working you could probably contact the support team via the DCS website help ticket system to get assistance. The module's more like a free update to the standalone version than a separately-purchased sequel. Of course if you love ED/TFC and want to through money at them, then by all means purchase it again! :)

You probably don't - most likely the retail DCS A-10C you've got is an older standalone version prior to DCS World. You can have it installed but it's essentially a separate product, so you don't need it installed to fly the A-10C in DCS World. What you'll want to do is install the A-10C module, either from the modules page in DCS World or download it from the website. You should be able to use the serial number from your boxed copy to activate the new module.

The link was incorrectly formatted, should be http://update.eagle.ru - you'll get a completely blank page if it works.

You'd want to de-activate the game (to reclaim the activation) prior to starting your new operating system install. Essentially what you're doing is equivalent to replacing your computer with a new one, i.e. moving your licensed copy to a different computer. So, deactivate on the old one, and then re-install on the new one which will then require activation.

If either of you are running any kind of advanced firewall or antivirus software you might want to try temporarily disabling it - perhaps something in the mission file is triggering a false positive and it's interfering with the game's ability to load the file. That might explain why other missions work okay. You could also try clearing out the ..\Saved Games\DCS\Logs folder and then reproducing the problem. Something in the logfile might give a clue, and you can of course upload them here for others to look at. Have you tried hosting any missions yourself, or is your buddy always the host? Might be interesting to see what happens if he connects to you instead.

If you've got TacView installed with the stable version of DCS World, then your export scripts will be in ..\Saved Games\DCS\Scripts. Copy the files "Export.lua" and "TacviewExportDCS.lua" into the Scripts folder under the open beta user directory, i.e. ..\Saved Games\DCS.openbeta\Scripts. (Create the Scripts folder if it doesn't already exist there.)

Hitting the SAVE button will in fact save the profile, but it will only use those settings if you actually load the profile. In addition to the HUD DSMS left/right method for cycling profiles, you can also activate your saved profiles from the DSMS profiles screen: use the up/down OSBs to select the profile you want to use, and then press ACT to activate it. It's not clear from your post Devrim whether you're actually hitting the save button, but just in case and for anyone else reading the thread: the blinking SAVE text indicates you've made changes to the profile that have not yet been saved. If you navigate away from that profile your changes will be lost. If you hit the SAVE button it will stop blinking and the changes will actually be stored. Might also be worth mentioning that after a profile is activated, you can override the master mode with the master mode button on the stick. So if you've set the profile for CCIP delivery you can activate the profile, and then hit the master mode to cycle to CCRP mode, and get the appropriate cues.

Anything at all really, especially error messages etc.

Awesome! Glad it wasn't a broken stick, that would've been a pain. Happy flying! :pilotfly:

If it's happening with everything it does sound like it could be a hardware issue. Try going to the Windows 'Devices and Printers' window, right-click on any game controller and select 'Game Controller Settings', select the Joystick - HOTAS Warthog and hit Properties, and then fiddle with the stick and see what Windows makes of it. You can also try going to the 'Settings' tab in that dialog to recalibrate it. If you're seeing the same thing happen there then it's sadly probably going to be an issue with the stick itself.

Well unless the mission is poorly designed you can just change the frequency off of the ATC once you've departed and switch back upon your return. Generally flights shouldn't be set up to use the same frequency as ATC. Or you could turn that radio off. :D

The WH HOTAS is mapped properly out-of-the-box, the TRIM being the POV control is the only exception, as not everyone has TrackIR or similar. I think by default RightControl+Trim Hat will control trim. If you go to the controls section of the options menu, select "A-10C Sim" for the layer and "HOTAS" for the Category, you'll find the Trim: controls at the bottom of the list. Scroll across to find "Joystick - HOTAS Warthog" then click in in the controls grid to select it, hit the CLEAR button to clear the existing assignment, then the ADD button to re-assign it. You'll get a dialog prompting for the control you want to assign, you can just press the related control (i.e. the appropriate trim button on the stick) and then hit OK. You'll probably also want to at some point adjust the sensitivity curves, especially for the slew control on the throttle. You can do that via the "Axis Commands" category. You'll want to try it out with the default settings in-game first and then if it's too slow or too fast, make a note to adjust it next time you're in the menus. Tends to take a bit of trial and error. Your pedals probably won't be correctly configured automatically, you can set them up within the Axis Commands category as well. The controls configuration is a bit intimidating at first, but it's a complex sim with a LOT of controls. If you just focus on the main things you'll soon get the hang of it, and you'll find it's pretty flexible. The main annoyance with it is that it has a habit of assigning any unrecognised hardware

To run the updater use the shortcut in the start menu, the working directory needs to be the root "DCS World" folder, not the bin folder within it. If you don't have the shortcut for some reason you can create a new one shortcut to the DCS_updater.exe application and then modify the shortcut as follows: - Set Start In to to the DCS install folder, and - add the word 'update' to the end of the "target". For example, my target is: "C:\Games\DCS World\bin\DCS_updater.exe" update and the start in folder is: "C:\Games\DCS World"

You could look at the updater log in ..\Saved Games\DCS\Logs\autoupdate.log to see if it gives any useful information.