ColinM9991

See the picture. Clouds are sitting over the electrical lines making them somewhat difficult to see. Likely due to how they're rendered at the foreground of a players screen with depth added after the fact.

There is virtually no information available in the kneeboard. Dialog hints disappear forever (not a campaign issue but a frustrating issue with DCS) and the trigger areas are very small. Rather than having to navigate to the Briefing (which also has not a lot of information) it would be good if the kneeboard had a flight plan and some basic information pertaining to the mission. I have had 2 attempts at this mission now, landing in 4 places in total and have yet to complete it because for some reason I am missing something.

Just posted a solution here which describes how to use the Jadro to communicate with ATC. Haven't yet figured out the other frequencies. Not even sure if you can tune to tankers and what not, not like you'd need to in the Hind.

For those, like me, who haven't flown the Mi-8 and didn't find an answer in this thread: I've been able to communicate with ATC via the following steps: 1. Set your Jadro radio to STB 2. Tune your frequency to the second frequency found for ATC in the F-10 map. This is in MHz and should be converted to kHz for the radio. 3. Set your SPU-8 radio selector to Jadro (third option from the left, on the dial) 4. Use the "Radio - Main" control, typically Backslash or OEM102 on UK keyboards.

I'm going to have to close this. I've just realised that I deleted my Saved Games folder when I migrated from Steam to the Standalone version. I don't have this track file anymore. If I can reproduce then I'll re-open in the future.

I'll spend a bit of time later going through the track files just to make sure I send the right one. If it's not exhibiting the problem then I'll try to reproduce, if not then I'll close this until I can reproduce this issue again; unless of course anybody else has a track file.

I have track files from the same session I took screenshots of, but they're quite long. Do you have the ability to skip through the track to the correct time?

Just playing a session at the moment where I shot down an F-14 and could see the black smoke through the clouds. Cloud preset is Broken 3 with a cloud base of 4,392ft

I've just been reviewing the store on my account which I've had for a few years. This account has no purchases on it as I'm using it for authentication with the Steam version and with server hosting. I'm unable to see any 50% discount. Could somebody provide some clarity over the discount rules? Does it apply only to new accounts or any account that has no purchase history?

Thank you for clarifying this. I think it's worth adding this to the update command list in the original post as this thread is the only documentation source for this executable.

This documentation is missing the --quiet switch for the update command. Also, is it possible to get a command line version for those of us running dedicated servers? Allowing full automation is the right thing to do and saves a lot of time.

Never mind, the issue is my IQ. My string concatenation was wrong. In LUA it's .. and not +. Example net.log('Hello, ' .. 'World!')

Hi, I am currently playing around with the scripting environment for DCS on a dedicated server, that I'm hosting locally to test, and have registered some callbacks. I have noticed that these callbacks all work fine and are logging to the log file as expected. When I add the getMissionFilename or getMissionName functions, however, the callbacks, that I add these function calls to, stop logging with no errors being logged. 'Here's what I currently have local dcsexporter = {} function dcsexporter.onMissionLoadBegin() net.log('[DCS Exporter] onMissionLoadBegin ' + DCS.getMissionFilename()) end function dcsexporter.onSimulationStart() net.log('[DCS Exporter] onSimulationStart ' + DCS.getMissionFilename()) end if DCS.isServer() then net.log('[DCS Exporter] Adding DCS Exporter Hooks') net.log('[DCS Exporter] Running as Server') DCS.setUserCallbacks(dcsexporter) end If I remove the concatenation and the GetMissionFilename calls then everything works fine. I would appreciate if somebody could point out exactly what I'm doing wrong.

This doesn't really help. There is very little documentation around the callbacks and I'm currently struggling to get onMissionLoadBegin to fire when the mission begins, as the name suggests it should execute. Does this callback even exist? What on earth are onPlayerStart onPlayerStop What's the difference between onPlayerChangeSlot and onPlayerTryChangeSlot?

Classic deflection as always, well done.

What's the hesitation with releasing this profanity list? You'd swear it's patented intellectual property. It's a strange request as much as it's a strange push-back to not release such a simple list of information. Is there a fear of blow back due to the list, rightfully, containing racial, homophobic and generally upsetting words? "Rogue" somehow made the list. Somebody didn't use bad words when they chose that name but they were still affected by it. I'd rather see and report any false positives by inspecting the list, instead of running into a false positive when naming a server and waiting for it to launch only to report an error. It is an inefficient, tedious and time consuming process.

I've experienced this quite a lot too. I often have to cycle around and back to INR for it to stop drifting.

Does anything happen if you press SCS toward the DDI that the FLIR is displayed?

This is happening to a small and private server that we're hosting. I have just tried moving the server from the E to C drive, also suspecting the same permission issues, but this hasn't done the trick for us - the server is constantly reverting to Resume Manual which is a massive pain point for any players who don't have permission to start a mission. Has anybody else identified a potential fix?

It certainly is EA (although this is commonly used as an excuse with any EA title/DLC), unlike the A-10C, so it is an apples & oranges comparison, but there are many systems (ILS being one of them) that are implemented while the documentation says otherwise in some sections and contradicts itself in others. Effort can be spent on documentation while systems are being developed as it doesn't take a whole team of developers to consult with writers or BAs/POs. In fact I wouldn't even think any developers would be involved in the systems documentation as they'd typically get requirements handed down to them. Though this is a bold statement to make because I have no idea how ED actually do this. My experience only comes from the enterprise orgs that I have worked in.

Thank you, it's good to hear that they were looking and the position has likely been filled. I had a peek at the A-10C II docs and they do look great with a lot of detail. This is exactly my thinking and my frustration. I noticed in the Navigation section, relating to the HSI, that ILS currently "isn't implemented". That must be a very old revision because ILS has been implemented for as long as I've been flying the F18 (almost 2 years) and I've used it many times on carrier landings. (Note: ILS for the F18 actually refers to ICLS) There are many great content creators on YouTube but the manual should serve as a manual to learn from and a reference guide to solidify ones understanding.

Hi, I posted a thread yesterday which was deleted, I've no idea why because I've confirmed (via Google linking back to threads here) that this is the right area for such a thread (mods, please do message me with a reason if I'm breaking any rules). Are there any plans on rewriting the F18 documentation when it is feature complete and released? As I mentioned in my thread yesterday, I have started reading the official documentation just to cover some knowledge gaps and I'm noticing that a lot of paragraphs/sentences are contradictory as well as some information being wrong. Example of a contradictory statement: Page 32, Function Selector Push buttons - autopilot is engaged when you press the AP button on the UFC, but autopilot is not engaged when you press the AP button on the UFC. Example of an invalid statement: Page 121, Adding Waypoints to Sequence - The following statement is incorrect because it is the SEQUFC page where you add waypoints to a sequence. UFC opens the waypoint configuration page on the UFC. Another similar theme which seemed strange to me is on page 60, controls for the joystick. Why would the paddle of the joystick, nosewheel steering disengage, contain information for how to use NWS-HI mode, while the Nosewheel steering description has no mentioning of that? This is a minor detail but it's a strange place to put this. If this thread is breaking any rules then please tell me what rules they are and for what reason it's being removed so I know what I'm doing wrong here. This module isn't cheap and while YouTube videos are a great reference I think it would be better to have an official reference guide similar to that of the A-10C II documentation which is fantastic. Regards, Colin

Significantly higher quality than the official documentation, thank you.

I booted up the mission and stepped away from my PC for a period of time. On returning I discovered that the TACAN had eventually caught up. It worked fine when my friend hosted because he'd been hosting for some time also which gave the tankers enough time to complete a full lap of their waypoint targets. I'm speculating that the tankers had to cycle around the waypoints once for everything to get settled. Thank you for your response though, I appreciate your assistance and time.