Jump to content

Kenpilot

Members
  • Posts

    199
  • Joined

  • Last visited

Everything posted by Kenpilot

  1. Hey guys. In my simpit for the A10C, I have several external peripherals/controllers such as the Thrustmaster HOTAS Warthog joystick and throttles, Thrustmaster MFDs (2), Buddy Fox UCF, etc. I also have several arduinos and several GP WIZ40s for switches, buttons etc. I'm finally programming everything and binding the switches and buttons, etc. I'm starting to run in to the problem of there being several of the same switch/button assignments with a couple of the peripherals. Such as, the joystick having a Button 1 and the Buddy Fox UFC having a button 1. So when I try to bind one of them, they now both have the same assignment.. I would think since they are two totally different peripherals/controllers, it wouldn't matter if they both have a button 1, they're a button 1 on the joystick and a button 1 on the UFC. Is there a way around this or to help the computer understand that they are two different controllers or maybe rename the buttons on the controllers so that I only have one Button number for each button and switch? Thanks for any help!
  2. Awesome, thanks so much guys. Unfortunately I won't be at my simpit and computer for a little bit to be able to test everything out. I was supposed to be working on it when I posted this but got pulled away for stupid work. Damn adulting.
  3. I have an OLED display for the Chaff and Flare counter on the A10C Counter measures panel on the main instrument panel. Is anyone else using this setup with an arduino and have a sketch I could use? I thought DCS Bios would have it but apparently it doesn't. Thanks!
  4. I don't think I'm going to use a matrix but if I do, I'll definitely use this! Thanks!
  5. Hey guys. I'm fairly new to the arduino world and DCS Bios and I'm building a CDU for the A10C. Obviously the CDU panel uses a lot of tactile buttons for the panel and I know typically you are supposed to use an external resistor when wiring a button, but that would be A LOT of resistors for the panel. I've read where the arduino has sort of internal resistors where you can program the input pin to use these "internal" resistors so you don't have to wire a bunch of external resistors. Does anyone know how to include this program language in to the DCS BIOS program language for the CDU buttons? If anyone has built their own CDU panel using arduino, DCS BIOS and the internal resistor programming language for all of the buttons, could you please copy and paste your program so I can use it? Or at least see how to write it? I would greatly appreciate it. Obviously I might have to change the pin numbers depending on which arduinos you use, I know how to do that, I just don't know how to incorporate the arduino internal resistor program language with the DCS BIOS language. Thanks!!
  6. For those of you who 3D print your own knobs, how do you paint them for backlighting? Do you tape off lines and arrows and then spray paint them? Do you hand paint them? I've tried printing some using translucent PETG and taped off small lines and arrows on them and spray painted them but it comes out looking like crap, and trying to tape and then cut straight lines and tiny arrows on the knobs is super annoying and not the easiest task. How is everyone doing this? Thanks!
  7. Roger that, thanks for all your help! Definitely going to be keeping an eye out for the 3080.
  8. Ha! You ain't kidding. Looks like I'll be on the lookout for a 3080, wish me luck!! Do you think overclocking my CPU will help much or should I just leave that alone?
  9. Thanks for the feedback. 3 years ago when I got my GPU, the 1080 ti was one of the best out there. Do you know if the 3080 or 3080 ti is worth upgrading to from the 1080 ti? Again, if I can even get my hands on one.
  10. Hey guys, I'm looking to get the best possible performance and graphics as I can while playing DCS. Who isn't right? It's pretty good as it is now but I'd really like to be able to turn all the graphics on HIGH and add all the extra stuff that really makes this game shine. I'm a graphics snob so I want all the detail possible, but of course, I want my cake and eat it too so I want the performance to be smooth as can be as well. Here is what I have in my PC now: Motherboard - ROG STRIX Z390-F GAMING CPU - Intel Core i7-8700K Coffee Lake 6-Core 3.7 GHz (4.7 GHz Turbo) LGA 1151 (300 Series) 95W BX80684I78700K (NOT OVERCLOCKED) Memory - Corsair Vengeance LPZ 32 GB DDR4 DRAM 3200Mhz Hardrive - Samsung 960 EVO 500 GB SSD GPU - EVGA GeForce GTX 1080 Ti SC Black Edition GAMING, 11G-P4-6393-KR, 11GB GDDR5X I'm also using 2 Benq HT2150ST Projectors on to a 180 degree curved wide screen that I built. Yes, I know I'm not going to get as good as graphics and performance as I would on let's say a gaming monitor, and that's one of the reasons why I want to be able to max out everything so that I can get it to look as good as I can. Is it worth it to upgrade any of the hardware that I have now or should I just keep what I have and wait for the newer processor or GPU to come out? If I can actually get my hands on one that is. As far as overclocking, I've never done it before. I'm sure there are plenty of videos and how-tos on youtube these days, and I'm not afraid of trying it if you guys think it would make that big of a difference in what I'm looking for. Thanks for any help and suggestions!!
  11. I have the same setup as you, 2 projectors displaying on a 180 degree screen and using Fly Elise. I can't get mine to display properly either. Were you ever able to get it figured out? I used the exact .lua that is exported with Fly Elise and I selected it in the DCS settings under Monitor, and the resolution is 1920x1080, with an aspect ratio of 1.33333. I'm sure it has something to do with either the selected resolution or something in the .lua file that is exported.
  12. Thanks for all of the help and suggestions guys, I greatly appreciate it!!
  13. Do the A10 CMSP and CMSC panels need 16x2 or 20x2 LCD displays?
  14. Les, thank you so much!! This looks like it should get me on the right track. I agree, without so many awesome forum members on here, I would be completely lost with most of this stuff and I definitely wouldn't have a simpit, at least not one that would work! Thanks again so much for taking the time to explain all of this, it's exactly what I needed. I'll let you know if I run in to any issues or post on here. Hopefully one of these days when I'm more well versed in this stuff, I'll be able to pay it forward on here as well. Thanks again so much for your time!! Agrasyuk, thank YOU too!!
  15. Ah ok, didn't know there was a difference. Thanks for the info!! I'm needing LCD displays for the A10 CMSP and CMSC, so I just need letters and numbers Displayed. I was just looking at your thread that you posted and it looks like it might help me with all of the other panels that I'll be using LCD displays for, ILS, Radios, etc. Only problem is, when I started reading thru that post, my head started to spin. I'm very new to arduino and DCS Bios, and completely new to LCD displays, so I have no idea what I'm doing when it comes to those. I have a 3rd grade knowledge when it comes to Arduino and DCS Bios as I have used them for my landing gear panel, hydraulic/fuel gauge panel/fire T handles, indicator lights and the caution panel. So needless to say I know how to use them for LED's and switches, but haven't messed around with displays yet. If anyone knows of a LCD display for dummies and their use with arduino and dcs bios thread or how to, please let me know! Like a step by step, you need to buy this display (include link), you need to hook it up to the arduino like this, and then you need to go in to dcs bios and arduino IDE, etc... you get the point. Thanks for any and all help!!
  16. Hey guys, I'm getting to the part of my A10 pit where I'm needing to start installing displays. I'm starting with the A10 CMSP and the CMSC. I have no experience with these things and was wondering if there are any tutorials or DIY explanations on which ones I will need and how to wire them up and then code them? After some research, it looks like I need a couple 20x2 OLED displays for these 2 panels, but there are several out there. Anyone have any suggestions or links of that they've used? If it helps, I'm using arduino megas. Thanks for any help or guidance!
  17. Do they allow for 360 degrees continuous rotation and in either direction?
  18. I'm new to using rotary encoders and was wondering which ones I need for the Heading and Course knobs on the HSI for the A10, as well as the Attitude Indicator. I'll be using them with arduinos. Thanks!
  19. 3 times what will get me the 20 full flap degree?
  20. After going back and looking at the arduino sketch, mine looks nothing like yours. Did you get that sketch from the DCS Bios control reference for the A10? Or did you create that sketch on your own?
  21. So I tried what you said and I figured out the 0 and 90 point us numbers for the flaps gauge. They are 1325 and 1770. That gives me the 90 degrees of travel from 0 degrees flap position indication to 30 degrees flap position. Now what? Cause right now with those numbers, If I select flaps to 10 degrees, it goes to 10 degrees, but when I select flaps 20 degrees, it goes all the way to flaps 30 degrees indication, when the flaps are actually at 20. I'm totally lost.
  22. Thanks for the response! That's my problem, how do I figure out the 0 and 90 point us numbers??? Do I just randomly guess two different numbers and check it? This will take forever. I have tried a couple different people's servo settings from their sketches and none of them have matched the gauge in DCS. I don't think I'm understanding the whole concept of the microseconds and the 0-90, etc. Maybe I'm doing it wrong but I look at it like this: A servo travels 180 degrees. The flap position indicator for the A-10 travels from the 3 0'clock position (0 degrees of flaps) to a full flaps (30 degrees) 6 0'clock position. To me that is the 90 degree position to the 180 degree position. I have found two numbers that make it go from the 0 flaps position ( 3 o'clock/90 degree position) to the 30 degrees flap position (6 o'clock/180 degree position) but when I select flaps 10 degrees down from 0, the gauge indicates like 12 degrees flaps, not 10. Then when I select flaps 20 goes down from 10, the indicator goes to 30 degrees of flaps. Then when I retract them, they stop at totally different numbers. I'm completely lost. Shouldn't everybody's servo numbers be the same in the arduino sketch for the flap position indicator? Why does everyone have different numbers? Am I understanding the math correctly or is this not how servos work? (544-2400 microseconds = 180 degrees of travel). So if we take 2400 minus 544 = 1856 microseconds to travel 180 degrees. 1856 divided by 180 = 10.31 microseconds to travel 1 degree. So let's say the 0 degrees flap setting indication for my servo is 1300, then using the math I just used, the 30 degree flap setting (90 degrees of travel=927.9 microseconds) should be 2228. (1300 + 927.9).
×
×
  • Create New...