Ciribob

Server restarted - instead of crashing it hung, which means it didnt get restarted automatically Should be back up shortly :) Server IP is 91.205.184.66:10308 and at the bottom of the http://gadget.buddyspike.net/ if it doesnt appear in the server list

^ please :) Sent from my ONEPLUS A3003 using Tapatalk

You'll have to look in the windows error logs and tell me what is says. Get me on Discord and I can can help more easily: https://discord.gg/baw7g3t Do you have anything in your clientlogs.txt in the folder where you installed SRS? Have you reinstalled using the SRS installer the latest version? Sent from my ONEPLUS A3003 using Tapatalk

Please post in the CTLD thread as this old version is no longer supported. :) Sent from my ONEPLUS A3003 using Tapatalk

Do you have MSI afterburner running? If so turn that off and try. It crashes SRS when it tries to inject an FPS counter :( Have a look in the windows error logs in event viewer, should say why it broke in there Sent from my ONEPLUS A3003 using Tapatalk

The Defenders always spawn at the center of the area, usually near a structure. The idea is to always bring a JTAC to help find them, or if you've got help a few low passes and the tracers should help you to spot them. Viggen will eventually be moved to just Red, with Harrier on Blue but not sure when that will be. Repairing a Farp does not mean that you'll be able to rearm and refuel - the right units need to be present and the group that gets repaired is picked randomly. You may have to drop a few repair crates before the Farp is fully functional if you get unlucky. Map is reset as are sides.

BlueFlag does use the logic of uncontrolled Airfields as it's unlikely there will be an ATC on. However, please do use 251 for Blue and 124 for Red for all takeoff and landing notices. If there is an ATC on, please listen to them as you really don't want to hinder your team by smashing into a friendly :) Frequencies are here : https://docs.google.com/spreadsheets/d/1LYS-K2EBGBZ1RjD0UGUdOkAXJBGw3mmRQZ2cSsdbJao/edit?usp=drivesdk And also available via -freq typed in all chat and linked too from the website. Sent from my ONEPLUS A3003 using Tapatalk

Are you on Openbeta or release? The BlueFlag server is running open beta and seems pretty stable now. We have intermittent player disconnects but no server crashes as such. Sent from my ONEPLUS A3003 using Tapatalk

Can you get a short track of the issue? Any version will do. If I can replicate I can report. Personally I've seen massive improvements in OB, it's why BlueFlag is back online so I'd really like to replicate and report! :) Sent from my ONEPLUS A3003 using Tapatalk

Have you tried the latest openbeta? There was a stutter bug fixed for Huey and Mi8 It's not in release 1.5 - not sure about 2.3. Sent from my ONEPLUS A3003 using Tapatalk

Can you PM me a recording? That sounds very odd... Im Just using the built in .net stuff for the interface, it's a Microsoft technology so no idea why it would do that. Are you running anything like MSI afterburner or any other program that injects an FPS counter or overlay into games? I would guess something like that is trying to inject something and failing as it's not a game. I'd also on the off chance install this : https://www.microsoft.com/en-gb/download/details.aspx?id=8109 Reinstalls directx 9 which might help (it's what WPF .net uses under the hood) Sent from my ONEPLUS A3003 using Tapatalk

Thanks! I've been looking for a new place to stick this code that gets called on startup. After Christmas I'll update the video and instructions with the new location. Sent from my ONEPLUS A3003 using Tapatalk

Definitely dont enable allow more input devices - that'll not help - the whitelist way you tried first is the way to go The fact its there twice is odd - can you tried just unplugging that device (from USB) and seeing it it still appears? I've not got any devices that I can diagnose on and away at the moment. Wont be able to look till wednesday at the earliest. If you cant get it to work - add to the blacklist.txt and just use keyboard or other inputs as a temporary measure. Between the 1.3 and 1.4 versions I upgraded the library that handles Input so guess theres a bug in that library somewhere which is why it stopped for you. If there is a misbehaving device, it stops all devices from being bound which is why when you press set, you cant assign a device.

Server running Latest Open Beta - Please update! Server is on the Latest Open Beta patch as this has this fix added - https://forums.eagle.ru/showpost.php?p=3333229&postcount=26 as well as the stutter fix. This means autorestart script can work fine as there is no blocking DCS window (different to windows prompt so can't be detected). Massive thanks to ED for fixing it so quickly! D2M has been removed - and was for a while when the server was previously up. Search this thread for the previous debate on the subject :) It's not coming back for now, sorry :) Looks up and people are on so just try forcing DCS update?

