Jump to content

Newbie

Members
  • Posts

    8
  • Joined

  • Last visited

  1. Not sure if that's going to help but if you give me the file name, I'll tell you where it's in my Black Shark folder... If I were you, I'd uninstall/delete, restart the PC and try to install again (make sure no unnecessary programs are running during the process).
  2. It took me a while to figure out how to change both lua files to work with my dual monitor setup. Here's how I did it - hopefully it will help. My monitors - Primary, 1920 x 1080 - Secondary, 1680 x 1050 Screen resolution config in Windows Make sure they're aligned - primary at [0,0] and secondary at [0,height of primary]. If you put them side by side (my default is primary on the right and secondary on the left), then text commands during flight will overlap and you won't be able to read them :( options.lua - "multiMonitorSetup" - make sure you enter the setup name used in monitor setup file. In my case it's "my_setup2". - "aspect" is based on your primary monitor. - "width" is from your primary as well. - " height" is the total of primary plus secondary, so in my case: 1080+1050=2130. - "resolution" is from primary as well. My monitor setup file - "name" - make sure the name you use here is unique and used in options.lua file. In my case it's 'my_setup2'. - "height" is from your primary display. - "aspect" from primary as well (1920 / 1080 = 1.7777778 ). Shkval: - x = 0 - y = height of your primary display. - width = first I tried to enter half of the width of my secondary but it didn't work for some reason. So I started experimenting with values and finally discovered that - in my specific case - 840 is 50% of the width. No idea why but it works. ABRIS: - x = width of Shkval - y = height of your primary display. - width = should be the same as width of Shkval. This way they'll share the secondary display 50% each. Good luck!
  3. Hello, I'm new to DCS' simulators (spent 16 hours behind Black Shark's cockpit and approximately two behind A-10C's). Do you think you could take a look at the attached track and let me know what are some of the things I'm doing wrong? It's from "Deployment" campaign and the mission's name is "Escort" (it's the second one in the chain). The joystick I'm using is Microsoft Sidewinder Precision 2 (I know I should be using Thrustmaster but want to make sure I'm going to play these sims for a long time before my wife finds out that her wonderful husband needs a new "toy" :) ). Specific areas I have questions about are: 1. Trimming Trimming's purpose is to make the helicopter's cyclic keep its position without having the pilot apply any pressure afterward, correct? And apologies for poor phrasing - English is not my primary language and I have no piloting background. Shortly after taking off I: - allign towards the first waypoint, - reach desired speed and altitude, - release the joystick (if I keep applying pressure to the stick AND press [T] at the same time, the effect will be greatly amplified, which is not something I think I want), - press and hold [T], - push the stick back to regain heading & speed - release [T] Am I doing it right? 2. Stopping that damn thing and hovering without ANY movement This is a constant battle for me. I reach waypoint 2 and (cheating) want to take a position opposite the village. When the ambush takes place, my nose will already be pointed towards the enemy and all I'll have to do is fire away. This flythrough was actually pretty good - I was only moving at 10-ish KMH in autohover but in previous ones my helicopter kept "strafing" at 30-50 KMH despite my attempts to stop it. What am I doing wrong? I tried to trim a few times but don't think it worked as I would've wanted. 3. Rockets I think I fired too many from too far away. And I definitely need to practice aiming - I know :( 4. Autopilot altitude hold Just to make sure, the correct way to use it is to: - Reach the desired altitude. - Engage "hold altitude' mode ([LShift + A] in my case) - Engage collective break [F] I noticed the the helicopter will make attempts to return to set altitude in case the terrain changes (flying over a mountain, valley, etc.) but only by a few degrees, so if the difference is significant (e.g. I wanted to fly at 30 meters but suddenly I'm at 500), I'm better off disengaging the altitude autopilot, reaching 30 myself (quicker) and engaging it again once there. Would you agree? Thank you for your time! Campaign Deployment - Escort mission.trk
  4. Awesome. Worked like a charm. Thanks!
  5. Hi, I've just purchased A-10C and can't get my two monitors to work... Things work fine in Black Shark but in Warhog - no luck... I have 1920x1080 as my main display on the right and 1680x1050 as secondary on the left. Here's what I do in Black Shark: In Black Shark, I drag the window from the main, right monitor to the left and start the mission. I can't replicate it in A-10C, because the window cannot be moved at all... Advice would be greatly appreciated. Thank you!
×
×
  • Create New...