npole

I big player is gonna launch a hand tracking device... so I would hold my breath for some weeks...

One thing.. the screen resolution is ignored when running in VR mode right? Because i normally run in 1600p with the monitor...

Hi everyone, I own a 980Ti Hybrid (OC'ed) and a 6core 4.3Ghz... To get rid of the jitters, I have to set everything on OFF (textures.. etc.), is it normal or I'm doing something wrong? I have set the VSYNC already off.

Both the tech are here already (almost)... we will have some hand gesture and recognizing device "soon", from a big hardware player (it will be shown at the next E3), making the virtual cockpit clickable, much more easier. You can also have an hybrid tech (similar to the augmented reality, or the inverse of it): the VIVE has a webcam in front of it, it can be used to project the reality in the VR environment. The possibility are endless...

Any news about the dedicated server? I read about it in a previous newsletter that was being worked on... what's the state currently? We will have a proper dedicated server in the upcoming months ?

...any good server with 120C disabled? It's like playing the noob mode now, you see only "killed by 120C" on every single server out there! :D

Without discussing the fact that TWS is bugged atm so you're forced to go STT... eve if it's 15nm+ .. is there any explanation about it? I mean the specs says that if the target is further than 15 miles you can't STT it ... or it's just speculation? I'm trying to determine if it's a bug .. or if it's expected but not documented.

The distance can vary.. sometime it's 30nm .. some other times it's 20nm .. other times even less. A jammer will let you TWS but not STT? Same, for the distance: is there a distance where you can only soft lock but not hard lock? Knowing the limitations and the possible cause would help a lot...

Internal build.. he also already said that we won't have any change for the Mirage today (Friday DCS update), we must wait the next Friday (June 3rd).

In a bunch of occasions I cannot STT my targets... then after repeated tries, it finally locks it. I want to know what could be the cause of this behavior so I can understand how to counter act it. What happens is: I have a contact on the radar (I'm in HFR), I soft lock it (PID).. then if I try to hard lock it, it gets unlocked (it's like the lock button acts as a toggle), no other targets will be locked; I have to repeat the above steps several times, until it finally switches from PID to PIC (instead of unlocking the target...). Is this expected? And what could be the reason?

That's only about the radar scan frequency: as I said I already have it mapped. If you look at the bug, when you exit the CAC Mode (close combat mode), the radar will return to ENT... I was looking for a way to have it automatically (notice the word "automatically") switch to HFR Mode back (the default mode) without force me to press an additional key. CAC/DEFAULT mode is a command (on the 2000C it's on joystick)... ...while HFR/ENT/INT is another command (left panel)...

I didn't found a way to switch back to HFR Mode automatically when exiting the CAC Mode. I mapped the key as well, but pressing that button every time (additionally to the Normal Mode button) is annoying.

Okie tnx.. I had to save the modified ones or I would have done the modifcation again and it would have been a pain. I wanted the original just to check if I missed anything. Solved anyway.

Hi everyone, is there a way to bind a direct panel command to two different device ids? In example, this is the original line: {down = 3506, up = 3506, cockpit_device_id = 11, value_down = 1, value_up = 0, name = _('Command'), category = _('Sensors')}, The above will assign the values 1 and 0 to the same switch on the same panel. Is there a way to do the same but on different panels? In example something like this: {down = 3506, up = 3002, cockpit_device_id_down = 11, cockpit_device_id_up = 10, value_down = 1, value_up = 1, name = _('Command'), category = _('Sensors')}, ...any work around?

Does anyone has the most recent default lua's for the keyboard and the joystick to attach to a posy here (or to upload somewhere)? Or.. if there's a way to revert the file to the original state. Thanks.

When exiting from CAC Mode (Close Combat Radar Mode), the PRF (Radar Scan Frequency) switches to ENT (Interleaved), despite the switch on the panel remain on the HFR selection. Right clicking on the switch (it won't change its position) will reactivate the HFR mode. This is a big issue since apparently you cannot map this function to KEY/BUTTON, so you have constantly to move the view on the panel to reactivate the HFR mode, or your target lock won't PIC/STT (Single Target Mode) anymore. *this last part is not true anymore since you can bind the key now - the bug still.

I confirm there a bug with "Special Modes Deselect" function (default key "D"), when you switch to close combat back to normal mode, the VTB shows "ENT", even if you have HBR selected.. unless this is the normal behavior for some reason.

I hope that's not the case.. I mean the system knows already about the target soft locked, there's no reason to move the cursor again above it, also it's not easy to manage with the TDC when you're basically already in combat... I will test later today, but looking at this video, the lock switches to PIC while the cursor is elsewhere, I'm not sure if the switching happened automatically or if the guy pressed the lock button again @ 0:35: EDIT: oh!.. and he was in "ENT" as well.. now I'm even more confused.. lol. But maybe that video isn't true anymore since it come from last year.

Ok now I understood, thank you. It was the ENT mode that was confusing me: even if the switch (left of pilot) is in HFR mode, when I press the button to return to "Return to normal Scan mode", the VTB shows ENT instead. I don't know if that a normal behavior... probably I misinterpreted the command "Return to normal Scan mode" ... i believed it was used to exit the CAC mode (close combat mode), but apparently it's not.

Thank you. Can you actually switch from PID to PIC by locking again the target within the circle in the HUD? So without using the TDC in the radar? I watched it on a tutorial.. unless I misunderstood it. So that was my mistake, I were pressing the LOCK button again once ready to fire, believing that I was switching to single target mode... while in fact I remained in PID mode. That was about the 530... but what about the 550 at 18:00? Shouldn't it have hit the target even if I was in PID mode .. since it's IR? EDIT: about the PID to PIC.. maybe I figured it, I don't have to pay attention to anything, I can just push the lock button again when I'm ready and if there's a target in PID mode it will switch to PIC.. correct?

I know I'm doing MANY things wrong.. but I struggle to figure what I am doing with this missiles.. I'm unable to hit anything. In this video I'm noob-testing the aircraft.. so please ignore all the crap i do in the whole video... but let's concentrate on two shoots, why those missiles goes for their own route? 23:20 .. it's a 530, did it missed because the bandit was too near and going straight to me? 18:00 how did it missed? A Magic at 4.5 miles with a solid target... (it goes straight past the target).. [ame] [/ame] I know i'm doing something horrendously wrong... so please help. :D

Where you can check the purchase date to see if you're eligible to receive this map for free? The shop history doesn't go that far (it stops at 2013). Is there a place where you can add your key to check the first activation date? EDIT: nevermind, I found it on my profile: Bind date: 07-08-2011 ..so I was late. :)

Doh!

I mean this: http://forums.eagle.ru/showpost.php?p=2425663&postcount=5 ..it's 30 minutes past the 18:00 UTC but noting has happened?

Everyone else is moving toward DX12 .. and we still have to migrate to DX11? I don't want to be the one who moans about it.. but DX12 is a major improvement (much much more than the DX9 > DX11) in terms of performance. DCS2 isn't out yet.... why isn't going to be full DX12 compliant? It won't make sense to release something "new", with an already expiring tech.