Here are a copy of your logs: Attempt to Load Whitelist from C:\Program Files\DCS-SimpleRadio-Standalone\whitelist.txt File doesnt exist: C:\Program Files\DCS-SimpleRadio-Standalone\whitelist.txt Attempt to Load Blacklist from C:\Program Files\DCS-SimpleRadio-Standalone\blacklist.txt File doesnt exist: C:\Program Files\DCS-SimpleRadio-Standalone\blacklist.txt Starting Device Search. Expand Search: False Found Device ID:6f1d2b60-d5a0-11cf-bfc7-444553540000 Mouse Usage: Undefined Type: Mouse Adding Device ID:6f1d2b60-d5a0-11cf-bfc7-444553540000 Mouse Found Device ID:6f1d2b61-d5a0-11cf-bfc7-444553540000 Keyboard Usage: Undefined Type: Keyboard Adding Device ID:6f1d2b61-d5a0-11cf-bfc7-444553540000 Keyboard Found Device ID:19971997-0000-0000-0000-504944564944 F-22 Pro Usage: VendorDefinedBegin Type: Device Found Device ID:19981998-0000-0000-0000-504944564944 F-16 TQS Usage: Generic Type: Supplemental Found Device ID:c52b046d-0000-0000-0000-504944564944 USB Receiver Usage: Consumer Type: Device Found Device ID:c52b046d-0000-0000-0000-504944564944 USB Receiver Usage: Generic Type: Device Found Device ID:c52b046d-0000-0000-0000-504944564944 USB Receiver Usage: VendorDefinedBegin Type: Device Found Device ID:076306a3-0000-0000-0000-504944564944 Saitek Pro Flight Rudder Pedals Usage: Generic Type: Joystick Adding ID:076306a3-0000-0000-0000-504944564944 Saitek Pro Flight Rudder Pedals Found Device ID:13691038-0000-0000-0000-504944564944 Sensei Raw Gaming Mouse Usage: -64 Type: Device Found Device ID:c52b046d-0000-0000-0000-504944564944 USB Receiver Usage: -68 Type: Device Found Device ID:c52b046d-0000-0000-0000-504944564944 USB Receiver Usage: VendorDefinedBegin Type: Device Found Device ID:13691038-0000-0000-0000-504944564944 SteelSeries Sensei [RAW] Usage: Consumer Type: Device Found Device ID:19981998-0000-0000-0000-504944564944 F-16 TQS Usage: VendorDefinedBegin Type: Device Found Device ID:c52b046d-0000-0000-0000-504944564944 USB Receiver Usage: VendorDefinedBegin Type: Device Found Device ID:19971997-0000-0000-0000-504944564944 F-22 PRO Usage: Generic Type: Joystick Adding ID:19971997-0000-0000-0000-504944564944 F-22 PRO Found Device ID:508106a3-0000-0000-0000-504944564944 Programmable Hotkeys Usage: Consumer Type: Device Found Device ID:13691038-0000-0000-0000-504944564944 Sensei Raw Gaming Mouse Usage: Consumer Type: Device Any device that is "added" can be used by SRS for input As you can see (and the fact its not working) you can see that SRS didnt add Found Device ID:19981998-0000-0000-0000-504944564944 F-16 TQS Usage: VendorDefinedBegin Type: Device Easy fix though. Create a file called whitelist.txt C:\Program Files\DCS-SimpleRadio-Standalone\whitelist.txt Add the ID of your device to whitelist.txt 19981998-0000-0000-0000-504944564944 Save the file - restart SRS and it should work. Following the same steps you can add any other devices it ignores (as its not sure what to do with a generic "device" ) Hope that helps!

What is your throttle? If you post your client logs.txt I'll show you how you can whitelist the device so it works :) Sent from my ONEPLUS A3003 using Tapatalk

Frequencies for the Harrier radio should be fixed. As alpenwolf says, second radio isn't working yet and is on a fixed frequency. Sent from my ONEPLUS A3003 using Tapatalk

Type -freq or -frequencies in all chat to get them same as in BF Nevada Description and info will be updated at some point but the PDF I would guess won't be done for a while Sent from my ONEPLUS A3003 using Tapatalk

This is definitely working in the latest 1.4.5 version as it was patched to fix this. I'd go to saved games/dcs.openalpha/scripts, backup and then delete the folder I'd also delete the file for SRS in saved games/dcs.openalpha/config/SRSConfig.lua Then run the SRS installer again to sort out scripts folder. Should fix it :) Sounds like you've mixed up the paasthrough device (right drop down) and output device (left drop-down) Set the right drop-down to no paasthrough / nothing and use the left one to pick the right output device. Always test with preview audio to check it's all working Sent from my ONEPLUS A3003 using Tapatalk

That has been reported to ED, hopefully be solved in a patch soon :) Sent from my ONEPLUS A3003 using Tapatalk

Thanks! Thats what I meant by warehouse rebuild :) We do it quite a lot as its usually the only way to fix the Mig21 loadout. Just deleting the warehouse file and reopening the mission in the editor usually does it.

Nope sorry, it's literally just working as of this patch, so not going to push it any more other than some harrier additions and map tweaks. Once we've had it stable for weeks running with 60 players then it's a maybe but a long road to go for that! :) Sent from my ONEPLUS A3003 using Tapatalk

No - that was disabled a while back due to lag, sorry. Sent from my ONEPLUS A3003 using Tapatalk

Loadout issues are due to warehouse - needs to be rebuilt Mirage alignment is enforced and intended. :) As I said before, very early test but looks promising. Just need to get auto restart sorted! Sent from my ONEPLUS A3003 using Tapatalk

Switched to 1.5 server : https://forums.eagle.ru/showthread.php?t=175262 Password is blueflag In very early testing as crash recovery is not working yet. Sent from my ONEPLUS A3003 using Tapatalk