Jump to content

trashcan

Members
  • Posts

    15
  • Joined

  • Last visited

Everything posted by trashcan

  1. Good to know that I'm not the only one. Flying helicopters at dusk, dawn, or night is currently very uncomfortable.
  2. About 3 years ago I got my Gunfighter Mk2 with the MCG Pro. I don't think it had to live through "hard use", but it's used often. Everything on that stick and base is exactly as it was 3 years ago. Every button feels the same, every axis has the same precision. Once I had an issue with the X-axis jumping, but that was due to the cable within the base not being fully plugged in. I assume that was my fault, when I changed the cams. After reseating this cable 2 years ago, no issues occured anymore. The Mk2 had a bit of an issue with the rubber dust cover creating too much resistance at near-maximum stick deflection. I ordered and installed the improved dust cover of the Mk3, and that issue has gone away. In general, I absolutely love the base. It allowed me to set it up exactly how I want it to be. I hate it when sticks require a lot of force to move. The Thrustmaster Cougar was a desaster on the desk. It required so much force that it constantly tipped and fell back on the desk, making enough noise to wake up other people. There are a few minor things, that could maybe be better about the MCG: The buttons' switches feel like they are going to last until the end of humanity, but they don't feel like "real airplane" buttons. They are very precise, with a very well defined actuation point, but they don't feel and sound like I'm using a stick out of an airplane. Don't know if any of the competitor products are better, and it's not something I think about when using the stick. (Maybe I'm wrong, I haven been in too many airplanes) The hand/palm rest is oddly shaped, and always at a weird height. When I first set up the stick, I couldn't find a position where the handrest felt natural, where all the fingers perfectly aligned with the finger grooves and the trigger on the stick. I thought this would cause issue during use, but I'm when actually using the stick, I never think about this, and have no issues even after day-long flying sessions, so I assume, it's not actually a problem. tl;dr: no regrets. No wear of any kind after 3 years of use. It will live forever.
  3. Have this problem as well. All other missions seem to work though. Still a very cool mission though, thanks @ElementLT
  4. That bug is really annoying. The A8 is already slow compared to the other fighters, the extra drag doesn't help. Doesn't seem like this is a bug that would be very complicated or time consuming to fix?
  5. No, not just you. It seems that it's gone...
  6. Without touching the editor, because I'm currently not doing anything in the mission editor.
  7. Oh I see, so it has been my fault. Interesting I made it so far without issues. Sorry for the noise.
  8. Hi, I've just noticed issues with the F10 orders (Falke, attack!). While it worked in the early missions (altough I've flown those with DCS 2.5.6), my Wingman/men ignored the orders given with the F10-menu in Mission 11. (even tried it multiple times, had no effect) Just now in Mission 11, the wingman kept following me in formation, even though Spitfires were at his and my six. Only after giving a seperate command via the F2 (Wingman) command menu, he broke off. However, it was already too late then and the menu-fiddling took me so much time that I was in a very bad situation. Mission 9 also didn't really work with the F10 orders. Don't know if it's specific to these missions, or if it's a 2.7 specific problem though. Or am I even doing it wrong, and I'm supposed to give orders one by one via the Wingman/Flight/Second Element menus? Unfortunately no .trk file, as DCS 2.7 likes to crash-to-desktop whenever I bail out or crash...
  9. Think about how much anger ED created when the F-16 early access didn't have external lights. The screaming "first no external lights, now an unfinished external model! It's getting worse!!" would be intense.
  10. Whenever I place a Huey in the mission editor with the "solo flight" option enabled (found under the "..." tab of the aircraft in the mission editor, where you could also unmount the IR suppressor), there is a constant weird sound audible. To me, it sounds like a wiper motor or something like that, even though everything is cold&dark. The sound disappears when disabling the "solo flight" option. Steps to reproduce: open the attached mission file and spawn. Sound is immediately there. hueysyria_solo.miz
  11. For me, flak was no problem. I have been shot down by AAA, but that was absolutely my fault for doing a long, straight, slow run-in trying to strafe ground targets.
  12. I think it's really cool that we got so many voice lines. But as a native german speaker, I would agree. Some of the dialogue at least seems like it was obviously written in english first and then translated to german by a non-native speaker. I don't know the specific terms used by the Luftwaffe in the 1940s, but some seem wrong. E.g. I think they call fighter control "Kontrolle" over the radio a few times. I would assume it should probably be something like "Leitstelle" or "Kommando", because "Kontrolle" usually has a different meaning (at least today). Of course I could be wrong here, german military always had a weird way with words... Anyways, it's easy to see past these minor quirks, the voiceovers still add a lot to the atmosphere and immersion, because most of the dialogue actually sounds like how people in the 1940s could have talked. Overall, it really is a great campaign, well done. (The new damage model also makes it so much more enjoyable.)
  13. Have noticed this as well on the Syria map in singleplayer. Zoom in, point mouse at a certain landmark, note the coordinates. Zoom out, move map around, point mouse at the same landmark again: it now shows different coordinates. Edit: But I think this is the wrong sub-forum...
  14. Since DCS at 2160p looks pretty ok without MSAA, I don't have MSAA turned on. I can't afford it performance-wise.
  15. What kind of information do you need? I still have this issue. It doesn't bother me too much when dropping GBUs from 30000ft, but recently I'm flying a lot of the WW2 planes, and especially in multiplayer, this issue is annoying. What I can say: It's always a black box on the left half of the screen. It happens on all maps (except Nevada, I have not tried that), and it happens everywhere on these maps. However it's much more frequent when there are large bodies of water visible (lakes, sea). It also happens more often, when looking around. Very rarely when just looking straight on. Altitude above ground does not seem to have an effect. I have only seen it in the cockpit, not in external views. But I rarely use external views, so I wouldn't take that too absolute. Under worst conditions, this happens every 10 seconds. The setup: latest DCS open beta, resolution 3840x2160. I have tried A LOT of different graphics settings in DCS, and could not find one where I felt the flickering would occur less often. The system: Win 10 with all the updates it can get, AMD Ryzen 5 3600, Radeon Vega 64 with latest drivers, 32GB RAM. Please let me know if you need any further information. I'd really like to help solve this issue, because it's really annoying. Also, if there are some workarounds, I'll try those. But I couldn't find anything recent on the 45 pages of this thread.
×
×
  • Create New...