Jump to content

FlyLikeKilroy

Members
  • Posts

    7
  • Joined

  • Last visited

Personal Information

  • Flight Simulators
    DCS World 2.x, X-Plane 11
  • Location
    Oregon, USA
  • Interests
    Flight simulation, breathing
  • Occupation
    IT
  1. A quick update. The latest version of Parallels Desktop (Mac host) supports Direct X for Windows 10, allowing DCS World 2.5.x to run succesfully. It's slow, but it runs.
  2. Apparently DCS World 2.x requires DirectX 11, which Parallels Desktop for Mac does not currently support (Win 10 client/Mac host). So, as far as I can tell, it's not possible to do this as a virtual machine.
  3. I'm familiar with Boot Camp but that won't work for me. I need to be able to switch between DCS mission editing and real work in my native Mac apps. You know, 'multitasking' ;-)
  4. I am running Windows 10 in a virtual environment (Parallels Desktop) on my Mac, with 8 GB of RAM. I've installed DCS World in that virtual Win 10 instance but it won't run -- it displays the initial DCS World logo screen, and then dies without error. I'm not wanting to fly in my virtual Win 10 instance, just use it as a place to create and edit missions during breaks at work. I would then fly those missions on my main dedicated Windows 10 machine at home (which runs DCS just fine). Is there a way to only edit missions and not have all the rest of DCS World attached? I've assumed that my virtual Win 10 instance isn't beefy enough (it's running with 8 GB of RAM but I'm not sure the rest of it meets the minimum specs required by DCS World).
  5. Thanks, hansangb. That walk-through you linked to was helpful and enabled me to get my left and right MCFD's exported to my touch screen, with Ikarus running on top. It took a fair bit of trial-and-error to get them positioned and sized correctly, but that's just tedious effort, nothing complicated. I tried getting RWR and other gauges exported but it actually crashed DCS when attempting it using the same methods. I'll experiment with those this weekend. Thanks!
  6. I'll check it out, hansangb. Thanks!
  7. Opy, your setup is basically the exact same thing I'm trying to get working. Can you do us all a solid and be more specific about how? Goal: Get my DCS World 2.5.x working with three identical screens plus a touch screen (with Ikarus preferably, or HELIOS second choice) with interactive gauges and switches in a T-configuration. I intend to fly the A-10C 80% of the time and the FC3 F-15C 20% of the time. All running stand-alone installation of DCS in Windows 10. Detail: I have three identical 32" flat panel displays at 2560x1440 resolution in a three-panel side-by-side array. We'll call them 3-1-2 (those are the monitor IDs as reported by Windows 10). I have a fourth monitor that is a 1920x1080 touch screen in the bottom center position, directly below monitor #1. We'll call this one #4, as reported by Windows 10. This forms a T-configuration, with a 7680x1440 resolution viewport across the top three. I have followed directions provided in many of the other threads on this forum and that advice has gotten me this far, but I still have a little more to go. Status: I have successfully got the three main monitors working with a customized 3screens.lua file, and I have been able to get Ikarus to export 90% of the A-10C's cockpit gauges to #4 (they work and interact to my touches). However, the MFCDs and RWR (and maybe some other displays and gauges I'm unaware of) don't display on #4. The OBS buttons around the MFCDs on #4 work; I can press them and their results affect the main screen cockpit. Frustration: I have been able to get the left and right MFCD and RWR to show up on the three main monitors (3, 1 or 2), using X/Y coordinates to place them where I want. These floating displays 'work' in the sense that they show what's going on in the main cockpit. However, I can't get them to show up on the touch screen monitor #4 itself. I've tried referencing Y values greater than 1440, etc. I've tried including #4 in the total resolution in 3screens.lua (7680x2520) but that doesn't work, either; it screws up the main displays and still doesn't display the MFCDs and RWR on #4. Bottom line: How do I get the MFCD displays to show up on my touch screen #4 monitor?
×
×
  • Create New...