Jump to content

janpitor

Members
  • Posts

    25
  • Joined

  • Last visited

  1. F-14 remote display Good evening guys. I have this information about a display I need to read from F-14B and use dcs bios and Arduino to display it on a 7 segment. My question is, what would be the code to read the value and convert this to string variable in arduino? (I can later convert that to integer, I know how to do that) It is not in DCS bios. Thanks PLT_UHF_REMOTE_DISP - PILOT UHF ARC-159 Radio Remote , UHF 1 , exported as string
  2. My only problem is, there is no working profile for F-14 for Helios for now, so I guess I would have to start from scratch EDIT: I've found a thread where cpt zeen is working on one, so this will be solved shortly. Thanks
  3. Thanks, screen capture will probably not help, because it would not really be a duplicate of any part of the first screen. I guess my options are to wait for ikarus/helios to create profile, create it by my own, or do it via separate viewports, which may be more FPS hungry.
  4. Hi gents. Is there a way to viewport not exact instruments, but to create a viewport in a way, for example to take a view from point 0.5 meters below normal head position in direction forward, 30 degrees wide and send that to second monitor? What I want to achieve is to have a big portion of the dashboard on the second monitor without trying to compile it from separate instruments. It would be whole instruments of F-14 without the side switch consoles. If it is possible, what would be the FPS impact on really marginal system (compared to helios/ikarus, which are not yet compatible with F-14, and the method of viewporting all the instruments)? Thanks i7 2.8GHz, 8GB ram, GTX1050Ti, all in a gaming laptop, The screens would be 2x FullHD, one of them through USB
  5. I just started the BFM campaign and have one question. What should be the setting of master arm so that the pod will record a kill? Safe, camera only, or do we fire live ammunition? Thank you
  6. Thanks for the info :) It makes sense
  7. Is there a reason why it is released only in open beta and the other early access modules are released in stable? Or will it be released in stable after some initial period?
  8. Guys is this released also on the release verison or only on beta? I dont have anything yet. Thanks Never mind, I see on the website I need the beta. I guess I will wait till the final release
  9. Gentlemen, just for clarification, I do not know about US, but in Europe QFE is very rarely used (maybe some local aeroclub flying). Normally QNH is set on the ground up to transition altitude. So OP's question is valid
  10. L-39 is our primary trainer, it is a great addition to dcs
  11. If you can get a second hand G-940, go for it. It is much better than any saitek, somewhere between saiteks and warthog, but has pedals, FFB and a lot of buttons and hats. It is a shame logitech is not producing them anymore
  12. I would recommend the A-10C. It has very good RWR and very good targeting pod. This combination allows for high survivability even for novice pilot. Also, mud moving is far less demanding on situational awareness than BVR. As soon as you manage to use HOTAS effectively, you will be able to fight without learning the complexity of aircraft systems. All this will come later.
  13. Well, that is strange. However, I do not own the A, I only comment based on C model. Just curious, what is the actual stall speed if you try it?
  14. Hi, I think the normal climb speed is around 180 in A-10, so you can climb faster with lower airspeed. 270 is more for level flight
×
×
  • Create New...