unknown

Hi, i'm new to VR but i noticed in my first flight with the A8 that the sight is behaving weird. Attached are two pictures, i'm not an artist so forgive the simplicity. If i move my head left right or right left i would expect the gun sight to behave like in the first picture but it's like in the second. The reticle moves and then jumps like if it's changing from left to right eye and at some point it's merging.

Just finished my first quick flight and i can confirm the things marked bold in the quote, didn't try the other things yet.

I have accomplished my first flight too. What a lovely lttle bird, thank you very much for this ED! :thumbup: PS: Recently got into VR, am i the only one who thinks the WW2 birds are way easier to fly in VR?

Yes, i know that. What he ^^ said :D We can't change it, so what...have some fun. :beer:

Could be, but i don't think so. Wags said they will release this patch this time if the 3r party module is working or not. But heh, maybe the latest fix for that module screwed everything up....:music_whistling: Who knows, who cares....

But the last two delays was because of a 3rd party module not being ready/working for/with version 2.5.5. So technically this is a new reason for the delay.

Works for me, i'm running the OB.

Yes, i did that. I did this again and touched my desk to be the "ground", looks good now. Sorry for spamming such stupid questions here. :beer: And by the way, now that it works it's a blast! :joystick::thumbup:

I tried to connect the Rift S at the same Ports like yesterday and i had the same problems. Long story short, i reinstalled Win 10 and now everything works perfectly fine. It seems i screwed something up back in my first Win 10 days with the Win 10 privacy programm. But know i have a "little" problem, i have to stand now to have my virtual head aligned with my RL head. If i sit down in my chair to have access to my HOTAS and pedals i'm looking directly at the stick in game :D Anyone has a quick solution for me? Something like a button click to center the camera like with TrackIR?

I found my problem, the camera was enabled in my win 10 settings but i remembered after first installing win 10 and all the "calling home debate" that i played with a little program called win 10 privacy. In this programm i disabled the camera(never used one myself), undid this and now everything workes fine. :thumbup: :beer: Except the hand controllers, in the oculus "home/menu" (don't know how to call it) they are sticking to my face and i can't use them there(connected in the software), but that i will figure out later at the weekend. Thank you!

Hi everyone, i'm totally new to VR and just got my Rift S today. I installed the software, it was updating the FW of the Rift S and after that i tried to run the setup to configure the Rift S and there i run out of luck. I connect the USB cable, wait until the LED in the rift turns from orange to white, plug in the DP cable, both show as connected/green in the software but the next step fails. I tried every USB port on my PC including one on my powered USB HUB but i always get an error telling me "...Sensors can not detect headset..." something like that(i'm running the software with german language settings). If i skip the setup and look into my the oculus software/device i can see the Rift S as active with a geen check but all i see in the Rift S is a rectangle with 3 white flashing dots. A quick google search didn't show me the fix for my problem, so i'm asking you guys. Anybody out there who can help me get this thing running?

Like said by my two previous speakers, ED and Belsimtek merged, there is no seperate Belsimtek anymore. They did atleast the PFM for the FC F-15C and they worked on parts of the F-18 if i remember correct

Yes that is what i quoted.... But thats the same as if i would say the "Leopard1/2 tank was using a 105mm and 120mm gun", it's not clear which version used what weapon, thats what iwanted to say.

Do you have a direct link? Because the only thing i can find in your quoted link is the F-16 C/D Block 50/52 article which states:"...The Block 50/52 is capable of carrying the new JDAM munition, the AGM-154A/B JSOW and is the first F-16 version to integrate the AGM-84 Harpoon antishipping missile....." So no clear statement which one could carry it. I would love to see it on the F-16 but i doubt our version can do it.

+1

That's why they test/bugfix this patch since last week.

You could put your point of view in your signature instead of quoting everybody who is happy with purchasing an EA product on the forums. This would save you alot of time and us reading the same statement for the hundredth time(at least felt). No hard feelings against you :beer:

:lol: I don't think there is a manual at this point! :lol: So i don't get how you can be mad about this, especially if you "...those who not only pre-order but who have been with DCS from the get-go!" you should know how this works. ;)

I don't know/care about the Harrier but the Mirage is a full released(NOT EA/Beta...) module for quite some time now... :music_whistling:

BUMP I just discovered this too. I took the FW-190D9 for a ride and tried to do some AG stuff and noticed that the WW2 asset pack units disapeared(not tanks?) very quickly while normal DCS ground units are visible from far away compared to the asset pack units. pic 1 - ww2 units visible pic 2 - now they are gone pic 3 - ordinary Kamaz trucks EDIT: ED could you please fix this? :beer: This is a realy game stopper for me as most of the time i do AG stuff and was hoping to do some of this in the upcoming FW-190A8. It's a long time ago i flew ww2 planes, helicopter and jets are my most used modules in DCS.

And to be even more fair, zeus stated "...months, not years." So technically everything within 24 months between that statement and the release would be true, only months and not years, clever statement. :thumbup:

No, that's in the "Phase 2 Product Sustainment" https://forums.eagle.ru/showthread.php?t=241132

To be fair it's only been 10 months ago not a whole year, so they have a few months left to stay inside their "...just a few months..." statement. :lol: ;) :music_whistling:

The key thing here is, without a second party telling your aircraft via datalink "hey this thing is hostile" your IFF is telling you "i don't get a friendly response" -> square/yellow/unknown contact. For your aircraft alone you need to be infront or in the back of the plane so NCTR(not IFF) can identify the plane type (Mig/Su/F.../ i think Wags stated somewhere within 20° 12/6 o'clock position). To do so your Radar needs a good look at the engine fan blades, if you look at him at his 3 o'clock your Radar can't see the fan blades -> no identification.

I can't confirm this, my ED account and PayPal is showing me i paid 64,99USD. But i also have 84USD as Bonus points and don't know where to spend them, so....ED you can have my extra Dollar for the F16. ;) Maybe it helps developing the MI-24 :music_whistling: