KosPilot

MP Black Screen Same issue, but only in MP. The screen goes black and I can hear the music in the background. Win7 x64, i7 3770K CPU and GTX690. No AMD in sight.

I have had this bug for a long time: Setup: 1. Multi (3) monitors with main display set to centre monitor (Centre monitor 30" landscape, side monitors 20.1" Portrait) 2. Graphics: GTX690, latest drivers Issue: The cockpit is displayed on all monitors as normal, but the clickable zones for dials and switches are shifted to the right. This means that if I use the mouse pointer to click on any switch/cockpit item, it will not be detected. Walk-around: If setting the left monitor as main display, the clickable zones and cockpit switches line up as normal. Switching between centre and left monitor as main display is causing severe problems depending what applications are active. Can this be fixed? Suggestions?

Email sent! I am obviously a bit slow on the trigger... Cheers ;D

LB, you guys are the best. Thank you!

F-4 Phantom. The F-4 and MiG-21 are iconic fighters of the Vietnam war. It would be nothing short of awesome to see these two fighters go toe to toe, and preferably with a map covering the correct part of the world.

-What he said!

MiG-21Bis is better known. Please gimme the MiG-21Bis...

I've been waiting for the MiG-21Bis for sooooooo long. Please finish that one first.

Agree! In addition to the client having the option to call for and await rescue I would also like to see the option in ME to place AI pilots on the map for CSAR purposes. The pilot model is already in DCS, and for AI - just re-skin a grunt and give him a M9. Everything is already set up in DCS for AI to "shoot flares" (signal flare on unit), "pop smoke" (smoke marker on unit) and transmit at any frequency. In the case of a downed client, the radio menu could be used to shoot flare, pop smoke or activate ELT (Emergency Locator Transmitter). This function would add significantly to DCS

Hi all, -need a bit of advise again. After release of the Huey module and the inclusion of new features in ME, I am updating one of my old maps to include Huey flights and using radio menu for manual mission selection. My maps are sometimes too ambitious in that I like to have a dynamic campaign feel to it, thus making a mess out of my triggers when updating a map. Attached is an example of two helos choosing over doing the same two missions via F10 in the radio menu. Once a mission is selected, it is locked to the pilot choosing it. (It may still need a bit of bulletproofing in MP, but in SP it's pretty good.) Because it took a fair amount of time coding it in ME; is there a method to copy it over to another map and save me the time of coding it again?! I know that using .lua scripts would more than likely solve my issue, but at the moment my .lua skills are way below par. Radio Menu Test.miz

I ran into a weird problem during ME map making. 1.2.4 11652 / 1.2.4 11855.154 At this specific map (attached) I used a Oliver Perry to ramp start a Huey. In the beginning it was working perfectly and I could rearm/refuel at the ship. Then, after a few saves, the ship stopped communicating with the Huey and rearm/refuel was not longer available. Selecting a weapon station using the [Alt-'] armament box displays an empty drop down menu. I have the same problem when starting with the Huey from FARP. When trying the same with a Ka-50, I get the armament drop down menu, but the ship do still not rearm and refuel the Ka-50. With the Ka-50 on a FARP everything works perfectly. Both Huey and Ka-50 get refuel/rearm at airports. Re-installation of DCSW and modules, and running the map in different DCS World versions does not fix the problem. I also deleted DCS under "Saved Games" just to be sure no bad config was carried over between installations. Still no joy. My conclusion (or theory) is that there must be a bad registry setting on my PC. The reason I believe that is 'cause DCS somehow knew some of my special settings after re-install even though I had deleted all traces of the previous installation. I have attached the miz. file so that you may see if you have the same problem. Please reply to this thread if you have any ideas. Mission#21.miz

I get a face-full of windscreen with my three monitors after 1.2.4 upgrade. View.lua was where I used to make my changes. Please, would some of you bright minds explain to me (or give an example) what values needs to be tweaked in SnapViewsDefault.lua for, let's say, setting min/max/default FOV for Ka-50.

Thank you, all I needed was already there... I just needed a... "corrector"... ;) Who came up with that word, is it in the orig flight manual?

Apologies! The problem is global with 1.2.4!! ED what have you done now...

Seriously, I'd like to assign the throttle to a controller axis. As there are sim-rigs out there with throttle twist grips, I am sure the hardcore simmer community would be grateful for that little addition :)

Hello there! AWESOME work with the HUEY! :) :) :) Please yell out if you have the same problems as what I have. First of all; I use three monitors in res 4960x1600, aspect ratio 3.1. Using default zoom means I get a facefull of windscreen (which makes stable flight and hover difficult, it's like holding a hover while looking through strong binoculars = not fun). For other DCS A/C, I always set zoom limits in View.lua, but this does not work for the Huey! Secondly; when assigning a controller axis to zoom, this axis will control the full allowable zoom range regardless of what limits are set up in View.lua (for AB212 ?) This is problematic for two reasons: 1. I like to use my right pedal toe-brake for zoom. Since the toe-brake is spring loaded I now get a ridiculous wide angle when not depressed. 2. If assigning zoom to a slider, the zoom will vibrate unless the slider is extremely precise (mine obviously isn't). This would not be a problem if a smaller zoom range could be set in View.lua It is GREAT to finally have a convensional heli in DCS. Thank you, thank you, THANK YOU!! :D

