Jump to content

Derbroomaster

Members
  • Posts

    122
  • Joined

  • Last visited

About Derbroomaster

  • Birthday October 31

Personal Information

  • Flight Simulators
    DCS, MSFS 2020
  • Location
    Ohio
  • Interests
    Flying, F1, NHL, Cincinnati Bengals, Columbus Blue Jackets

Recent Profile Visitors

1300 profile views
  1. You owe it to yourself to set yourself up to sit in the front seat. It is the single-most fun thing to do in DCS with a buddy. I have this and the Tomcat, and CP/G in the Apache is one of my favorite things to do.
  2. Yet we feel compelled to comment because the problem is not getting addressed.
  3. Precisely. And this is what the OP described pretty well, which is not a new problem, sadly.
  4. One workaround I use (which I shouldn't have to) is to either... a) Carry a mix of Kilos and Limas, putting George in SAL mode so that he constantly lases when given a target, which gives the range constantly, or... b) Don't WAS the Hellfires until you want George to look at a target, then WAS the Hellfires when you're getting ready to engage. This is a chronic problem that's been identified for well over a year and I've encountered escalating standards of evidence along the way, with no resolution in sight.
  5. lol wut
  6. Don't expect much help with this. George AI has been reported repeatedly as inconsistent, at best, multiple times. In any case, if you don't include a track file of what you're talking about happening and including the time mark when it happens (yes, really) you have zero chance of getting a useful response. This has been my experience, and there is still no resolution. At this time, if I feel like flying the Apache solo, I seriously have to weigh whether the inevitable frustration of George not working correctly is worth the effort.
  7. Thanks very much. I can provide a new file of whatever you need if required.
  8. Still happening after the latest patch. There are improvements, but this problem persists.
  9. OK, having read through this thread numerous times and attempting to mess with the .lua file, I'm no closer to solving my problem. I will restate it, since I don't think I adequately described this problem in the beginning. The MFD screens for the Pilot's position do not show in the MFD screens for the Pilot's position in the Helios screen (monitor 1). The Pilot MFD screens for the Pilot's position on the Helios screen are in fact the displays for the CPG. If I press a Pilot MFD button on the Helios screen, it corresponds to the correct Pilot MFD button. If/when I occupy the CPG seat, there is no problem. The screens are exported as expected. Can anyone tell me why this could be happening? Helios profile and monitor configuration .lua files uploaded. AH64 Final1.hpf Helios.lua
  10. Where is the file you're referencing here? And yes, the x value for resolution of the top screen should be 7680, as you mentioned.
  11. Screen 1 is the touchscreen. I believe my true problem is that the CP/G export is being seen in the Pilot seat. When I sit in the front the displays are fine.
  12. I will take a closer look at the Helios setup. I take care to apply Helios patches after every update and ensure each profile does not have identified issues. One thing to note is that the touchscreen (the fourth screen) is 1920 x 1080, while the other three are 2560 x 1440. The coordinates you call out in your screenshots: what numbers should those be as opposed to what are showing? Additionally, what is the .lua file these numbers came from and where is it located? Thanks for the information. I'll be doing my homework. I was away from the sim for a week learning a GA plane.
  13. This is the only Apache-related file in that path: DCS Apache.lua
  14. Where is this file normally located? I don't go under the hood often enough to remember.
×
×
  • Create New...