Jump to content

dhevans79

Members
  • Content Count

    103
  • Joined

  • Last visited

About dhevans79

  • Rank
    Member
  • Birthday 08/29/1979

Personal Information

  • Flight Simulators
    DCS 1.5
    DCS 2.0
    FSX Steam Edition
  • Location
    Switzerland
  • Occupation
    Programmer
  1. Do those mods still work/have been updated with the new sound files? I thought I heard recently that the sounds have been "encrypted" through an obscufated folder/filename structure? If they still work, this looks like a mini treasure chest for those that like sound mods [emoji16] Sent from my SM-N950F using Tapatalk
  2. Cheers, that answers the question perfectly. I'll double check by using a voltmeter on the pin to confirm. Sent from my SM-N950F using Tapatalk
  3. Hi all, Just got my basic hardware setup complete and run some tests to check some basics on the Arduino. I note that the arduino supports INPUT_PULLUP to use the internal resistors on the board. Does anyone know if DCS BIOS supports this somehow? I didn't see anything when scanning the documentation. I have the resistors, just thought it was a little more elegant than having to plug them in to the circuit too. Just beginning electronics, so please feel free to correct my thinking if necessary. Cheers to all, and here's to the start of a new relationship with all you home cockpit b
  4. Thank you all for your comments. Given the information above, it doesn't sound like it should be troublesome to use DCS BIOS for my project, and as such I can benefit from all the work that you have all put in to supporting this project. Here's hoping that I'll be able to add to this community in the foreseeable future. Regards, David Sent from my SM-N950F using Tapatalk
  5. Whilst the gesture is appreciated, it's not the point of the question ;) With regards to Blue73 response, if it's only a couple of updates a year, that's ok. If I understand correctly, these are derived from the commands the developers use to control the sim, so I guess these basic function s shouldn't change much on complete modules (guess that's not the case for the F18 yet, due to still being in EA) Sent from my SM-N950F using Tapatalk
  6. Hi all, I'm looking to start building some generic panels that could interact with DCS BIOS. My question is whether I plan to use DCS BIOS for the advanced functionality , or whether I just build some generic button boxes mapped via the standard and limited controls to reduce "tinker time". My main worry is whether the DCS BIOS commands/module regularly break with the updates from ED, or whether the system is more or less stable over long periods. I want to be able to play the sim, rather than reflash and reprogram commands due to each update made by ED. So as a general question to a
  7. I dont see that reference for dcs 2.5 in the OP. Maybe I misunderstood, but that meant the level of detail in the textures. To redo the textures for 2.5 is not just a re-release, but a whole placement issue from the start. ED had to do a lot of work to keep the old missions working. I don't think it's a case of simply overlaying the textures on to the new mesh... Sent from my SM-N950F using Tapatalk
  8. Hmm, not sure on that last point... I just set up a mission last night for jtac with m2kc. I did basically the same thing, only setting the radio frequency to 135mhz and I did NOT set a laser code. After learning to follow the conversation through to 'IN' and targeting the bomb ahead of the target to the sensor was finding the lase during the descent, I reran the mission at least 5 times with perfect hits each time... This was on 2.5 main (not beta) Sent from my SM-N950F using Tapatalk
  9. Sorry to maybe be a pain in the ass, but I would prefer the mentioned approach of a snippet generated from a full flight recording. The events we wish to review may not be part of the planned offensive and may be missed if we manually start and stop the recording. In any case, I've loved using tacview since I found it and am very pleased with how you maintain it. Keep up the good work and thank you! :) Sent from my SM-N950F using Tapatalk
  10. I've been using the mouse stick as buttons, using the stick without pinky for TAD slew, and with pinky up/down as airbrake, fwd/back as china. The only problem is that as soon as you need to use SST for anything, DCS 2.5 doesn't recognise the pinky button (#6) any more as a modifier, so that means I have most of the commands in DCS, and any pinky modified switches in SST. A bit of a bummer, but that's the best I found. Otherwise it's to use the start/stop buttons just under the throttle, but I found those being a bit difficult to use, as I would need to look at the throttle to find them,
  11. Yeah, after spending a whole 30 seconds looking at the buttons, changing the contrast to my desired level works very nicely. Thanks for that tip, wouldn't have thought of it myself. That, and massively reducing the brightness has really improved the image output. THANKS! Sent from my SM-N950F using Tapatalk
  12. Yeah, I tried that a while back with no real results. It updated the gamma slightly and shifter the colours to a slightly colder temp, but nothing major. Was probably worthwhile to do it in any case, to start from a good reference point. I had the same problem with the overblown tad colours in 2.2 but spent most of my time in 1.5 so didn't really spend much time trying to correct it. As it doesn't seem to be a major issue on the forums, I'm placing a solid bet on my monitor setup so I'll have to spend some time with it and see if I get similar results as the OP. Or just adjust to the new
  13. I've noticed the tad in the a10c looks "strong" so I can't really read it clearly. Is this something that was resolved by your monitor tuning, or you don't fly this plane much / not your focus... Sent from my SM-N950F using Tapatalk
  14. Wow, this is the top tip of the week. Didn't know it would do this! Sent from my SM-N950F using Tapatalk
  15. Wow, that was a roller-coaster ride from start to finish.. Sent from my SM-N950F using Tapatalk
×
×
  • Create New...