iffoif

Hi, thanks for your reply and your suggestions. I did not know about a messge log and I'll take a look at this. This will certainly help in those situations when there is information overload. Thanks for your help and for the excellent campaigns!

Hello! I tried playing the 1st mission ran into a problem: After delivering troops to the FOB and being on the way home, after receiving the call for rerouting and another assignment, I crashed the helicopter. The reason: I was fumbling with setting up the FM radio homing (which does not work for the given frequency), looking at the kneeboards, trying to find the map marker which was supposedly added (since it being the same color and shape and design as the others, I was not able to find out which one it was), trying to remember which coordinates I received in the radio message, looking out, trying to find out where the hell to go ("it is near" is not a good description of where to go), actually flying the hleicopter.... Well, it became clear that flying the helo alone is not realistic. The PNF should be in charge of setting these things up. My question is: Can I play this mission together with another human player? So he can set up the radios, spot the outside and keep up on the radio stuff? And I would love to posit these suggestions: 1) FM radio homing does NOT work for the new assignment in the south. Yes, I entered the correct frequency, homing worked for all the other locations. I was totally at a loss where to go, circling around while fumbling with radios and kneeboard pages. 2) Make the map marker stand out in a way, give it a unique name like e.g. "FOB 2 - This is the marker I added". Is it possible to add "hand drawn" lines and shapes through scripting on the map? 3) Please make it possible to request repeating this particular radio transmission kind of like this: "press space to request repeat of last radio instructions". Or make the copilot say something helpful, if he notices me not making progress towards the other FOB for 10 minutes. Thanks for taking the time to read this.

I have ran into a similar issue some time ago. Here is how to find out what causes the conflict: In the multiplayer browser, click on the red exclamation mark (which tells you, that you are impure). The game then shows you a list of conflicting files. These are the ones you need to remove.

oooooh, interesting! You learn something new every day! Thank you for the explanation!

Thank you for taking the time to reply! Oh and thank you for this great campaign! That is what I tried and I got PTSD flashbacks from the time I learned cross country navigation in FSX with Rod Machados PPL license texbook.... The problem with this method is that it is hard to account for wind induced drift... And what is SuperFudd? I got no messages, probably because I missed the trigger zones? Hmmmm, the video is interesting! Unfortunately the navigation part was cut out - after takeoff and the initial turn, the video commences at around waypoint 2. Interestingly, there is no voiceover and the pilot just asks AWACS for bogey dope and turns right towards the enemy planes. Is that what we are supposed to do?

Hello! I tried this mission on the weekend and need help.... * On my first attempt I got lost because there is no Radio navigation and the F5 can not interpret the russian "Channel 28". How am I supposed to navigate besides estimating my distance and useing the compass? * On my 2nd attempt the VR mouse cursor disappeared and I no longer was able to click things in the cockpit. DCS stuff.... * On my 3rd attempt I was killed from an impressiv edistance by a Su24 that made an insane loop towards my flight and attacked us from above with astounding speed. My F5 was sniped with a gun burst before my AIMs could get a lock. Also the F5 struggles to stay above stall speed at 25k feet, unless you go constant full afterburner. Could you give me any hints on how to navigate in that mission? And how to not stall at full throttle? And what to do wit the Su24s that have unlimited energy to do 500 kts loopings at 25k?

That is good to know! On my first attempt, I tried going low and evading but was shot down. On my next try I flew a screaming spiral at the SAMs and took out a few units with my guns.... However, when returning to base nearly at sea level, I suddenly saw shimmering stars surround my plane and a short while later my pilot died. Weird!

In that case you unfortunately will not be able to see or join the server. In order to play on it, you need to switch to the open beta version. Depending on whether you use the Steam or standalone verison, the procedure differs (but you will find plenty of instructions on this forum on how to do it).

Thank you for taking the time to answer to my post! Yes, of course people can choose their own frequencies (which is what I do with a friend of mine, when we cruise around Hoggit TNN). But if you offer some "official" ones, it could promote communication on those frequencies. And yes, ingame voice comms..... I don't want to be a naysayer (and even less intend to be inflammatory!), but I have been following DCS for a few years. If it goes like the new AI, or weather system or clouds (which may finally be coming after 10+ years?) or proper ATC and so on.... we could be waiting until 2035 for that. And even then, I highly doubt that EDs implementaiton will be even half as good as Ciribob's excellent SRS. Their track record simply shows that. So until the ingame voice comms will be actually usable and implemented with the planes, having options like SRS and evn discord, is awesome.