Only logging heli flight hours. I've tried the Su-25T in World and on occasion other fixed-wing but it just does not give me the same rewarding feeling of actual airmanship. So guess what; yes I am hanging out for that Huey... Bigtime.

If hit while down low and at IAS<120km/h I agree the priorities change a little :D

Prepare for the situation. 1. Learn how to fly and land safely without hydraulics / SAS (Personally I never use flight director and "AP channels", but that is a personal choice) 2. If the mission allows it, fill MAX 75% fuel (adjust with alt-' before leaving pad/parking area). The lesser weight of fuel will allow you to stay afloat with only one engine. 3. Practice reduced power takeoff and landing with one engine only, 75% fuel and clean stores. 4. Practice autorotations. When you are hit: 5. If you are high enough or have excess fwd speed; lower collective to maintain RRPM 6. Adjust fwd speed to ~140km/h 7. Jettison stores 8. Easy does it! For clearing hills, zig-zag up the slope at 140km/h. 8. At landing, maintain 140km/h for as long as possible. Stay above Effective Translational Lift, or ETL, min 40km/h until right before touching down. 9. If landing on an airfield or road, do a running landing. Tip: Do not shut down the damaged engine. Sometimes it may still provide a small amount of torque (I am fully aware that this is a questionable strategy if the engine is on fire...) Do not use emergency throttle unless you ARE going to crash if you don't use it. Emergency throttle may burn out your only good engine. If you are still going down, leave undercarriage up if landing with lateral speed on soft ground! One engine demo.trk

The torque gauge will indicate your rotor load. In a level balanced turn your bank angle is a direct indication of G.

Did not vote! I do not agree with the options. How about "Other" at least? 1st choice: Middle east map with Israel, Jordan, Lebanon, Syria, Cyprus including a snippet of Turkey, Iraq, Saudi Arabia and Egypt. 2nd choice: Indochina Peninsula - Vietnam, Thailand, Laos, Burma, including parts of China incl. Hainan 3rd choice: Afghanistan/Pakistan/India

My hardware code for activating BS2 1.2.2 is reported to be invalid without any changes to hardware. ED didn't mention that in their change log either! :mad: #^%@^%$@^&$ EDIT: I had the files downloaded from different accounts, that's why the hardware verification failed. All good now.

-And missiles does not do too well hitting branches and bouncing off tree-trunks anyways

Map option "Allies only" is reintroduced with DCS:W 1.2.2 :) Thank you, thank you, thank you!

Thank you for the feedback :thumbup: Request noted! I will add it to the brief. Maybe it is possible to have a individual msg pop up when peeps are spawning... I'll look into solutions :) EDIT: As Mega states below; I checked and found the following information for Nanchik: Active RWY, Departures; 06 Active RWY, Arrivals; 24 With the current performance of DCS ATC, I understand if people fall victim to runway accidents. I will however stick with that as I don't see that I have another choice...