TheBamse

Oh right! I always think that it is the Scorpion that is monocle and JHCMS has its image projected for both eyes ... for some unknown reason. My b!

Just like when using screens with track-ir. The symbology will be centered pretty much no matter how you turn your head. To counter the question, why would it be different in VR? :)

I think I was a bit nitpicky. I just got home and got some quiet-time to actually sit down and compare more closely. Comparing you first seconds in the clarity video when you engage the after burner to what I see ... it's pretty much the same to what I see. Bottom rows of DDI push-buttons at the bottom and just above the bottom of the apex in the canopy frame (or whatever it's called, sry). My clarity isn't there yet but I haven't spent a single second going through my bitrates and stuff (and that I'm using QuickSync instead of NVENC ... but that's potato/potaato ;D) TL;DR: I'm all good. Thanks again! ;)

Hi Jabbers! Awesome videos, thank you for making them! Just a quick Q; while following the guide in "All things VR" I do get a much higher resolution and everything and things looks quite a lot better quality-wise watching my downscaled 1080p output recording (with canvas being set to 2160p). The main issue, if it even can be called an issue, is that the aspect ratio still gets a bit, well ... not to my liking. I do understand the cause of this since I'm trying to cram in a portrait framed image ("native" OR desktop mirror (as in not the Oculus Mirror program that is)) into a landscape canvas (OBS) and there will some croppage due to this. Looking at the end result in "All things VR" along with the newer video in the OP, it looks like your Game Capture is a bit less "zoomed in"/cropped than it does for me after centering the source (Ctrl-D). My capture seems to crop away more from the top and bottom than for you. Is that due to ... well, perhaps some difference in resolution or settings in DCS somehow or just that you're working your magic when setting up the OBS source in your scene? :)

Tab is the default hide/show buttom for the chat if if my mind doesn't play tricks on me. There is no built-in VoIP. Third party software is needed and which one is up to the server. Some use TS3, some use Discord, some (most? :]) use SRS. Some uses a combination of multiple. Check the server briefing/description on what VoIP software to use :)

Just a quick heads up, not all things on wikipedia is the absolute truth and/or the numbers are from when deploying in optimal conditions. Are all your AIM-120 deployments done in what would basically be a lab environment where all the parameters possible is truly optimal? :)

Although I'm "on you side" for the sake of the argument, ED has no responsibilities to how mods are written and what compatibility to break and not. Mod-makers have to adapt to the changes ED makes, not the other way around. Just check Arma3 that was meant to be modded right from the get-go; altho the devs were sometimes good on announcing the upcoming changes that was far from the norm. EDs policy is quite QUITE different and most mods are basically hacks in lack of better words. If you want it fixed, post in the mods' thread.

I strongly suspect it might be the test bed for IASGATG-inspired/copied missile tweaks along with guidance rework. This is a fine time to live in as a DCS:er! ... altho the wait for all the upcoming goodies is excruciating! ;)

So what use are the changelogs nowadays if they omit pretty much the biggest changes (especially for a new flagship product even tho WIP)? Does the content creators hate the person responsible for the changelogs and doesn't tell him/her shit? Is the mindset that it's xmas year 'round and its meant for us to find "happy little accidents"? Bad communication between teams? Product in WIP so changes aren't classified as real changelog items until "completed" and to be added at a later date? Not meaning it to be rude altho typing some of the stuff jokingly, just trying to get the mindset or policy :)

lol. The mother of all damned if you do, damned if you don't kinda situation :D

