robgraham

Tried that didn't do anything, got the flicker within 2 minutes of being in the air.

Nineline, you may also want to ask Rik about it as well, he posted as mentioned a 'confirmed' when we reported this last patch and there wasn't anything in the patch notes saying that it may have been fixed..

yeah even latest drivers didn't fix it for me.

you mean it's like some ones taken a point and shot it up into the sky and looks like random spikes etc? I'd suggest.. 1. running a DDU and reinstalling your driver. 2. checking your power cables etc. 3. making certain it's NOT happening in any other game etc. normally it's a sign of either a driver issue or a card issue though.

Same, otherwise i'm up to date, on the drivers.. Watching the frame times just now while i got the flicker there is nothing out of the ordinary compared to the rest of it.. (other then DCS only leveraging 50% gpu). Can say this only started with 2.5.4 and that Rik (i think it was rik) had in the VR forums at least acknowledged he'd confirmed that it was happening in vr last release, but yeah i'm getting it in both vr and non vr. https://forums.eagle.ru/showpost.php?p=3728259&postcount=37

The other one is maybe Nineline it's driver related? I don't know what your on but i'm running Nvidia GTX 2070, Driver version is 417.35

I just deleted both metashader folders, + fxo and it's happened on vr and monitor nineline, the settings are attached. If I drop water to medium and loose the screen space reflections on the water (which makes it look like crap) it fixes the issue, If I leave them as it is here then I get an intermittent flicker on the monitor when in normal and left eye mostly in vr though at times the right does flicker as well. It is almost as if a draw call is taking too long but I've not actually sat and looked at the Frame Times yet to see if that is actually the case (About to now)

