verana_ss

hmmm.. 15 plus years of simming and finally my dream come true. Theres a beautiful 3rd party software for FC3 created by Yoda but now the functionality become official. Congrats to DL lovers, welcome advanced warfare.

nvm...

As far as I can tell, radar now works pretty well however when slaving radar with JHMCS, does the circle indicator suppose to go outside radar gimbal limit? And i know i know its not appropriate to ask here but I would like to see some love in AG functionality.. marking or displaying designated point.. :)

Commenting out the UIview or something like that in monitor lua do trigger this bug

It does indeed fix the weapon selection but ground shadow will be bugged with the settings.

would love to see Slave function working as it'd make life much easier

^this!:thumbup:

Definitely, Link16.

^ this. reflector tint do indeed get exaggerated by some camera sensor even when it can be barely recognized by human eye.

I still recommend having triple monitor as DCS supports dedicated FOV for "each monitor", which I call "true multi monitor support" This having "dedicated FOV for each monitor" is rather important as with conventional setup, wider FOV makes warp effect that ruins your experience(side edge of monitor is rendered stretched out).

You guys noticed GAU8's rounds blast sound added? The sound is actually not coming from the blast itself but still I understand what dev is trying to achieve. My hats off to the sound dev who made it. I like it... A LOT!

I would like to change the default FOV at least.. not being able to readout HUD is the biggest and the only drawback issue Im having with DK2, flying A-10C. Also, I'm not sure if it's just me but I feel the size ratio between real world vs virtual world in DCS is like 1:8.5, so I want to make the v.world a little bit bigger. Sad but true that Res of the CV1 is likely to be 1440p which I doubt is enough for HUD readout.:(

If only zoom was functional in the rift mode..! :)

Ive got DK2 today and tested it a bit. Wags's review covered pretty much all the important points. I had to turn off the legacy support in Oculus utiility and Exit the Oculus Utility itself in addition to Cowboy's advise to make it work on the current version of DCS btw. This is already mentioned by Wags but the feeling of landing is indeed completely different. You get the additional "cue" from the 3D or (almost) 1:1 size of the world which you wont get with the traditional normal size of display(24inch-42inch). It is actually easier to land the thing(both chopper and fast plane) Also, another thing I have noticed and thought is interesting is that when you concentrate on the HUD, your eye focus switches to infinite mode which is another thing you wont experience with the traditional monitor although Im not sure this is also true in reality. The only thing DK2 is still not for practical use in flightsimming is resolution IMO. I really hope CV1 gets to the level where we can readout the numbers in HUD easily.

DK2 support Sweet!

both have pros and cons imo. Interesting experience I had with Oculus + Chopper demo was that with VR, you hardly gonna try a silly maneuver with it. I dont know if it's because things are drawn with almost 1:1 with 3D, you somewhat feel "it will trigger catastrophic outcome if I exceed this" feeling as you do in reality.(like when you drive a car) Also when you land the chopper, your handling on the stick and throttle become very deliberate even though its FM is gamey as there is actually no choice other than doing that.(you feel VERY uncomfortable with rough landing) I think these feelings you can experience are VR exclusive.

Email sent

I still don't understand why people try to talk about missile with its KD ratio when the number seems to be heavily affected by target's action. Meanwhile, I support the opinion that AIM-120 performance itself is way undermodeled (WIP) not because "I think so" but the various comments made by the people who works closely to the A/A military operation.(IIRC, SFAL)

This is big news for the Rift users.

is this right? fucntion letspackthedynadd() dynadd codes end local lets-respawn-planes mist.scheduleFunction(letspackthedynadd, {}, timer.GetTimer() + 300)I could be totally wrong but wouldn't this take reservation of the next respawn when the original group lands or gets destroyed..? My explanation was poor that might fail to make myself understood, this is the video of outcome of the additional code that I posted to achieve following objective 1- 24/7 CAP over at AO, cloned group succeed to CAP role when original leaves the area. <-- main purpose of this additional code 2- Respawn CAP group when it gets wiped out for whatever reason <-- Already achieved by Baron's code 3- Easy to alter, add and maintainance flights in mission editor <-- Already achieved by Baron's code

I dont know if decades old plane without constant upgade would do much under modern EW.

Actually the panel I was referring to was the one below throttle. You can clearly see "JTIDS" text in there. Not to mention the F-15E stick that seemed to be delivered to 15C with JITDS implementation, judging from the document I posted.

Hi, St3v3f Thank you for your advice. Do you mean I should pack all the dynadd code into switch condition section using mist.scheduleFunction? I'll try that way thanks again! :)

here you go Kuky's mod http://forums.eagle.ru/showthread.php?t=71639 lightningstrike's mod http://forum.lockon.ru/showthread.php?p=1764456

beautiful