Jump to content

Shiroka

Members
  • Posts

    196
  • Joined

  • Last visited

Everything posted by Shiroka

  1. Try this: https://www.digitalcombatsimulator.com/en/files/3311626/ Not my work. When I downloaded it I played with the modified lua files so it didn’t change the mfds, just the AMPCD.
  2. Hey, yeah sorry I never got round to sending you the file - been crazy busy at work. Glad you figured it out. Yeah that’s the only problem, the speed brake doesn’t auto retract. I’ve just learnt to deal with it now, and it’s part of my landing procedure to manually retract it. Maybe someone smarter than me can figure out a better way of doing it - I thought about using the other button on the left throttle (the 2 way momentary press up and down) as that’s more like how it functions IRL (I believe) but I decided against it for consistency between modules (plus I need that switch for other stuff). Obviously my lua file is essentially assigning a digital function to what is really an analog switch so it’s a bit of a fudge. Maybe you could use one of the levers on the bottom of the throttle too (though personally I like having the speed brake on the throttle itself)? Options to think about anyway!

    1. GremlinIV

      GremlinIV

      Hey Dude me again Just bought me a AV8BNA Harrier - and guess what it has a funky airbrake control that my x56 doesnt like when i use the SLD switch unless i use the Delay method like i had on the F18.

      (only 3.5 seconds this time cos its slow)

       

      anyway was wondering if you know any code trickery for the default joystick file for the Harrier.  It looks completely different from the F18, has no equals this and that etc, and it also seems to be an icommand not a Hotas_command.

      Im assuming the icommand is an axis thing maybe.

       

      I havent tried just adding your line to it as the name has changed to airbrake from speedbrake etc, so it is clearly different.

       

      Not sure if you know of a fix like the f18 one or have the knowledge to know how to make one, but if you do id appreciate it.  Fumbling with a 3.5secs delay for airbrake out and then often it not retracting unless you cycle another 3.5 seconds is a pain....

       

      Thx

    2. GremlinIV

      GremlinIV

      Ahhh lol no mind i fixed it - seems stt software was playing up i had used the f18 profile and edited it to the av8 i deleted the delay on the sld but seems sttt wanted to keep it in the background - a few deletes and computer on off got it to accept that wasnt what i wanted it to do and let me delete it and just a a B and a B in it which now works -

       

      Also the harrier airbrake is weird anyway as it sticks out on the ground and when in landing config - but i wil work that out lol - got rid of the delay again so all is well

       

  3. Which one did you try? The top one definitely works as I use it myself. I set it up that way to be as close to the real movement as possible (where rear = extend and forward = retract). I’ve done similar on all the planes I own (hence why I made the mod) and they all work no issues. If it would help, happy to PM you or @ia_pro1691 my lua file with the modification added?
  4. Sorry, just read that you said you are not that tech savvy so here is the simple version: Go to Mods/aircraft/FA-18C/Input/FA-18C/joystick Open the default.lua file in a text editor (notepad++ works well) Paste the following line in (somewhere after line 7): { down = hotas_commands.THROTTLE_SPEED_BRAKE, up = hotas_commands.THROTTLE_SPEED_BRAKE, cockpit_device_id = devices.HOTAS, value_down = 1.0, value_up = -1.0, name = _('Speed Brake Switch - EXTEND/RETRACT'), category = {_('_Custom'), _('HOTAS')} }, Should create a new binding you can map in the controls setup called "Speed Brake Switch - EXTEND/RETRACT", just map it straight to the X56 slider, no need to mess about with the Logitech software. Currently set up for aft = extend, forward = retract, if you want to change the order (to forward = extend, aft = retract) try this (I haven't tried so no guarantee it will work though): { down = hotas_commands.THROTTLE_SPEED_BRAKE, up = hotas_commands.THROTTLE_SPEED_BRAKE, cockpit_device_id = devices.HOTAS, value_down = -1.0, value_up = 1.0, name = _('Speed Brake Switch - EXTEND/RETRACT'), category = {_('_Custom'), _('HOTAS')} }, You'll have to do this each time you update DCS unless you use a Mod Manager!
  5. https://www.digitalcombatsimulator.com/en/files/3312384/ haven’t updated this to 2.7 yet but for the Hornet I believe it should still work. If not just copy the line I added near the top of the included lua file (line 8 or 9 I believe) into the same file in the 2.7 file structure (the mod is OvGME ready so you should be able to pick up the file structure from that). That should let you bind the X56 slider to a 2POS airbrake. It’s currently set up for forward = retract and aft = extend but you should be able to tweak it fairly easily on a text editor to work the other way around.
  6. Thanks for the response. At least I know it’s not me doing something crazy. Great to know you are looking at a solution though, at worst it’s a very minor annoyance, and not dampening my enjoyment at all!
  7. The clock doesn’t show the right time (whether you set it in the ME to Zulu or Local). I reported it back about 6 months ago, Razbam said in a changelog that they fixed it (they didn’t) and moved it to resolved, I re-reported it a couple of times when patches still didn’t fix it. Maybe I’ll re-report it when it’s still not working in 2.7 if I can be bothered (I’m not convinced this bugs forum is monitored anymore).
  8. So I'm really enjoying this campaign (much more than I thought I would tbh) - my only problem is for some reason the finger lift button isn't working (the one that acts as an AB detent), i.e., if I push too far forward on the throttle it automatically goes into AB without needing the button. This doesn't happen on any other mission or campaign (where the button is required to push it into AB), but for some reason on all the Rising Squall missions. Am I doing something wrong? Keep burning through fuel when I am accidentally in MAX not MIL.
  9. Is the dispenser still in standby (at the top of the MFD)? One of the OSBs along the bottom of the MFD should switch between MAN/SA/AUTO
  10. Try rolling back SteamVR to the lkg version (it’s an option in the betas tab) rather than the beta. That worked for me.
  11. Try manually dialing in the frequency. That worked for me on another mission.
  12. So I had this bug, apparently something to do with the way the frequencies are detected. Rather than switch to the JTAC channel, at this point switch to manual and enter in the frequency manually - that worked for me.
  13. Still an issue with the latest OB so I created a new bug report with track files etc.
  14. So I've done some more digging - maybe you are correct and it is working (or my repair and clean fixed it). Anyway, now the selectors are actually there (maybe they were before), but I can only see them on the rare occasion when I am in direct sunlight. You can see the problem in the image below (where stations 3,4, and 5 are selected) - as soon as a shadow goes over them they become totally invisible. Maybe that is as intended? I guess from the image in Chuck's guide in my post above I always assumed they were supposed to be backlit.
  15. You're getting something like this? I get the barely visible dash when not selected, but nothing, just black when selected.
  16. Creating a new bug report as the previous one was moved to resolved a while back and I don't want it to get missed again. The changelog listed this as fixed, it is still not fixed. Created 2 simple missions in the mission editor, both with start time 08:00L (04:00Z). 1) Mission Editor: Clock Time = ZULU This functions correctly, the analog clock (to the right of the ECM/RWR/EXP knobs) shows the correct time 04:00, see track "Clock Time ZULU.trk" 2) Mission Editor: Clock Time = LOCAL This functions incorrectly, the analog clock (to the right of the ECM/RWR/EXP knobs) still shows time 04:00, whereas it should show 08:00. See track "Clock Time LOCAL.trk" Clock Time ZULU.trk Clock Time LOCAL.trk
  17. As described above. This bug appeared a few updates ago but I'm only getting round to making a report now. When you select a weapon station (either on the STRS page or directly on the ASMCI), the red SEL indicators above the button for the selected store type no longer light up. My understanding (and how it used to function) is that say you have GBU-12 in stations 1, 2, 6, and 7, then pressing any of these should select the GBU-12 type and cause all four indicator lights to illuminate. Currently no lights appear. ASMCI.trk
  18. I’ll give it a try again - thought it was way too easy!
  19. So in mission 5, I took off and flew on the correct 330 heading, all 3 wingmen joined me. I didn’t hear anything else (last radio call was about the tower in Batumi) so I flew to the boat and landed as planned and it said mission success. Is that it or did I miss something?
  20. I use an X56. At first I was getting lots of ghost inputs from things I had assigned to levers on the throttle (NVGs/landing gear triggering suddenly). It’s a fairly well known problem with the X56, should be some discussion here on the forums somewhere. Anyway for reference I completely solved this by buying a separate PCI(E) USB board and also a powered USB hub (both pretty cheap on Amazon). Now I connect joystick direct to PCI(E) board and throttle through powered hub to PCI(E), no more ghosting. Could this be the issue? Something like this for the board: https://www.amazon.com/dp/B07Z34BJYH/ref=cm_sw_r_cp_awdb_imm_G0DX6J3GMGAS4MXXZB65?_encoding=UTF8&psc=1 And this: https://www.amazon.com/atolla-Charging-Splitter-Individual-Switches/dp/B07MQDJLSF/ref=mp_s_a_1_1_sspa?dchild=1&keywords=powered+usb+3.0+hub&qid=1613847884&sr=8-1-spons&psc=1&smid=A2KVFO4XQ2RAFL&spLa=ZW5jcnlwdGVkUXVhbGlmaWVyPUFIRkwzUlo0UlhJRTQmZW5jcnlwdGVkSWQ9QTA3MjI4MjUzRExHNEpOVENTVjRMJmVuY3J5cHRlZEFkSWQ9QTAwNDgwOTk5VEZMSjdUWFRXUzMmd2lkZ2V0TmFtZT1zcF9waG9uZV9zZWFyY2hfYXRmJmFjdGlvbj1jbGlja1JlZGlyZWN0JmRvTm90TG9nQ2xpY2s9dHJ1ZQ==
  21. I’m gonna shoot a guess (and this is just a guess): Estimated Horizontal/Vertical Position Error Maybe calculated from the Dilution of Precision in the GPS signal? Don’t know if this (DOP) is modeled in DCS (would be interested if anyone does know)?
  22. So I grew up playing the demo of F/A-18 Hornet 3.0 on our family PC for hours on end. 9 yr old me with a mouse and keyboard (and no clue what I was doing) flying around Hawaii and occasionally crashing into the runway at full speed because I didn’t know how to land. Actually discovered DCS when I was having a nostalgic moment looking for old videos on YouTube and it was a suggested link. Amazing to see how far flight sims have come in 25 years, I echo the thoughts of many in here that the ED team has knocked it out of the park with the Hornet - and the first time I tried it in VR with a HOTAS... I work with computer software a lot, and don’t get easily amazed by fancy graphics on games etc., but I literally had to scoop my jaw off the floor... the immersion is incredible! On the downside, although I was never exactly a big gamer, I will say you’ve probably ruined computer games for me... because I have no interest in touching anything else anymore
  23. from Wags’ post: “In parallel, we are also addressing many bugs and needed and adjustments. We are reading all your valuable feedback. Thank you!” from my reading of it, the list (which looks awesome IMO) is just the “new” features, not the bug fixes. The one thing I’m really looking forward to seeing which I haven’t seen mentioned yet is getting offset functionality working, I really like using waypoint offsets in the A-10 and AV-8B, make CAS a lot easier.
×
×
  • Create New...