Jump to content

jstnj

Members
  • Posts

    54
  • Joined

  • Last visited

Everything posted by jstnj

  1. A few of the missions (I think 5 is one of them), the runways for takeoff and landing conflict with each other. Sometimes, the rest of the flight will take off on runway 09, while you are given taxi directions to takeoff in the opposite direction (27) Sometimes, you takeoff runway 09, and even though the winds are the same when you finish the sortie, your landing clearance is for rw27 In aviation, including in most military operations that im aware of, the prevailing runway choice is typically made based on takeoff/landings being into the wind. I am assuming you made some of these choices to make rendezvous easier, but as far as being "true to life" typically there is only ever ONE active runway, and you'd never takeoff or land in the opposite direction of traffic because it would be extremely dangerous. Anyway, love the campaign overall, thanks for all the hard work!
  2. multiplayer does not complicate this at all. The local "sandbox" of weather must to be the same, yes... but its fine if one player has a gust decoupled from another. That's perfectly fine compromise. MSFS and even Xplane 11 has been doing this for years on hardware a decade old.
  3. hate to bring this thread back from the dead but: The movement controls (cockpit view up, left, down) dont seem to work for me. I use a Tobii EyeTracker 5, and I'm trying to set the default cockpit view to look more up toward the horizon but I'm not sure which file to edit. Ive edited View.lua in savedgames, within DCS root, and seemingly edited vAngle for the a-10 anywhere i could find it...but its not working I'm at a loss and desperate for clear instructions.
  4. Disabling eye tracking in Tobii Game Hub settings for for some reason doesn't work correctly (your eyes still slightly influence camera direction and its very annoying). Hot tip for anyone wanting to turn OFF eye tracking but keep head tracking: Keep eye tracking ON in Game Hub, but: Turn Responsiveness, Yaw Limit, and Pitch Limit all to 0 (all the way down) within the Eye Tracking section. This solved the issue for me.
  5. I appreciate it One more question: I can easily extract the contents of these files, but I cannot seem to update contents within the original miz..is there a trick to that? I tried 2 strategies, neither work: 1. Open miz in 7zip, right click mission file and "View", edit the data and then try to save it inline within 7zip 2. Open miz in 7zip, extract the missions file, edit it in Notepad++ and try to overwrite the original using 7zip Both result in "Access denied" Maybe something changed about the encryption, or maybe I'm just doing something wrong..
  6. A little confused by your list...I'm not sure it's intuitively describing WHAT is wrong with some of the items, it just seems like a list of lights and switches. (This post is in the interest of getting them fixed, the easier it is for ED to understand will hopefully result in a quicker fix)
  7. The intended logic for AI wingmen is assumed to be: After gear up, match the light configuration of the lead aircraft It does this ^ with the exception of the anti-collision lights.* Recreation steps: Cold & Dark start A-10C II with at least 1 AI wingman in your flight Configure lights for taxi and taxi At any point pre-takeoff, flip your anti-collision lights on (Wingman turns their anti-coll lights on) Takeoff, clean up the aircraft, have the wingman rejoin when you level off Turn off lights (middle pinky switch position), Turn off the anti-collision lights on the light panel Notice that the wingman turns off the Nav lights, but the anti-collision lights stay on I am assuming this isn't just an A-10 issue, but I can only speak for the module I own. Its especially immersion breaking on night missions where you are fencing in and trying to go to the IP covertly, but your wingman is having a disco rave at your 3 o'clock. *I'm not actually sure of this, ED should look through the lights logic to ensure that the entire external light configuration of the aircraft is considered in order for this bug to be called "fixed". --- Edit: This is a 10 year problem, can it be looked at?
  8. TIL miz files are a compressed filetype and not some proprietary ED thing. Thanks
  9. Hey thanks for making me aware you can edit the mission data....when you say the "mission file", what file is that? I tried viewing the .miz files in Mods/Campaign/A-10C Operation Persian Freedom/ in Notepad++, but theyre clearly not the files that need editing.
  10. Ah, i was wondering why I had laser vision through clouds
  11. I need this for the A-10C Thanks for the contribution regardles
  12. I tried to restart the campaign on latest open beta and Mission 1 Ground/Tower frequency doesn't work so, I always fail the mission. Unless I'm misunderstanding the ARC210 directions I should be tuning 131.5 on the 210 and 260 AM on the regular radio?
  13. Anyone heard from them? I'd be willing to pay for the stl file and get them printed for my own personal use.
  14. I fly everything including MSFS aircraft with mine
  15. I would agree with you if it wasn't for the fact that the A-10 has been off ED's radar long before the Russian hostility began, unless you count the annexation of Crimea in 2014
  16. You better not release a great campaign for the A-10 and force ED to pay attention to this module after neglecting it! How dare you Jokes aside, looking forward to seeing what this turns into...and hopefully it does have an effect on the A-10II development
  17. Any improvement to the A-10 would be a happy accident since ED have clearly put it on life support, priority-wise.
  18. As an example, the radio listed in the initial features for the Tank Killer expansion (2 years ago?) isn't being prioritized because of "lack of dev time"...and we can't check in on it because the thread was locked. This has happened for a few elements of the aircraft. I'm sorry, but why is this in the "wishlist" section of the forum when we shouldn't have to "wish" for it at all? The only "feature" the A-10 II has gotten in the past year is the new FLIR implementation, but: That's only because of the development on the Apache module, and It clearly wasn't tested before release, because the temperature polarity is reversed on every module that uses it (besides the Apache, of course) I'd prefer that ED just give it to us straight: should we expect any attention to be paid to the A-10 II? Sorry to sound impassioned, but I have been peeking at the release notes over the past 6 months and the A-10 II has gone completely unmentioned. It feels completely neglected.
  19. Important to note that if this is the experience in DCS, it's not how it should be. There is an auto-lase setting you should be able to configure. As long as the laser is enabled it would lase within the x seconds setting you set. Is a feature of the SNIPER and older generation TGPs as well IIRC. Definitely should be working in a blk50
  20. I've also been waiting for it in the A-10II...crickets
  21. ED hasn't built it yet, but IRL you do it through the UFC CRUS page.
  22. Not true. Depending on prevailing atmospheric conditions during a flight, ice crystals can form in the tube despite not meeting this criteria
  23. It is my understanding that AI wingmen/women should match the flight lead's light configuration. I am playing the Piercing Fury campaign and on the night missions I'm noticing they are chilling in orbit around AAA like a christmas tree, NAV and formation lights all on... This doesn't seem to be working as it should. Maybe it's already known? Running latest open beta.
  24. Yeah I just got it to work by restarting. Seems unreliable but, at least it's working now. Thanks Taz
×
×
  • Create New...