Jump to content

Col. Kernel

  • Content Count

  • Joined

  • Last visited

About Col. Kernel

  • Rank
    Junior Member

Personal Information

  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Another observation that I made during takeoff: If you apply roll trim using the trim wheel (on the left panel) instead of the trim hat on the stick, the trim wheel does not reset during takeoff. However, the trim indicator (the gauge next to the trim wheel) resets to zero during the takeoff roll, so that there is a discrepancy between the wheel and the indicator. Once airborne (or perhaps when the gear is up), the trim indicator jumps back to the same non-zero value as before it reset.
  2. You can set system time exactly the same way by overriding the default values with the ICP keypad and pressing ENTR.
  3. When applying roll trim before takeoff (e.g. due to an asymmetric stores load), the roll trim resets/centers during acceleration with the wheels still on the ground. With an asymmetric stores load, this causes the aircraft to roll at lift-off. I've read in the manual, that PITCH trim centers when ground speed exceeds 60 knots, but this is not mentioned for ROLL trim. In fact, the manual says that roll trim should be applied before takeoff in case of asymmetric loads to prevent wing drop. Usual caveats: I've never flown the Viper IRL, nor do I know the inner workings of the FLCS, bu
  4. Thanks for posting Lace. I also struggled with the MiG-29s and the Sidewinders. The most reliable tactic for me was to stay back in SAM cover and keep the Redfor occupied while having the SAMs take them out. For some reason the Su-25s tended to egress by flying over the Hawk batteries, which most often proved fatal.
  5. I think for some reason that those "Bomb in zone" triggers don't really work for mission goals. Another thing is that it will only test if the bomb is inside the zone at some point - not that the bomb actually hit the runway. As for the latter part, the thread below discusses how to check for runway damage. A bit more involved than what I thought it would be. In any case, the mission scoring isn't crucial, although it is nice to have some built-in battle damage assessment.
  6. Thanks for continuing this enjoyable line of missions Lace. I really like mission 7 because it's so technically demanding due to the low visibility conditions. It takes a lot of precision to line up correctly with the target, and an instrument landing in such low visibility always carries challenges of its own. I've flown it a few times, but never managed to get any points under "Results", even though I've had a good number of hits on the runway. Perhaps I'm being overly confident that they were good hits or perhaps the mission goal triggers aren't working quite right.
  7. You're not doing anything wrong, it's a feature of the mission editor. The list of aircraft is dependent on the task chosen, which can be unfortunate for multi-role aircraft. You might (just might) be able to edit the aircraft in the mission file itself afterwards, but from my experience I would not expect things to work 100%. From the DCS manual (page 124): http://cdn.akamai.steamstatic.com/steam/apps/223750/manuals/ED_GUI_Manual_EN.pdf?t=1509720393
  8. I had those errors in my logs too, when DCS suddenly started crashing. For me it has helped to roll back Windows Update KB4589212, which was installed on my rig earlier this week: https://forums.eagle.ru/topic/270049-windows-woes-random-ctd-fixed-by-rolling-back-win10-update-kb4589212-intel-microcode-update/?tab=comments#comment-4646556
  9. In case it can help anyone: In late March my otherwise fairly stable rig suddenly had massive stuttering and random crashes in DCS. I went through the usual process with mods, repairs, removing OC's and what not. I finally figured out that Windows Update had installed a number of update packages around the time the problems had started. Rolling back these updates restored stability. After a month of stability I suddenly started getting random CTDs in DCS (now version 2.7) again earlier this week. Sometimes with an error log, sometimes without a log. The error log would
  10. Well, color me impressed! Thanks for the very solid update! Performance is good... and those clouds... I first loaded an Instant Action mission for the Viper on the Caucasus map. A thin layer of clouds, which looked a bit pixelated and ok-ish, but nothing more. I then loaded up the mission editor and tried a preset for broken clouds. Immediately impressed with the perception of depth of the clouds and I had an enjoyable time zooming around from cloud to cloud. I finally loaded up a preset for overcast and rain and added some wind to the mix. Mind blown! The rain sounds, the claustrophobic
  11. Hi Florence. I've been making progress in the campaign and just wanted to provide feedback on what I've experienced so far. I like the campaign and am determined to play it through. I've come to enjoy the repetition in each mission, making it just another day in the office. Mission 3: In mission 4 and mission 8 you kindly provide a hint that you should check/change the laser codes. You could add that hint to mission 3 as well, since that will be the first time that the player encounters the 1687 code in the campaign. I learned the hard way, when playing through mission 3.
  12. Think I made it work. Used the previous non-crashing dxgi.dll (after reading Brainfreeze's reply) and now the new settings for radius and SingleImage turn up in the menu. The sharpening wasn't right at first, but switching SingleImage off made it work. The new radius setting works too - confirmed by setting it to a very low value. So far the performance improvement is minimal (with the default radius of 0.5). The previous version had a frametime impact of about 0.8ms - this one about 0.6-0.7 in the same scenario, so could be measurement error.
  13. Looks promising, but I haven't been able to make it work so far either. Like zildag found, the new dxgi.dll crashes DCS on startup.
  14. Windows Update installed some system updates (KB4589212, KB4601154, KB5001567) around the 20th-21st March on my rig, which led to stutters in DCS VR. The stutters disappeared when I rolled back the updates. As impalor suggests, try looking at the update history. In a different sim, there has also been quite a few reports on degrading performance in VR with some of the latest NVIDIA drivers
  • Create New...