KungFu

Kinda like the F16 FLCS?

@NineLine Well I installed the dedicated server on my secondary PC and ran the downloaded GF track file. I think either GF sets the fog level through scripts or at the time of joining the server the fog was off because the trk file had it off. I was able to spot targets with George just fine. I edited the mission and turned fog to auto.....George can not see targets even when there is no visible fog and the target is a couple hundred meters away. So then I ran the same mission from the ME (fog on auto) and George cannot see targets I imagine all missions with fog turned on to auto or like others have tried more advanced with differing levels will have this problem. So not related to dedicated server + fog (auto), it's simply fog, maybe in this case it being set to auto. I did not try a more advanced fog setting, but fog auto definitely will prevent George from seeing stuff even with no visible fog on ME launched and dedicated server missions.

I'm beginning to agree with some that this may be a dedicated server issue along with fog or some other setting as I can get George to work fine on several MP servers, but unsure if fog is is on those. I took the GF mission (the downloaded track file) and ran it from DCS from the ME and George could spot stuff. I could not get it to work as MP (not dedicated) as my mouse would not work in the cockpit, very weird.

Yeah it seems totally random between what people are seeing. It being Christmas Eve maybe the reports are lower than they'd normally be.

He works fine in SP for me on the Cauc Dam Mission. In MP he does not on the server I play on (and I think we are talking the same MP server(s), two other servers I joined worked ok

I can get him to work on the SCUD hunt mission on the pad and detecting all the friendly units, however he doesn't work on a popular MP server I play on where he detects nothing.

Honest question and not meant to be a troll, how does something this obvious make it through testing?

So just getting back to the Viper after years of flying helos. Because I mostly fly helos, I have a center mounted stick with an 10cm extension. So my issue is that right after rotations on takeoff and on final approach landing, she is squirrely as well a squirrel on crack. Almost like I'm rocking the rudder pedals left and right. (yes autopilot is off) In normal flight it feels pretty good. I don't remember it being like this when I flew it last. My settings are below, should I be doing something else.

Well crap, the SRS overlay is causing this...good call. What I don't understand is that SRS is used so much, I'm surprised this hasn't been reported like .... every day. But, the fact that DCS cannot properly handle something like this still means it's a DCS issue.

Well the confined to window didn't change anything. SRS is pretty darn common so I doubt it, but I'll disable it and try it out

Maybe the confine option is making it do it, will have to check when I get a chance.

This is very annoying and it happens on all aircraft. Had the issue on two different PCs and two different VR headsets. Someone recommended LALT C. This only works momentarily and the white dot of immersion killer comes back. Demonstration of issue in video:

This is still an issue today, reported but not fixed?

So started flying with the FCR as I fly on a MP server that limits them of course. I come up to an area with an SA6, site is huge with all kinds of launchers and supporting vehicles and a couple of shilkas. They are on a pretty flat open area. Im in VR and can see them easily, I would say there were 20 or so vehicles about 2km out Hit the FCR, nothing. Make sure it's covering the area, yep....set to continuous...no returns. I'm at like 100ft agl and I then play with the elevation, nope nothing returned. However like 10mins earlier this thing was picking up stuff behind trees, so I know it's working. I wind up having George find them and fire on them with tads designation. Most of them missed, in fact they hit the exact same empty place with different targets. (Yes I made sure the lased and got valid point tracks) So what other than the obvious (FCR looking elsewhere, wrong elevation, etc) what would cause it to not see things that are obviously there and out in the open?

Coming from a base station tracking which was smooth as butter, the Crystal seems to want to constantly adjust a bit when looking around in the cockpit and to some extent outside. I'm sitting in front of a 49" samsung G9 and my desk it pretty clean so I'm wondering if there aren't enough "targets" or if the monitor is throwing it off, especially since it's curved. Windows are all covered, firmware is the latest. I've seen these IR pads on amazon and wonder if they are worth trying or am I barking up the wrong tree.

Figured it out, seems my stick wasn't perfectly calibrated. I use instant on the Huey and central on the apache. So the trim function in DCS must look for a perfect center on the stick axis, if it is not then it subtracts the value from the trimmer position. (The red X moves after I hit the trimmer button, usually about half the distance from where I had it when I hit the trimmer) And on helos, as everyone knows a tiny bit makes a huge difference

So I get this on the apache and the huey, I have not tried it on anything else yet. So I hit the force trim when it's where I like it, release the stick and it does not trim to the exact position I hit force trim, it's usually a bit off. For example I trim forward, release the stick and the trim position is not as far forward as where I had the physical stick. This is extremely irritating and I can't think of what in the world can be causing it.j Any ideas?

Just got my Beyond yesterday and I'm not impressed with the fitment at all. There is pressure on the bridge of my nose and the left side where the usb plug is, there is a gap and I can see daylight out of the corner of my eye. As far as moisture, yeah it's noticeable even with the fan cranked it gets pretty warm. The bottom of the headband also rubs the top of my ears and it's noticeable, maybe I need to adjust the bands but they seem to fall from their original location over time Glare is an issue, in the f15e from almost sunset to dark in game there is a band of glare just below the center of the view. I played around with the brightness settings and it really didn't help too much. Tracking, well you have to get your lighthouses nearly perfect due to the size of these things. It lost tracking several times at first with the same locations when using my index. I do like that I can wear my higher end headset, I like the weight. Image clarity is really good. Do I think they are worth 1k just for the headset.....NO.

I don't think it can be moved unless something has changed, I've asked this before and got a "NO". The VR implementation of the George interface is not optimal. First it's displayed at the top center in VR and it's co-mingling with part of the canopy an just looks unprofessional. It would be nice to be able to turn it off visually and "communicate" with George without it visible. He is pretty good about telling you what he is doing. When presented with a target list (which will have to be visible), the opacity is such that certain backgrounds make it difficult to read, it also is out of the sweet spot of many headsets which makes it even more difficult to read easily It would be nice to be able to move the interface as well (like many other 3 party apps do), would also be nice to be able to set the opacity of the target list. Hope George gets some love soon, he's been single since early access release date I think.

Ah, well that explains the tacan issue...but yeah getting AP to work reliably is a pain. Kinda reminds me of the Harrier's system at launch being a bit touchy

Ok, so most of the time when I enable alt hold, it never holds alt (yes trimmed for level flight) Sometimes cycling AP helps God forbid I set an altitude, cause it rarely holds that alt. Set for 20k, heads down ... look up a few moments later and I'm at 30k. Don't get it, tried everything even trimmed out at 20k, set AP and then it does to the moon Alice. With regards to steerpoints, it works most of the time, but trying it with tacan boxed it gets pretty confused, sometimes trying to follow a previous steerpoint. Missing something other than cycle on/off a few times to get it to take?

I use an Index, my system specs in sig. I wound up fixing it by completely removing steam and steamvr and reinstalling. This makes no sense to me as nothing changed other than DCS. Could be a red herring but it's fine now.

[Running MT] So after this last update, I get severe tracking stuttering that comes and goes (all planes I own) The framerate is steady at whatever refresh rate I select (Index) I do have process lasso DCS and SteamVR on separate P cores ( I did this to try to fix the issue, it does occur without process lasso running) I can get say the apache and have smooth head movements, then all the sudden stutters wherever I look. It's not a headset issue as other games are just fine. Sometimes switching the refresh from like 90 to 80 and vice versa clears the issue and not long afterwards it comes back. I am not using DLSS, but am using DLAA and tried TAA with no change. This never happened until this update so I assume it's a DCS issue. Anyone get the same?

I had to put curves and saturation in for the Apache, even with a 10cm extension on the cyclic

Yeah, it lagged when I entered the mission, I have an Orion 2 throttle that must have had the gear switch down and I didn't notice the gear down due to the studders on mission entry. Didn't even notice the Master Caution either, it was off when I was able to take descent control Anyway, from what I'm hearing these seems to be normal behavior and is repeatable. This is fine, just wanted to know why I was seeing it.