yeah water high is still causing this issue :(

The block update adds the JHMCS to the C, the 'glasspit' is already there that was the purpose of the c update. For a CAS bird the JHMCS would add look, see, designate capacity as you do currently through the hud. The biggest thing that I really want to see.. seems I very much doubt we will ever get a real version of SADL is a set of fricken BINOCULARS, they are Part of the basic kit for the hawg, allowing Them to visually see and I'd targets with out the pod etc but we don't have em heh But ok'd settle for pbr and fixed bugs

May have found the cause for this at least on my rack box.. OVH (whom i host through) apparently automatically turn on certain things including on 'Game' boxes the 'GAME' Firewall.. which going and looking surprise, surprise blocks traffic on UDP ports that aren't defined. Needless to say I've.. removed that, leaving only the DDOS mitigation protection and I would hope that DCS isn't pinging enough during a server listing to go 'Hey I'm DDOS'n ya server ' hehe. will see over the next few days i guess.

The issue is that I'm the admin of the server not the one with the issue, i can't make them try anything i can only deal with them complaining at me over it. If you read the first post I see the server fine.. and i'm in a different state to the one were the server is.. I've a feeling that the person in question has something blocking it yes, especially given he only appears able to hand me an IP6 address when I asked so i could see if a trace worked.. However I've also had it happen on a machine I -could- remote desktop to (as the friend on that machine let me) and when that happened I could get a 20ms ping reply from the server on his machine, but not a connection to it , despite on my machine again different town over 400km away.. having no issue and then 15 minutes later it just suddenly 'work'.. no rhyme or reason to it. Now yes I get your point 'somethings blocking' but again when nothing changes in that 15 minutes and you have a machine that can ping the server but get told the server isn't online even when the ports open and others are on it and their ports are open.. it makes you wonder what is going on.

Can confirm DCS was the same version for them and yeah as Doctor Vixen said they can try the Ip and get server offline.. the weird part is too that you can PING the server and get a response from their machines. it would be really interesting to know what causes a machine to show up in the list and what doesn't though if all the servers are reporting to the central 'authentication' server at Eagle's end.. you'd think that if they are all registering there as online then on client machines etc when they go to multiplayer they should all just show up and if you can't connect either give the time out of the like.. We've one guy who literally can't see the server at all, yet every one else can for example and yes he's on 2.5.4 :P if i host he can see me fine for example..

Use S_EVENT_ENGINES_SHUTDOWN to get the trigger and then check that speed and altitude are below set parameters.. ie speed less then 1 and altitude less then 10 radar. you could also use something like the M.O.O.S.E scripting stuff

Figured I'd add a few notes to this for any one who maybe trying to get things running on a Windows 2016 box that 'has' the right equipment....... 1. make certain that the 2016 install is the one with the Desktop Experience items.. else your going to have to make certain to get the Virtual Machine items installed and working from the start. 2. By default the Desktop experience items do NOT include Direct Play and a few other items like this.. you may find you have to install them to get DCS to work. 3. Make certain you don't moronically name your Autoexec.cfg as Autoexec.cfg.txt and then wonder why things aren't working properly ;) 4. Server 2016 is very aggressive on port protection so you'll have to cross check all that as well. 5. Make certain windows is up to date... My suggestion if you can run 2012 or 2008 server but a lot of data centres aren't giving licenses for these guys any more :/ at least over here in Oz.

Not 100% certain Emmy, I've had one person claim it just says the server is offline while another (the person who let me RD) into his machine at first was doing that and then it connected.. fine. It's one of those weird ones were people are like its not there .. I go look in multiplayer and it shows up fine, connects fine etc.. and i'm like I can see it, I can connect to it etc. Server in question is TGW Dedicated FYI. and one guy just posted me this https://imgur.com/a36D5PR

So we have a dedicated server that runs at a data-center in Sydney that's been running rock solid and all fine but we have some weirdness happening, At times some can't see the server in the server list at all and/or get told the server is offline even while others can connect to it at that very same time and the DCS World multiplayer server list on the 'your account' list shows the server up fine. Having Done a RD to a friend who was having the issue I noticed that he was seeing 1 or 2 'less' servers then I was I had for example 207 and he had 205. Now as it's a dedicated box it's on a NIC so of course UPNP is not there but the ports for DCS are all open and when this has been happening I can connect to the server fine and i'm not anywhere close to it (completely different state) I'm wondering if any one has any suggestions on what might be causing the issue Lua: Lua CPU usage: metric: average game loading: 39.7098 % 2019-01-06 06:20:36.737 INFO NET: server has started 2019-01-06 06:20:40.747 INFO NET: No UPNP devices found. 2019-01-06 06:20:40.747 INFO NET: Successfully set up Dual-Stack socket, using both IPv4 and IPv6 2019-01-06 06:20:40.747 INFO NET: Listen to IPv6 on port 10308 2019-01-06 06:20:40.753 INFO Dispatcher: loadMission C:\Users\root\Saved Games\DCS.openbeta\Missions\CASCAP-Withrange-LSO-1-update.miz 2019-01-06 06:20:40.859 INFO WORLDGENERAL: loading mission from: "C:\Users\root\Saved Games\DCS.openbeta\Missions\CASCAP-Withrange-LSO-1-update.miz" 2019-01-06 06:21:05.936 INFO NET: Loading mission: "C:\Users\root\Saved Games\DCS.openbeta\Missions\CASCAP-Withrange-LSO-1-update.miz" 2019-01-06 06:21:05.936 INFO NET: Registering server as 139.99.144.189:10308 (port is assumed to be open) 2019-01-06 06:21:05.936 INFO LuaNET: Starting Dedicated Server... 2019-01-06 06:21:05.936 INFO LuaNET: SLMOD INFO: Modifying netview... results: , true and as I've said for some it's showing up fine for others it's either not in the list at all or intermittent. Any suggestions etc would be grateful

Rik, I have had it happen both in VR and Non Vr, just so your aware.

part of it is you have to remember we are in a computer.. some times things have to be slightly 'cheated' to allow for that fact and that you can't sit there and go to the JTAC ok, I need a spot code 1766 for the first 2 runs but when my buddy comes in he needs 1688.. Instead the JTAC gives us the code and we 'pretend' that we are just making certain that we've checked our bombs and the arming computer are all set up right as per our mission planed code. (which we presume is the one the JTAC passes us) Otherwise Multiplayer etc would be a nightmare to say the least.

well in reality the damned things suffered that many seeker fails, motor fails etc that outside of the few 'tests' they were never overly effective (in US Service) for the price tag.. It's why you see more and more Tom Cats towards their EOL running AIM-7/120c mixes as by the end of 2004 the 54's where taken out of service. The Irani's used them though with great effect (54 kills from memory). During the Gulf war the Iraqi's tended to turn and run when they were fired on by the 54, basically forcing them to waste the shots.. So your best bet normally is to if they launch long enough away turn and run against the first set.. then go defensive and try and ground drive them if your closer, hopefully maybe we get some of the seeker and motor issues modelled and every one can experience the swearing the real pilots did ;)