Not a bug, here are the specs (if I'm not mistaken, feel free to correct me ofc :D) for the AN/ARC-210: 30.0-87.975 MHz FM 108.0-117.975 MHz AM (recieve only) 118.0-155.975 MHz AM 156.0-173.975 MHz FM 225.0-399.975 MHz AM/FM So the reason FM/AM disappears is because you cannot change between AM/FM on 30.000 since it's a FM-only frequency, by design.

Not sure if it's the same underlying cause, but getting wild rubberbanding is super easy 100% reproducible by just going into the F10 map even on a simple mission with two aircraft in the air (tested with separate mission per aircraft; 2 A-10C, 2 M2k, 2 F/A-18C) and no other units or logic placed. Two aircraft set to client, default loadout, save&run. Entering F10-map creates about 3-5 seconds of rubber banding, teleporting and "false" location jumping, exiting the map about 4-8 seconds later and again rubber banding galore for a couple of seconds. Tested with "dedicated" server running i7-6700, 32GB RAM, onboard intel gfx, SSD, 1Gbit/s connection (40ms (-+5ms) ping to both clients) and player hosted server running i7-4970k@4.7Ghz, 16GB RAM, much faster SSD than above "dedicated", GTX1080, 250dl/50ul connection with second player having 20-25ms ping. Same behavior on both servers with +-1 second variation on the flubber-fest.

Instructions on how to generate a dxdiag.txt: Either go to start menu and select run or Win+R and type dxdiag and press enter/click ok. Let the green bar in the bottom left work it's way to the right and once it disapears, click the bottom button "Save All Information". Save the file somewhere and attach in a post.

There's no general way of communicating in MP but very commonly used is SRS, Simple Radio Standalone by Ciribob and MorpheusXAUT found here: https://forums.eagle.ru/showthread.php?t=169387 In the end it's up to the server owner so check the briefing or server description on whatever server you're connecting to for details. Some use TS3, some use Discord, some use SRS ... or a combination.

TDC axis mapping is there and working like a charm for me running latest OB (which is identical to release at the time of writing). I'm using TMWH throttle with DeltaSims analogue slew replacement.

Like the linked news post says: "autumn 2018" ;) No further details about that has been released.

It was in one of the recent news letters after the very popcorn worthy threads created in the last months regarding mostly MP-related stuff; https://forums.eagle.ru/showpost.php?p=3565024&postcount=150 (last part) Popcorn threads: https://forums.eagle.ru/showthread.php?t=215348 https://forums.eagle.ru/showthread.php?t=215654 (split off from the first one)

Hi there! Only got a single answer and that is for: 1. In all the mentioned aircraft you control SRS through the regular in-game cockpit radios, not the 2D-interface.

Got my analog version in the mail this friday and installed it yesterday. A bit fiddly getting the old shit-nipple out but a very straight forward installation. And what an upgrade ... oh man. After just 10 minutes of some A-10C action and some curvature tweaking it's as perfect as one could wish. No more camera-randomly-stops-slewing and back'n'forth to get the crosshairs on exactly where you want it to be. Worth every penny and strongly recommend it to anyone not happy with the original slew. GREAT job Delta and even tho I'm an atheist, you're doing gods work here :)

there are replies in the "official" thread about that; https://forums.eagle.ru/showpost.php?p=3565661&postcount=200

Roger, thanks for verifying. I'll be making a proper post in the bugs section with tracks and everything as soon as I have the time to do it.

Just to be clear and repeat my post above, they were dropped in FF mode (Free Fall), not RET mode (retarded) and yes, 14k feet :) Visual inspection by pressing F6 was made and they did indeed drop slick, as programmed, in all of the attempts. Ofc I don't expect pinpoint accuracy with any unguided munitions but as with a regular Mk82s (as in non-SnakeEyes) I also wouldn't expect being several miles off-target in a no wind scenario.

Semi-necro but just wanted to check if I'm doing things incorrectly or not with the SE's. So, this is my 2 setups for 2 different tests; 2x Mk82 SE set with AUTO, MNOSE, FF, single bomb per pickle. Waypoint designation. 500kts, 14000ft. I fly fairly straight and fairly level. Bombs hit several miles behind/long of designation. Same setup but with CCIP set (and ofc no waypoint desig). To even see the cross at the end of the DIL/BFL I need to do more than a 60 degree dive. This tells me that no matter what DRAG you set the SE's to they are always calculated for a RET-release in the HUD. In regards to the latest OB fix; "Mk-82 Snakeye bomb always releases retarded - fixed", so remaining "bug"/not completely implemented or intended behavior? Has anyone else tried this? :)

To be fair, they said nothing about tweaking effectiveness/damage model, they only mentioned accuracy of CCIP/AUTO with cluster munitions along with added HT-functionality.

Are you actually expecting a patch next week on an unidentified problem you are experiencing that hasn't been accepted as a bug and/or not marked as reported by ED? :) If your solution is a new mobo you probably shouldn't waste anymore time and buy a new one tomorrow.