Hello everyone! I also love flying on this server. Did not try the firefighting yet, but am looking forward to it. Personally I dislike Discord (maybe I am too old) as it is totally cluttered and confusing to me. Why don't you just use SRS to communicate and coordinate? SRS basically is an essential DCS addon anyways, a de facto standard for online comms. The mission author could define certain frequencies for e.g. SAR comms, Fire OPs comms, airfield traffic and so on, publish them in the mission briefing and players would just tune into those frequencies. Or mybe just use a "general comms" frequency like 245 or something like that. Back when I had a friend who played online with me, we always chose a "personal" frequency to talk between the two of us and had the other relevant frequency tuned on the other radio. Worked perfectly fine.

Hello! Has this been fixed yet? I tried the Case 1 instant action missions and was unable to see the AOA indexer lights. Also trying to turn them to brighter did not work.

Sorry for making a double post, but I wanted to separate the VR screenshot from the others. This is a screenshot of the display mirror DCS window. EDIT: I also managed to capture a short video of the display mirror window. Sorry, I have no experience with this, so I hope it will be enough proof. Link: https://drive.google.com/file/d/1ELokFvjgbY8aKY76qOhICBbYzK_Xx8Z9/view?usp=sharing

Hello Elmo! Would you like a screen captured video, oder rather one filmed with a smartphone?

OK, I was extremely busy lately but managed to get a 2D screenshot on on of my computers. This is how the warning lights panel looks in 2D: unreadable. When you zoom in a lot, the issue gets better. I will try to upload a screenshot from my other computer and one VR screenshot later. Edit: I uploaded 3 more screenshots from my other computer. Here you can see clearly in 2D that the warning lights are not readable.

How about this bug? Is it already fixed or at least acknowleged? Last time I tried starting up the harrier, the sounds were still all messed up: Audio warnings inaudible, engine spool sound cuts out in mid-start etc....

It's good to see that after many frustrating years, bugs finally get acknowledged. How about this bug? Is it already fixed or at least acknowleged?

Has this been fixed already? Or at least officially acknowledged?

I am glad it was of a little help. Yes, the process is a bit involved, but not as bad as some other setups I did years ago. Following that "checklist" step by step and reading those webpages helped me a lot. After only a few hours work, the server is up and running. The only thing that still bugs me is: I have to connect to the server computer by remote desktop to access the local webGUI.

Hello! You need to provide more information: Did you open the needed windows firewall ports? Did you configure your router/firewall? Did you set up port forwarding properly? The screenshot you posted looks to me like a port forwarding screen form a router. You need to enter the proper values in there. E.g.: Local IP is the servers IP address, the ports and protocols need to match the needs of your DCS server. I tried following a combination of the tutorials linked here and here. I also made a small checklist and got everything working. Maybe it will help you, to read the list of tasks I performed to get the server up an running: I hope that this wall of text helps in some way.

Hi there! The bug with the wing sweep lever and mouse scrolling is still there. When scrolling the lever into oversweep with the mousewheel, it will go through the "fullly backward" setting and immediately jump to the "zero/ full forward" setting. This makes it VERY hard to set the wings on oversweep. Also happens when using the key bindings. Could you please fix this?

Todays open beta update introduced a new and very annoying bug: EVERY SINGLE rotary dial in the cockpit is now broken. When turning them with the mouse wheel, they keep turning through the max value and snap back to zero value. That means, you can no longer simply turn the dials to max. Affected dials are e.g.: The MFD brightness dials and all dials on the UFC. Please fix this ASAP, it's terribly annoying and makes using the Harrier a great pain in the rear.

Thank you so much! I was very frustrated with what I perceived as limited usefulness of the T1/T2/T3 switches. Now you gave me a perfect solution on how to fix this problem! Thanks a lot!

Thanks for the suggestions. I always have bound the "VR Zoom" and "VR recenter" to a toggle switch on my Throttle: Toggling the switch up zooms, and toggling it down recenters the view. However I have to agree with Viper2097: Even zoomed it, it does not get much better.

I just started having the same problem: DCS crashes as soon as the the INS knob is turned from "Align SEA" to "Align GND" the crash files have been sent via DCS. Here is how to replicate: 1) start cold and card 2) make the usual startup procedure 3) turn off parking brake so you can advance throttle, throttle to idle, parking brake on 4) continue until INS alignment 5) Turn INS knob to "Align GND" 6) DCS Crashes. The interesting thing is: I ontice dthat this only happens with certain mission files.... Scratching my head about this problem....

I tried writing a message to him and even got a reply. Let's see what will happen next.