Jump to content

mauzer

Members
  • Posts

    8
  • Joined

  • Last visited

Personal Information

  • Flight Simulators
    DCS
  • Location
    Sweden
  1. I think I saw someone (RagnarDa?) saying the crash after the final mission in The Mjolnir Response was a DCS-issue. Maybe this is too. Anyway, I tried it again today. I quit the mission right after the completion message was shown, and that did the trick! Of course, I can't be 100% sure it wouldn't have worked this time even if I taxied and shut down correctly. After all, this time radio comms with ATC worked, which it hadn't for the last 4 or 5 missions before. Maybe there was something else that triggered the crash...
  2. Just finished the new campaign, and it was great fun! However, like the mini-campaign, it crashed on completion of the last mission. I have tried it twice now with almost the same result. The first time it crashed after landing, as I was about to exit the runway on taxiway C. The second time I got a message saying that the campaign was completed and the theme tune started playing (while still rolling on the runway), and it froze and then crashed after that. Campaign is still displayed as Active. Maybe it could work if I quit the mission while still rolling, right after the completion message is shown. Will try again tomorrow.
  3. You're absolutely right! I normally end up with a QFE of just above 1012. When I set it to 1010.6 as indicated by the kneeboard the bombs fall short. It feels very touchy, but I guess that type of weapon deployment would need a very accurate QFE setting. Adding 2 hPA seem to be an ok workaround for now, but I agree this should be looked at by the devs. Thanks for helping me improve my CCIP bombing skills! :thumbup:
  4. Weird! I experience the same thing in the CCIP training mission (half of the bombs fall short), but when I fly the Instant Action mission "Offensive Counter Air" practically all bombs are on target. Only one bomb falls short when I press the trigger as the dot passes the closest target (tried a bunch of times now). I don't understand why I get different results in the two missions. I also get the fragmentation and arming warnings in both missions. It is still possible to release the bombs, they all seem to arm fine and there's no fragmentation damage. --- edit --- I didn't correctly set the QFE in the Offensive Counter Air mission. I set the QFE so that radar and barometric altitudes matched when lining up for the target over the sea. When setting the QFE to the value indicated by the kneeboard the bombs fall short in that mission too. Adding 2hPa to the QFE seems to do the trick in both missions, as veenee states in the "Dive bombing bugged?" thread.
  5. I have tried that same mission a bunch of times now using PLAN in both NAV (CCIP) and ANF modes, and I manage to hit the targets pretty consistently with the same release parameters as you (100m, mach .9). I set the QFE by making sure barometric and radar altitudes match while over the water. I guess the target may be a few meters above sea level, and my QFE would be off by an equal amount. Could that make such a big difference? I'm running the latest open beta by the way, and I assume you are too?
  6. The game reports wind different to how it is displayed in the Viggen. In the mission editor and mission briefing (and, I assume, the kneeboard) wind speed is in m/s and wind direction is where the wind is blowing to. In Viggen, wind speed is measured in km/h and wind direction is where the wind is blowing from. So indicated wind in Viggen should be roughly 180 degrees off compared to what you see in your kneeboard. Does that make sense? I just did a quick test and it seems to me that wind is displayed correctly in both multiplayer and singleplayer. Also tried dropping some BK90's, and they seem to be dealing a lot better with the wind now. The submunitions still drift a bit off target though, but I guess that may be pretty realistic.
  7. The wind direction in the mission editor is the other way around, which may very well be the origin of much of our confusion. It shows the direction where the wind is heading. There is a small arrow indicating the wind direction and if you input 90° in the ME, the arrow will point to the east. The CK37 in Viggen will then be indicating a wind direction of 270°. You should be able to verify in the ME if the arrow points towards the north (and 12° west) for your custom made mission. The indicated wind in CK37 should then be close to 168°. If so, the ATC would be right in sending off planes on rwy 09. Any wind direction between 4° and 184° should be OK for rwy 09.
  8. Agreed, wind correction is backwards in Viggen. @alftand is correct, however, about how wind is displayed in VIND/RUTA/MAL. Specifying the direction the wind comes from is how it is done in weather forecasts, which makes it natural to represent winds the same way in the aircraft. I set up a practice mission with a strong wind from west to east, and Viggen correctly displayed the wind direction as 270°. The steering command in the HUD also seemed to be working as it should. When heading south, I would see very similar symbology to what is shown in OP's screenshot. The nose would have to point a few degrees into the wind (to the right for both OP and me) for the airplane to hit the waypoint. I also experimented a bit with bombs and BK90's in the same weather setup. Bombs in PLAN mode (both with and without chutes) and BK90's all fail to hit the target unless I manually enter a wind direction 180° offset from the actual direction (in my case 90° instead of 270°). Unless manually entering the opposite wind direction like that, the HUD symbology in PLAN bombing mode directs you to drop the bombs on the wrong side of the target seen from the wind. In my case the steering order directs me to the east (left) side of the target. Even when entering the opposite wind direction, I found that the bombs would not quite hit the target spot on, but if I also doubled the wind speed they would hit a lot more accurately. Same thing with the BK90's. Not sure those results are very relevant though, since I was flying in silly hard winds (12 m/s).
×
×
  • Create New...