Kid18120
-
Posts
263 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Kid18120
-
-
13 hours ago, Corrigan said:
Has this been fixed in the 14 months since? Anyone know?
Nope, still there like that.
It's annoying AF! Occasionally i do see some full green circle or full red triangles but they last not too long and turn to the usual white brick hiding the datalink track-
1
-
1
-
-
18 hours ago, MsKatze said:
I also encountered this problem, but I observed from Olympus that every time this situation occurs, the server-side FPS will be displayed as 0. At this time, I only need to pause the server and delete the redundant AI units (using Olympus) to restore its FPS to temporarily solve this problem until the next AI number increases.
Since the last update, the server usage has obviously increased, and I had to cut some game content to make the server stable.
Please forgive my poor English ability, I hope you can understand it
Thanks for the reply and yes, it's clear what you mean.
However, our server is set to that it goes into pause when no clients are present and the freezes always happen while noone is on the server.
Olympus won't respond as the server is completely frozen and windows' task manager reports the DCS_server.exe as "not responding" and won't move from there until we kill it. -
Yes after a restart of the affected instance(s) it goes back to normal again.
For now only instances 1 and 3 have been affected, with #1 being twice now, while #3 is the first time.
Seems a bit of a random thing. Might actually be related to ED's servers -
We don't use the internal voice chat so it is disabled via server config.
It was also my understanding that the webrtc port was deprecated and all traffic routed through the game port (i.e. 10308).
Our ports setup is:# instance1
DCS 10308
WebGUI 8088
# instance2
DCS 10309
WebGUI 8089
# instance3
DCS 10310
WebGUI 8090 -
Hello,
as per title, i have 3 instances running on the same machine, all 3 working fine but 2 of the 3 instances have this error in dcs.log file and are not showing on MP Server List nor under "My Server" from my account. Though we can connect just fine via direct IP and everything else works as expected.
"""""""""""
ERROR ASYNCNET (1916): HTTP request dcs:server:update failed with error 7: Couldn't connect to server
ERROR ASYNCNET (Main): Server update failed with code -7. The server will be unlisted."""""""""""
Already checked Windows firewall, we have all the needed inbount ports opened, outgoing firewall set to allow all by default.
Anyone else having this issue and maybe found a solution? Other than restarting the server, which we already tried and obviously "fixes" the problem until it happens again.Thanks in advance!
-
We're now running off a new fresh system install with all the bells and whistles except LotATC, seems to be stable. Sucks but hey, it works
-
22 hours ago, HC_Official said:
we removed LotATC from our server a while ago as it was causing freezing/crashes
We thought about doing so as well but we do actively use it, plus on the old box it seems not to cause issues. Same software version for everything except Windows 10 on the old box and Server 2022 on the new one, so i think it's more likely a problem with either the new environment or some config/settings on DCS-side
-
Hi all,
we're experiencing a bit of a weird issue with DCS Server (modular installer version) on a fresh Windows Server 2022 installation on a dedicated server box.
To cut the text short, we have 3 instances of DCS server running which work properly but they do tend to randomly freeze (task manager shows them as "not responding" and not necessarily all 3 of them at the same time).Server logs were a bit of a mess so we cleaned up the machine and started the instances once again, so i will provide some logs as soon as the issue rehappens.
It seems like the issue happens after about 10-12hours of running time, though sometimes it happens on instance1, some other times on the instance3, or other times on 2 of the 3 instances.
In the meantime here are some more server related details:
- Server specs are: CPU Ryzen 5 7600X, RAM 64GB ECC, 1TB NVME SSD, running on a Windows Server 2022, no dedicated GPU
- DCS was installed via the dedicated server modular installer
- the user running on the server is the actual "Administrator" user with full access rights
- instances are all working on their dedicated saved games folders (instance1, instance2 and instance3 respectively)
- each instance has its own autoexec.cfg (see below for its content) where the only difference between the instances is the webgui port
- we have SRS, Olympus, LotATC and Tacview installed but currently only DCS, SRS and Olympus are being used
- running missions use DSMC and CTLD
- the 3 instances are running 3 different mission files, featuring light, medium and havy loads in unit counts
While waiting for the servers to freeze up to get proper logs, which i will post here as soon as we have them, i'm eager to get your opinions on what to try or check in order to troubleshoot the issue.
Things we have tried so far:
- Cleanup/Reinstall software used (SRS, Olympus, etc.)
- We were previously running on a local administrator user that was not "Administrator" so we switched everything back to use the actual "Administrator" account
- Change DCS, webguid, SRS and LotATC ports
- Running DCS_Server.exe as admin (Right click - properties - compatibility - run this program as administrator) ---> this is the latest change we made so we don't know if it might have fixed the issue, we'll see
Autoexec.cfg file content:
if not net then net = {} end
net.download_speed = 131072000
net.upload_speed = 131072000
net.use_ipv6 = false
net.use_upnp = false
options.graphics.render3D = false
webgui_port = 1234
disable_write_track = true
no_device_hotplug = true
crash_report_mode = "silent"Thanks to anyone who will chime in.
-
Thanks for the feedback Vader. Much appreciated
-
On 5/8/2024 at 6:28 PM, fjacobsen said:
I would think it would be part of EMCON - being able to turn off an emitter.
That switch has nothing to do with turning off the radar altimeter, it just alters the parameter visualized on the HUD.
What you would be looking for is the radar altimeter power switch located by the LEFT/RIGHT PYLON and FCR power switches -
Definitively not hardware / controller related. It happens at random times, seems a bit more consistent on MP rather than SP for some reason, but still very hit and miss.
Known workaround to get the antenna elevation "unstuck" are to cycle RWS/TWS or change the azimuth for the mode you're in (i usually just go spotlight holding TMS UP as it's quicker)-
1
-
-
Velcros are a common "mod" to attach protectors to helmets. I wouldn't stress over it.
-
3
-
-
As per the title, the default skin for the F16 (and a few others. i.e. Bulldogs,) have a "cut" in the color tonality between the fuselage and the wings, with wings being noticibly darker since last update
-
1
-
-
On 4/30/2024 at 3:14 PM, Lord Vader said:
In my own tests, I was never able to make this happen, even switching between RWS/TWS or with MRM override.
I will continue to try and catch it but so far I am a bit inclined to something related to hardware assignment. I tried both an axis and a button for the elevation, no luck so far.
It's still happening every now and then.
I doubt it's controller/hardware related as it happens randomly. It seems to be a bit more frequent if you are in TWS with a bugged target, then TMS RIGHT to start tracking it and somehow you lose the radar contant. After that point the antenna elevation stops responding until one of the workarounds is done-
1
-
-
I can confirm this.
Also i'll add the preset channels that don't show up seem to be working, it's just the channel indication that doesnt change until you get to ch.6. Both VHF AM and FM panels
-
Clear!
If you need more hands on the testing I can help side I can help.
I'm not too skilled on the scripting/coding but I can certainly test the build with various systems, especially for the A10C as I pretty much fly with it 100% of the time.
Just shoot me a PM with the details if there's a free spot
-
PS: I tried build 55847 and found no problems so far. Are you on latest Helios?
Thanks for the quick reply!
I'm currently on Helios v1.6.3304, did i miss a release?
Everything works perfectly with the "old" A10C, but not with the new A10C_2.
Some switches do work but i get no MFCDS nor other instruments working.
What steps could i try?
-
It's not unsupported, make sure you have the latest version. I added support two weeks ago. :)
If unsure, reinstall with the autoupdater
Sent from my HD1903 using Tapatalk
I found an issue with the A10C_2.
It all works fine for Radio1 (VHF AM) and Radio2 (UHF) but whenever I try to use Radio3 (VHF FM) instead of switching to it, it starts transmitting on the last radio i used.
Is it just my installation that has something messed up?
-
even if the interface for A-10C II isn't there yet, it should at least not break the viewport patch install. I am working on that now.
Do you have an ETA on A10C_2 support? (no pressure of course, just asking :) )
EDIT: As of the update that just dropped for DCS (2.5.6.55847), nothing works anymore, not even MFCDs export and the other few things that were working with Helios :(
-
Hi all..after latest DCS OB patch and after adding A-10C II - i am having issue with helios -- https://i.imgur.com/FxYBhzS.jpg? Anybody has the same prob?
Yes it's a common problem.
The new A10 is seen as a new module so i guess it will require new scripts to be released with an update for helios (hopefully soon :smartass: )
-
I had to bind coolie hat up, by default it was set to down and the down press mapped to nothing
Same here, seems to be a bug in the default mapping file
-
TGP not resetting with China Hat Aft
As per title, China Hat Aft short is not resetting the TGP, instead it starts LSS.
Steps to reproduce:
1- Make sure China Hat Aft is mapped in the controls
2- Move the TGP around
3- Press China Hat Aft Short
expected: TGP should reset to boresight mode
actual: TGP goes in LSS mode
-
Even so - Just as with the SC. I guess most of the community would prefer to postpone if needed instead of a buggy product. The only rigid thing should be quality... Would be cool to get the new toys tomorrow... But I'm willing to wait if needed.
Indeed
-
BigNewy confirmed on Facebook that the release is still planned for the 30th.
This screen shot is from yesterday
AN/AAQ-33 Advanced Targeting Pod Discussion
in DCS: F-16C Viper
Posted
The problem here wish the second part of your observation is that TV-XR modes are useless at night and the IR-XR modes are far less "hires" compared to the current implementation of the Litening pod, making the IR Pointer the only real benefit of the sniper over the litening at night time.
Hopefully there will be adjustments in the very near future.
In daytime there's no reason at all to use the Litening any more IMHO