Leaderboard
Popular Content
Showing content with the highest reputation on 09/22/11 in Posts
-
And the Next DCS Aircraft is.. Dear Mr. Wags, As you surely already know, the whole world of Sims awaits anxiously the announcement of your next plane. Do not think that it is time to reveal what it is less than that plane? Sincerely, Denis Palermo :thumbup:2 points
-
Wanted to share this with all of you because I see often people asking how to use the zoom in a easier/effective way .... so: Zoom-In/Zoom-Out on PAC1 to make your life easier ! (first posted here: http://forums.eagle.ru/showthread.php?p=1293475#post1293475) Why don't use a macro for zoom-in/zoom-out instead of a slider ...and also automate the zoom in some kind of way? Following is just a example - you can use it on a toggle-switch/button or bands -It don't has to be a Press/Release command. This is what I did on my TM-Cougar using Foxy: (read further if you have a Saitek-Controller ) BTN TG1 /P KD(p) <KD(KP*) DLY(800) KU(KP*)> /R KU(p) <KD(KP/) DLY(800) KU(KP/)>Explanation what this macro does: KU = Key up KD = Key down DLY(800) = Delay-:hold the state that is posted before this "DLY" command for 800 millisecond (0.8sec) before execute the next state - as long the initial button is pressed (KP/) - (KP*) = corresponding key-press on the num-pad : "*" and "/" - this is zoom-in and zoom-out in DCS A-10c <> = what's between this brackets will be executed even if the button is released before the delay is timed out. KU(p)-KD(p) = Key up "p" -Key down "p" : this initiate and releases the PAC1 state in DCS A-10c I have this on the first stage of my trigger and it zooms in for 0.8sec and also enters the PAC-1 state. When I release the trigger it releases the PAC-1 and zooms out for 0.8sec . (Similar like gunsight in IL2) This is very helpful while aiming at the target. -and after I have fired the guns/rockets I will get back to my default zoom without having to fiddle around with a over-sensitive slider/rotary. And I also use this to get a better look to the Mav/TGP image of the MFCDs when lookong into the cockpit and use it when I'm in the need of binoculars. And you can also use a Toggle modifier (/T) instead the press/release (/P,/R). But having it on the first stage trigger feels most natural to me. How to do this on a Saitek Controller: I made a video that explains my macro in the SST and shows how it reacts in DCS-A10c if set to the stage1 trigger: Sorry for the German layout - but if you a smart-guy you will have no problems to follow the steps. (I programmed it on a Saítek-Throttle-Quadrant - so I have no profile for a X52 to share.) And you can also put it on a rotary or slider using bands. Or use it as a Toggle event. If you have a TM-Warthog and adapt this for yourself and have also the time : Please post how to do the same on TM-warthog with a small explanation ! EDIT: Made autohotkey-script that works with every joystick. Download autohotkey and use this script- Binos-pess and hold.AHK: And this is the variant to toggle zoom in/out with one key-press - Toggle Zoom.AHK Don't forget to edit it to your Button ID you want to use for "Binos" >>> 4Joy17:: ; This is my Bino toggle Jostick button = Jostick ID #4 Button 17 -change this to your new "Bino" button. ; Use joystick test from autohotkey help to locate your button Download these AHK scripts If you found this useful you may want to check also this: How to unchain the rudder from trim in DCS-BlackShark How To: Remove centre detend from Saitek Pro Flight Rudder Paddles corrupt calibration? crazy joystick response? Use this tools Fix it: Drag/Drop and Click-able Radio Communication menu Tweaked Cockpit view for DCS A-10C Zoom in-out AHK script.zip1 point
-
Status update: Currently we're adding the terrain elevation lines. After that we'll add objects like antennas or lighthouses and all the other stuff that is relevant for the pilot due to their elevation above the ground or their useability as visual navigation reference objects. After that the charts will be given to our squadron members for internal testing. After fixing everything that might appear, they'll be ready to go.1 point
-
will do mate if i new how i would give you a rep but i dont know how haha found it lol there ya go mate a big +1 from me mate1 point
-
1 point
-
Christian, sorry my German is not very good, so I can't help in your native language. Can you ask a friend who can write clearer English to post the question, as your English doesn't make your request clear. (I'm gonna google that into German and it may come out wrong but here goes) Christian, sorry mein Deutsch ist nicht sehr gut, so kann ich nicht in Ihrer Muttersprache helfen. Können Sie bitten einen Freund, schreiben klarer Englisch können, um nach der Frage, wie Sie Ihr Englisch nicht Ihre Anfrage klar. (If that is offensive at all, blame google)1 point
-
You need to make an adjustment to your grid setting. If you start on an airfield to the east of the coast your default grid is most likely going to be 38T. If JTAC gives you coordinates in the 37T grid and you don't change your grid setting, you're going to make a waypoint thats hundreds of miles away from your actual target. I can't give you the most techincal explaination but essentially the UTM system divides the globe up into a grid and unfortunately for us, the region thats modeled is divided between 37T and 38T. There are a bunch of threads on this specific topic, just search around. The easiest thing to remember is if JTAC gives you coordinates that start with A-G your grid should be 37T. If they're H-Z it should be 38T.1 point
-
You can use Alt+C to toggle between mouselook (move mouse to look around) and mouse-as-cursor for clicking on things. I don't think you can bind the right mouse button, since you need that to interact with some of the controls (and some of the knobs need mouse wheel up/down).1 point
-
Not only wags but also many people on this forum have known it yet. The reason they are not willing to tell you is they want you to be more anxious:D1 point
-
1 point
-
1 point
-
1 point
-
I don't know the exact refreshrate of my monitor (to the digit behind the point) but i know if Windows detects it, it show a refreshrate of 59Hz with the option to set it to 60Hz. So i recon my monitors refreshrate is somewhere in between (but that's a rough guess until i find it's thru refreshrate somewhere). Either way, it doesn't matter if i select either 59 or 60Hz, the results are the same for both settings. Anyway, just a thought... they have been releasing videodrivers for what, 20 years now, should a decent videodriver knows his way around this trap by now? Here are bit of my findings regarding Eagle Dynamic sims: Explenation: Smooth for me is when there is a "very" fluid motion and there are no regular hickups or constant stutter, whatever there cause is. An "occational stutter" due to loading data can occur. But if these occur on a regular bases, i don't call it smooth anymore... Lock On: - VSync ON through D3DOverrider + FULL SCREEN = smooth, no tearing Lock On FC2: - VSync OFF + WINDOW MODE (but at full screen res): Smooth, no tearing: FPS don't go higher then monitors refreshrate = 60 - VSync OFF + FULL SCREEN: Smooth, but quite some tearing - VSync ON (nVidia 275.33 driver) + FULL SCREEN: smooth but quite some tearing and VSync does work (unlike in Black Shark, see below)!!! - VSync ON through D3DOverrider + FULL SCREEN: Not smooth, some minor stutter, no tearing DCS: Black Shark: - VSync OFF + WINDOWS MODE (but at full screen resolution): Smooth , no tearing - VSync OFF + FULL SCREEN: Smooth, but quite some tearing - VSync ON (nVidia 275.33 driver) + FULL SCREEN: smooth but quite some tearing and VSync does not work, FPS 50% higher then refreshrate!!! - VSync ON through D3DOverrider (VSync works now!!!) + FULL SCREEN: Not smooth, some minor stutter, no tearing DCS: A-10C: - VSync ON through DCS:A-10C settings (nVidia is set to application controlled) + FULL SCREEN: smooth, no tearing. - VSync ON + WINDOWS MODE (nVidia is set to application controlled): smooth, no tearing - VSync OFF + WINDOWS MODE (at full screen res): Not smooth, constant stutter, tearing, FPS goes higher then MAX FPS set in graphics.cfg file!!! - VSync ON through D3DOverider FULL SCREEN OR WINDOWS MODE: VSync does not work!!! Not smooth, constant stutter, tearing, FPS goes higher then MAX FPS set in graphics.cfg file! !!! D3DOverrider doesn't work with 64-bit applications !!! A big problem occurs in both nVidia Settings and in D3DOverrider because they see LockOn as a seperate game, LockOn FC2 and Black Shark as one single game (both simulator.exe) in D3DOverrider, Black Shark and A-10C as one single game (DCS: Black Shark) in nVidia settings. This gives throuble if for both sims, the settings needed to get a smooth fluid motion are contradictory. Therefore i use either a setting through nVidia, D3DOverrider or ingame (A-10C) to make a good setup.1 point
-
1 point
-
1 point
-
Друзья, может я уже и не в тему...но готов что-нибудь для вас озвучить. Имею целый пакет профессиональных програм для звукозаписи. И просто есть желание поучавствовать. Буду рад помочь.1 point
-
To the developers of this campaign, I don't know it this is appropriate to say but I have enjoyed this so far, thanks for a great job.1 point
-
Why not just adjust the gain level directly using Notepad++? Look for; C:\DCS A-10C\Sounds\sdef\Aircrafts\Engines\EngineTF34GE100InR.sdef and C:\DCS A-10C\Sounds\sdef\Aircrafts\Engines\EngineTF34GE100InL.sdef Example below; wave = "Effects/Aircrafts/Engines/EngineTF34GE100InR" outer_radius = 1000 position = {-7.5, 0.0, 0.5} gain = 0.25 (default is 1.0) I like 0.25 Don't forget to back up your files.1 point
-
Recently Browsing 0 members
- No registered users viewing this page.