It means - Comm Menu.. So on the Hornet Comm1 or Comm 2 you get the F1,f2,f3 etc menu's F10 is 'Other' which is what these type of scripts etc live under.

Having this happen as well at first thought that something had broken.. really annoying when your doing a formation landing run and lead lands and suddenly bounces up into the sky then back down then up then back down.

Not that it should be needed given as mentioned by fael it's easy to reproduce, this is from the ready at ramp clearly shows both with key binding and with switch that the retract isn't working unless the probe is fully extended first. Steps to reproduce: 1. Start the aircraft 2. move the probe switch out then before probe fully extended back to retract. 3. observe that the probe is not retracting as it should as the switch is in the retract position. bug has been in since EA Release. probeissue.trk

This needs attention I agree can't see a bunch of the options at times and have to guess that your hitting the right set..

The reason that most are jumping to that conclusion is because based on how Wag's worded the post that is how many people are working on the Hornet systems at the moment or to take a direct line "We, for the most part, have four guys working on Hornet systems and here is what they are working on:" now most are missing the 'for the most part' which means they are likely ramping up/down as required but he does specifically state 'four people' on the hornet system team there, what I find a little more concerning and also a little more a 'so thats why we still don't have agr' is this line: "Supporting tech like the A/G radar (we lost our original engineer on this) and an improved FLIR rendering system are in work and are fundamental to A/G radar implementation and the ATFLIR." It explains why we don't have the Air to Ground radar, but doesn't give any information on how much of a delay we can expect on those features because of the loss of the engineer working on it. And for some of us the Air to Ground radar was the big selling point (other then you know hornet) and with out the AGR then the hornet doesn't even make a lot 1 hornet let alone a lot 20 ;). But it's early access I get that and Wag's has been very open with all of us about the majority of delays on things. What I think has people concerned maybe the most is that there was a steady stream of updates prior to the Northern Hemisphere's summer 'break' then since that break a major reduction in the speed of the updates and the 'depth' of them so to speak. Of course at the same time I think people also tend to forget that some times things just take longer to happen and throwing more people at them doesn't necessarily make it 'faster' either, the AGR is likely a great example of this (as much as I really want it) which is that they have to do the core API for the main sim, which likely doesn't need a dedicated Hornet coder at the moment to do the work, same goes for the ATFLIR that's core systems work though for some of us ED would likely find if they asked again we'd rather see those systems 'sooner' then 'later' but then you ask this community anything you get several thousand different replies ;). But the TLDR version is yes people are saying/believing that there are only more or less 4 programmers working on the hornet, because if you read wag's own post it reads as we have 4 dedicated programmers on the hornet.

This ones fairly easy to reproduce, go to your HSI Data, UFC, insert a new waypoint or go to modify an existing, enter an altitude you'll notice that it enters as 1 ft lower then the altitude entered on the UFC. It's not a 'big' bug, but it is a bug. example I entered 3172 FT for a target and it resulted in 3171ft being displayed & when i entered 3171 it displays 3170 etc.