Jump to content

Smashy

Members
  • Posts

    144
  • Joined

  • Last visited

Everything posted by Smashy

  1. Try playing around with MIDS SETUP page. You can get there from the HMD format page. Experiment with increasing range with PB14 and see if that helps.
  2. Honest question - given the info in the FAQ, can you provide detailed info on the massive MP problems you anticipate?
  3. I'm just starting up with the Apache and if I have to be honest, George as pilot or CP/G isn't terrible. The interface is clean and concise and does about 80% of what I need. He obviously isn't as good as a good human crewmate but he is probably better than a lot of randos you'd find on some of the busier MP servers.
  4. I'm having problems getting George to launch a Hellfire in LOAL HI/LO. I'm guessing it's because I can't get him to switch his acquisition source to a point from the nav database so the target is always out of constraints. Is this just the way it is? It's not a huge deal but just something I'm curious about after fiddling around with it a bit this afternoon.
  5. I have no idea but I'm now following this Hannibal Lecter-level topic.
  6. Once you get the seat and head position dialed in, you can save it to a snapview. By recalling the snapview, boresighting takes a few seconds. To save a snapview: LWin + Numpad[1-9] then RAlt + Num0 to save To recall the snapview: RCtrl + Num0 then the Numpad key you used in the previous step
  7. Is the Apache manual being done by ED's dedicated documentation team that was mentioned in the recent past? Whoever is working on it, amazing job. It's very well done and a clear improvement over some of ED's past manuals.
  8. Serious question: why do people like you take the time and energy to look for problems and then make snarky comments in a way that is clearly non-constructive when there are so many things about this game to learn and enjoy? It's not as if you're conducting methodical tests to provide useful feedback to ED. Instead, it's almost as if you make a conscious effort to find faults and not have any fun. Life's too short for that and I truly wonder what motivates posts like this.
  9. One possibility is you have a modifier+axis bound to UHF volume. Did you check your axis bindings?
  10. Brilliant list, thanks for sharing these @wilbur81! I'm adding these to my podcast playlist. I'm always excited to fly the Hornet and listening to these kinds of interviews just feed that stoke. The way internet gladiators bash on one module or another in that "my dad can beat up your dad" fashion strikes me as extremely immature. It's boring to hear Viper guys bash the Hornet or vice versa. It's a video game and meant to be fun. Sure I have my favorites (Hornet, Huey, Mustang and now the Apache is growing on me) but all the modules I own have something to offer.
  11. Will the ability to have multiple versions still be supported once the unified release hits? I use OB (with minor mods and add-ons) as my primary but keep a clean stable install to troubleshoot and test things if I run into problems to help determine if the problem is on my end or not. It would be nice to be able to do this going forward, if not with stable at least with a previous version.
  12. I played with this last night and you are correct. My mistake!
  13. I'm not sure if this is the optimal solution but this fixed it for me: Edit <DCS base dir>/Mods/aircraft/Uh-1H/Cockpit/Scripts/AI/ControlPanel/g_panel_page.lua Find the following line (appx line 42): local shift_X = -0.65 Experiment with the value to position the AI crew panel to where you like. My multi-monitor configuration has a horizontal resolution of 6144 and changing this value to "-2.80" put the AI panel where I wanted it. It will get overwritten when you update/repair DCS so save it in a safe place or look for it in <DCS base dir>/_backup.### to find it again. Hope this helps.
  14. Right on, I'm doing something very similar as well. It's an acceptable workaround but can sometimes get clumsy switching between RWS/TWS to get the bar setting changed.
  15. Can bar scan values be cursor-bumped like range and azimuth values?
  16. Is it easier to accurately simulate older aircraft, avionics, sensors and weapons when compared to a newer platform? For modules like the Hornet, F-15E, and Apache I imagine a lot of details are fudged over either intentionally or because reliable unclassified data sources simply aren't available. Would this be the case with the F-4E? As awesome as the Phantom looks, it's even more exciting to think HB would be delivering as accurate a sim experience as possible. Do unclassified data sources exist for a platform as old as the F-4E?
  17. adding dxdiag.txt and dcs.log per @BIGNEWY's request. My primary problem is a constant flickering like a bad fluorescent bulb. This happens in the 2D GUI as well as in-game. Often, a faint ghost image of a previous screen can be seen while in game(i.e., grid lines from F10 map, briefing window, options page). This doesn't happen on any other games I've tried, including an older stable version of DCS. dcs.log DxDiag.txt
  18. I'm seeing the exact same issue. The flickering is so fast and so severe, I'm grateful I don't have epilepsy. It's apparent on various 2D screens in the GUI. In game, it's also noticeable at points of high contrast (i.e., horizon line). It does not happen in an older stable version that I happened to have installed. I've also tried experimenting with various settings but nothing has helped so far. RX 6800XT (23.10.1 drivers)
  19. Did a cleanup and slow repair but did not remove mods listed above. The pipper was still behaving erratically. Instead of trying to troubleshoot my current install piece-by-piece, I decided to go with a fresh download of the stable release and test on that. Got a freshly-downloaded stable install done, installed the Hornet and Syria, and setup a simple test against a Flanker. The pipper starts jumping around once the Flanker starts maneuvering. It's especially noticeable when the Flanker is rolling side-to-side. No mods, no changes to default except importing my HOTAS binds from my beta install. Here's the track from this test. The random guns shots were just me trying to see what the BATR cue was doing. Hornet pipper test.trk
  20. I appreciate the look. Sorry I forgot to include version and mod info in my previous post. For anyone curious: OpenBeta 2.8.6.41363, testing in single-threaded Following files have been modified: ./Mods/aircraft/F-16C/Cockpit/Scripts/EWS/CMDS/device/CMDS_ALE47.lua ./Mods/aircraft/F-16C/Input/F-16C/joystick/default.lua ./Mods/aircraft/F-16C/Input/F-16C/keyboard/default.lua ./Mods/aircraft/FA-18C/Cockpit/Scripts/TEWS/device/CMDS_ALE47.lua ./Mods/aircraft/FA-18C/Input/FA-18C/joystick/default.lua ./Mods/aircraft/FA-18C/Input/FA-18C/keyboard/default.lua ./Mods/aircraft/Ka-50/Cockpit/Scripts/Devices_specs/UV_26.lua ./Mods/aircraft/Mi-8MTV2/Cockpit/Scripts/CargoIndicator/CargoIndicator_page.lua ./Mods/aircraft/Mi-8MTV2/Cockpit/Scripts/ControlsIndicator/ControlsIndicator_page.lua ./Mods/aircraft/P-51D/Input/P-51D/joystick/default.lua ./Mods/aircraft/P-51D/Input/P-51D/keyboard/default.lua ./Mods/aircraft/Uh-1H/Cockpit/Scripts/AI/ControlPanel/g_panel_page.lua ./Mods/aircraft/Uh-1H/Cockpit/Scripts/CargoIndicator/CargoIndicator_page.lua ./Mods/aircraft/Uh-1H/Input/UH-1H/joystick/default.lua ./Mods/aircraft/Uh-1H/Input/UH-1H/keyboard/default.lua ./Scripts/Aircrafts/_Common/Cockpit/ViewportHandling.lua ./Scripts/Speech/common_events.lua third-party mods: SRS DCS Scratchpad TacView DCS-ExportScript Helios I'll try the repair and systematically remove mods for testing. I'll report back when that's all done. Thanks again!
  21. Is this still fixed for you? For me, the pipper still appears to follow the behavior of the foresight cue. With a lock on a maneuvering and jinking target, the pipper still jumps around like crazy. Here's a short track where I'm saddled up behind a F1. Notice how the pipper starts moving erratically as soon as the F1 starts maneuvering. Even the BATR (bullet impact) cue is affected even though I'm still straight and level. Additionally, if the radar is in SIL mode switching to guns will take the radar out of SIL mode. I'm not sure if that's working as intended or not. @BIGNEWY can you please take a look at the track? Hopefully this clearly illustrates the problem I'm seeing. If more examples are needed, lmk and I can try to provide more tracks. Thanks. Hornet pipper.trk
  22. You can add the relevant pages to [DCS rootdir]/Mods/terrains/[mapname]/Kneeboard This works great for all maps I have except Syria. I think there's a long-standing bug that affects Syria-specific custom kneeboard pages.
  23. @Minsky - your module and aerodrome kneeboards really are works of art. Thanks for creating and sharing these!
  24. Resurrecting a necrothread but I was just going to dig into this file tonight to do the same thing. I'm glad I found this post before I wasted my time. The first clue was that the default values for the AIM120 in this file aren't applied to a hot or cold started Hornet. Has anyone found a way to do what OP was trying to do in the last year? I'm also hoping for a data transfer cart. Hopefully we'll see something somewhere down the road.
  25. In some of the joystick device diff LUA files, I noticed some interesting names in the name-value pairs found there: ["hardwareDetent"] = false, ["hardwareDetentAB"] = 0, ["hardwareDetentMax"] = 0, These are in the axis section for my new rudder pedals (which don't have detents). Are these old or are they something new for upcoming device support features? Maybe VKB TECS :D?
×
×
  • Create New...