Search the Community
Showing results for tags 'bug?'.
-
TL;DR: when a mission spawns or clones a unit, memory is allocated. This memory is never deallocated, even on group/unit destroy, explode or removeJunk. Thus over time any mission that creates units will crash either from memory starvation or from hitting the RegMapStorage cap of 4094 groups. This investigation started after we noticed the excellent Pretense mission was dying after a few hours on our hosted server. By profiling the memory usage of the DCS_Server process using Process Lasso logging, we noticed that the VM (private bytes memory) continued to increase regardless of unit destruction, client join/leave or any other factor. The control was performed with a basic ME mission with a single client helo and no AI. VM usage was flat. The logical next step was then to write a script that spawned new units at a constant rate, and destroyed them on a cadence. If VM was deallocated, we would expect to see a sawtooth pattern. If it wasn't, we would expect to see a relatively straight incline up. The mission starts with 2 minutes of no spawning to establish a baseline with all scripts loaded. It is virtually flat. Once spawning starts (1 group of 5 vehicles every 3 seconds), VM rises steadily and does not reduce with destroy() being called on all ground objects every 60 seconds. When the spawn rate was increased to 1 group of 10 units every second, as expected the rate of VM accrual increased and VM was never deallocated. With a mission (not server) restart, no (effective) deallocation was performed as the VM restarts higher than when the mission was restarted. The next step was to also removeJunk around the spawn Zone to clean up as much as is permitted in the scripting environment. The same spawn parameters were used, with an additional step of calling removeJunk on a sphere 2x the size of the spawn zone every 5 minutes. In this test, VM continued the trend of accruing with no reduction due to destroy() or removeJunk(). It continued to accrue VM until the server crashed with the following error: 2024-04-11 03:15:28.743 WARNING EDOBJECTS (Main): RegMapStorage start cycle to find empty space in <viColumn> 2024-04-11 03:15:28.743 ERROR EDOBJECTS (Main): RegMapStorage has no more IDs (4094 max) in <viColumn> 2024-04-11 03:15:28.743 ERROR EDOBJECTS (Main): Failed assert `false` at Projects\edObjects\Source\Registry\RegMapStorage.cpp:124 This effectively caps the life of any mission that creates units on the fly based on the server RAM and the RegMapStorage cap of 4094. At 1 group per second being created, we'd expect to hit this cap at ~4094 seconds, or about 1.1 hours. This is basically exactly what we saw, despite all units in those groups being both destroyed and junk removed. A working theory is that this behaviour was introduced with the Apache FCR in order to allow destroyed vehicles to still be seen by the FCR. That said, others have said anecdotally that this predates the Apache. The effect is that dynamic missions require a regular server (not mission) restart to prevent this VM saturation, on a cadence that depends on the rate at which new units are spawned by the mission, and the total server RAM. Request that ED advise or investigate a solution that allows mission editors to purge the VM allocation of "dead but still there objects" in areas that are no longer relevant to the mission to prolong the life of the mission/server. While this may have other effects e.g. rendering them invisible to FCR, the alternative (a server crash or restart) is surely not better. Log data and charts: https://docs.google.com/spreadsheets/d/1p0tKoeipHJOaChhKnzNKjLD30maU3xKCvJH5o4quBY0/edit?usp=sharing (edit: if anyone wants to help me replace the MOOSE functions with stock to eliminate that potential source of error, please do!) edit2 another data point using trigger.action.explosion rather than destroy(). Same issue. RnR_Memtest_Syria.miz update: tested a different miz with no MOOSE (thanks cfrag), which creates 7 groups per second and destroys the group rather than the individual vehicles. Same VM accrual, and right on cue at ~590 sec (4094 / 7) it starts spamming RegMapStorage full.
- 7 replies
-
- 3
-
-
- performance
- bug?
- (and 1 more)
-
DCS open beta: 2.9.3.51704 Description: Hi, last night with my squadron we were using the ingame VOIP for a change, even if everyone has it well configured, we realized some can hear each other and some others don't, using the same frequency, no encryption, everyone was in the same airfield (Senaki's ramp), for example Pilot A can hear Pilot B Pilot A can hear Pilot C Pilot B can hear Pilot A Pilot B can't hear Pilot C and so on, we were like 10 online that night and i wasn't able to hear like 3 other pilots, another friend was able hear the ones i didn't but can't hear other pilots, furthermore, we all saw the green indicator we were receiving a transmition without audio in the way i said before, which bring a quite strange behaivor where friends were replying to some other pilots i couldn't hear We check volumes, if everyone was in radio mode, if everyone was in the same freq, or using encryption we all were correct on the settings. We check again in previous day and is not fixed who can i hear or not, maybe someone i heard loud and clear previously, now i can't hear at all Can someone help us out? EDIT: Followed up this post, none are using Sonar and the diagram is quite larger, not regarding only one pilot in my case we are even more
-
There is a red exclamation mark on the trim input for the KA-50 3. Hovering over it reveals nothing. I have cut the .lua for the warthog joystick and keyboard out and repaired. If anyone has any idea what i can do to fix this i would appreciate it.
-
The Brigthness of the navigation lights in external view, increase or decrease depending on the zoom level. Su25-Nav-Ligths-Bug-1.m4v
-
Hello! I finally found some time to try out Open Beta yesterday, when discovered that both the YJ-62, and YJ-83 missiles are not deploying into their proper post launch flight configurations. While the missiles themselves fly without issue, they end up zipping around with either none of their wings deployed, and or both of their launch boosters remaining attached to their tails. The booster sections in particular for both the YJ-62 & YJ-83, will remain attached to the missile all the way from launch to impact with the target. I have included several screenshots of my game below to describe what I am referring to. Hope this helps!
- 5 replies
-
- 1
-
-
- naval surface combatants
- bug?
- (and 3 more)
-
I have not been able to do any damage with the heavy HEAT/AP cluster bomb, dropped form a Su-25. I have just played some instant action strike, and I'm pretty sure I dropped the RBK-500-255 PTAB-10.5 within range of some BTR 90. They were within the blast cloud. They received zero damage. I have the damage dialog, and checked - not even 1% damage. Is this accurate performance, or is the damage bugged? If the cluster munitions called heavy HEAT/AP cannot do any damage to a BTR from the top, this seems wrong. Track attached. 255ptab105.trk
-
When you select the Vikhrs, the weapon name on the HUD is "1". Watching some older videos, it was "9A4172". This would seem correct... Is this a bug? I suspect so, as "1" is not a useful designation of the selected weapon.
-
EDIT/ADD: -Boost gauge tricky to read. Further down thread (see image) I found "true non bugged" idle boost ca -6.2. -I stupidly wrote zero (0) when meaning lowest idle boost. Edited to -6.2 in text (red). At no point during testing (all tests, all posts) did it actually show zero (0). Except engine off obviously. -Spitfire. Bugged (idle) high boost shifts between -3 or -4 depending HOTAS RPM level max/min. Might jump straight to post #6 (first with image). Previous posts I grasped less what's happening. Also, probably not intermittent (one thing I didn't grasp). I crashed Spitfire, did Quit -> Fly again. Suddenly Spitfire rolled on Spawn Rwy. Spitfire & P-51 both increase idle <1000 ~1500, Boost goes to -4 Spitfire instead of idle 0 -6.2. Seen once P-51, Spitfire all the time. Not tried others. When observed with Thrustmasters own software "Device Analyzer". All buttons work, analog hit correct endpoints (0-16383 for example). When plugging in the throttle the boost & rpm increases. What can this be? Throttle otherwise seems to work as it should, ie I can increase & decrease, just starting from boost -4 instead of zero -6.2 (Spitfire). Calibration? This has never happened before, bought 2018, so ie five years old, so I fear something more problematic is afoot.
-
Hi All Currently I have an stuttering problem with my reverb g2 and (only) DCS, I "debug™" my problem and what I found is every time a USB device is connected to the PC the game stutters. In my very own case, I believe, the VR-cable have a broken cable for the HMD audio, triggering disconnection and re-connection of the audio device -> leading to an unplayable game. How to reproduce: Even without VR you can use any related USB device, like a controller or audio-device start a game and then physically disconnect the device, this will trigger the freezing. [see example vídeos] Example video in VR here: Expected behaviour: DCS not freezing every time a USB device is (dis/re-)connected?? I attach the log with the device (un)plug info correlated to the stutters 2021-12-05 09:17:11.445 INFO APP: Device unplugged: \\?\USB#VID_03F0&PID_1841#8&7392e18&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 2021-12-05 09:17:24.554 INFO APP: Device plugged: \\?\USB#VID_03F0&PID_1841#8&7392e18&0&3#{a5dcbf10-6530-11d2-901f-00c04fb951ed} PLEASE ED-team, take a look on this issue it eventually will affect any random wired-vr user or wired-usb-(controller/audio) user dcs.log
-
Some countries don't have an option to add infantry units through the Mission Editor. There are a few important ones too. Could you perhaps add them? Even if they're basic models with an AK/M16 it'd be more than nothing. Argentina, Australia, Austria, Belgium, Canada, Chile, China, Croatia, Czech Republic, Denmark, Egypt, Ethiopia, France, Honduras, India, Iraq, Israel, Italy, Jordan, Kuwait, Libya, Malaysia, Mexico, Morocco, North Korea, Norway, Oman, Pakistan, Philippines, Poland, Portugal, Qatar, Saudi Arabia, Slovakia, South Africa, South Korea, Spain, Sudan, Sweden, Switzerland, Syria, Thailand, The Netherlands, Tunisia, Turkey, UAE, Venezuela, Vietnam, Yemen, Yugoslavia
-
Possible Multicrew Bug since recent update (July 2021)
AeroDan90 posted a topic in Bugs and Problems
So me and a friend have been practicing LANTIRN bombing with GBU's in the Tomcat (14B) for almost a week and after this most recent update i can no longer see the LANTIRN pod in the front pit, only the TCS will display and i also cannot see any ordinance (GBU 16's in this case) being selected by my RIO, all other functionality is there, he can set waypoints and can lock air targets, he can also use the full radar suite and the LANTIRN himself but it still only displays the TCS for me in the front, other things are also synced such as switch sounds, TID and the tape player are all working fine but without being able to see the LANTIRN and not having bombs being selected for the pilot this removes all A2G functionality for multicrew as dumb bombs are boring for RIO's. (or so I'm told, I always fly the thing) We had ran 20+ successful guided bombing missions in the Tomcat during the week leading up to the update and barring minor issues (desync) and my RIO forgetting to lase the first few bombs.. we have been issue free but after this update we have attempted several times to get this to work but so far we have had no luck. Things we have tried. - Consulting the manual as well as numerous tutorials in case we missed something obvious. - Multiple restarts/reconnects for any possible desync issues. - Starting both from the Ramp (hot and cold), from air starts and from the runway directly. - Multiple missions created by myself in case of file corruption, basic missions, no scripts, no MOOSE. - Having Jester set up everything first. - Having me jump in the back and set everything up (my RIO is new to DCS) and then having him jump in. - Loading in and then removing the LANTIRN with 'rearm' and then replacing it to force it to reset. - Loading in clean and then installing the LANTIRN fresh from 'rearm'. - Setting up the LANTIRN both on the ground and in the air. - Both of us re-installing the F14. At this point we are at a loss, the only thing that is different from when it worked is the new update and after reading through the patch notes nothing obvious seems to stand out dealing with the 14 or the LANTIRN that would cause such an issue, so now I'm here to see if anyone else is experiencing this issue as it's kind of annoying having my friend who is using a trial license for the F14 being unable to actually do anything useful, we both prefer A2G over A2A and right now other than the Hind or the Gazelle (both of which he does not own so more trials needed) we cant really do much together. Hopefully we are just missing something simple but im 98% certain this is a bug caused by the update otherwise the timing of it is ridiculously coincidental. -
As has been said in other topics, a Silence TCS-STT with WCS-Stby shooting is a bug, but when the WCS is on too?
-
UPDATE: Habe nun herausgefunden, wie es richtig geht..... Guten Abend! Ich habe mit der Mirage, mega Probleme! Für das INS habe ich mir dieses TuT zur HIlfe genommen: Mirage 2000C: CHANGES To INS Alignment & Approach Symbology - April 2021 | DCS WORLD 2.7 - YouTube Und ich befolge es strikt! Nun zum Problem: Ich gebe die Daten manuell ein (Die entsprechende Option des auto Ladens, ist im Menü aus) gelegentlich funktioniert es und mein HUD arbeitet entsprechend - nach dem "Booten" VAL und den umstellen auf NAV und [N]. Aber, regelmäßig, geht mein HUD nach Beendigung der Eingaben und den "Booten" des INS sowie den umstellen auf NAV + [N] wieder aus, bis auf den Kompass und ein + der wird im HUD gezeigt- obwohl das gesamte Flugzeug hochgefahren ist, auch in anderen "Stellungen" mit Batterie und Bodenstrom und den nur nötigsten. mit und ohne Bewaffnung, Radar an, Radar aus, Radar STBY... etc. Es nervt mich langsam gewaltig und ich frage mich, ob es wirklich an mir liegt? - oder liegt hier ein gewaltiger Bug vor? Nun ja, Verwende ich dann im rechten Pannel den einzelnen 3 Stufenschalter, für den Virtuelen Horizont und stelle ihn auf AN - nicht auf den NOTModus, so kommt im HUD "Horizon Secures" und ich kann nichts mehr machen. (also den Schalter brauche ich nicht, merke ich ) Ich weiß noch im Winter, da konnte man per Windos+POS1 Autostart machen und das INS lief prima. Jetzt mit Autostart geht das INS nicht automatisch - ja doch schon, aber halt das oben genannte passiert. Ich habe kein Pipper, keine Schnecke, kein Fadenkreuz Keine Horzontalanzeige keine Grad +/- NIX - außer der Kompass und ein + Zeichen..... Achso, Gunsight auch nicht Hoffe man kann mir helfen Grüße
-
Hello kind pilots, here is my probelm... So I will write down all of my components right here: CPU ---> Intel Core I7 8700K 3.70 GHz (https://www.amazon.com/Intel-i7-8700K-Desktop-Processor-Unlocked/dp/B07598VZR8/ref=sr_1_4?dchild=1&hvadid=77790517240465&hvbmt=bb&hvdev=c&hvqmt=b&keywords=core+i7+9700k&qid=1623684884&sr=8-4) GPU ---> GeForce GTX 1080 GAMING X 8G (https://www.msi.com/Graphics-Card/support/GeForce-GTX-1080-GAMING-X-8G.html) RAM---> HyperX Fury 16GB (2 x 8GB) DDR4 2133MHz DRAM (https://www.newegg.com/hyperx-16gb-288-pin-ddr4-sdram/p/N82E16820104674?Description=16gb ram hyperx&cm_re=16gb_ram hyperx-_-20-104-674-_-Product) Motherboard ---> MSI Z370 A PRO (https://www.msi.com/Motherboard/Z370-A-PRO) Tell me if you want the rest of it but I think it's what you have to know. So here is my problem, I began to play dcs some time ago and didn't really have problems with anything, it was all running great at high settings but as the updates went to come I incountered this issue... I am lagging a lot and what I mean by lagging is a frozen screen for multiple secconds, sometimes long enough to make me crash my plane while I can't do anything... It is very annoying and happens mainly when I'm close to other players. So I don't know if it's a computer hardware problem. I lowered my settings, but it still lags, and the game runs just fine in solo with even higher settings. Is it maybe my RAM ? I have 16go and I saw that the recommended config was with 16go ram (they are maybe talking about playing in solo, right ?). When I checked the benchmarks while playing I didn't get much higher than 14go so I don't know... If the RAM wasn't the problem then I thought: maybe my connection is. I did mulltiple speedtests and always got similar results which are 45 Mbps in download and 20Mbps in upload. Are these numbers too low(maybe the upload in particular). I don't know what I can do more, maybe I should reinstall DCS ? I also checked if it was running in all of the logical processors but it already was, so no problem there... I'll try to lower my settings even more than what it is now but I find it weird that with this config it has that much of a problem running it in multiplayer but again maybe it's not my config, (it runs perfectly in solo with heavy missions)... Thank you for hellping me out...
-
So me and 5 others flew an Elint flight but we didn't pick up the ELINT data even if we flew over the radars at 4000-6000m and they pinged us with search and tracking radars. Is the elint in the Viggen outdated? or what is up with it?
-
Hi, I recent update the TGT-TO-PUP as well as TGT-TO-VRP were added. I appears the ELEV parameter is actually Height, not elevation. In the image below, my height is 340, altitude 2120. That means the ground elevation is ~1780, which corresponds to the map. If I want the TGT-TO-PUP to be level with my FPM at 340 AGL (Height) I should set its ELEVation to 2120? When I do that the TGT-TO-PUP jumps very high. When I set it to 0f it is level with my FPM meaning it is Height and not elevation. Is this a bug? ELEV value for OA1/OA2 appear to be elevation, as it should and not Height.
-
I've supposedly landed too hard on one of my landing and I had to repair the the bird. Once I repaired it, I got everything started back up and I tried to connect to the datalink master mode but to no avail. I've tried to connect to the net using CLINK on the right mfd but it wont connect. I've resetted the radio control handover at the bottom left side but I'm still not able to connect. Is there any way to connect to datalink after repairing the plane or do I have to respawn everytime?
-
I just noticed a bug while watching a Tacview of mine. Atleast once a Bluefor Parachuter suddenly spawned in, without any bluefor ejecting. Also the Viggen's Tail seems to be indestructible (2nd last kill)? Here's the File: Tacview-20221101-204421-DCS-AJS-37 Paratroop intercept.zip.acmi -
When turning the altimeter knob to set QFE, it can't go below 930. So when my calculated QFE requires lets say a subtraction beyond 930, can't do that.
-
In my test myssion, Yankee TACAN on Mirage F1 doesn't work, but on F-18C and others its work. Did the test with channel 110Y. (!!! Important: In the C aucasus, everything works. I ran into a problem specifically in Syria. ) Attached test mission and track, it has two beacons TACAN - 55X and 55Y. When I set it to 55Y, it is ignored and the plane catches 55X Test.miz Y TACAN.trk
-
hi there, I've been having multiplayer issue where the game keeps crashing at random points, is there any way to fix this issue as it makes it unplayable. i have attached the crash log and dump file if it helps. Thanks, Mike dcs.20221225-190118.crash dcs.20221225-190118.dmp
-
Is the fuel flow not supposed to account for afterburner? (F14-B, not tested in A)
-
I was trying to learn how to use harpoon fix point, because it's not worked properly for me whenever I've tried to use it in servers. What I've found is that while the hsi will display correctly the bearing that the missile should be following, the missiles themselves will fly off to the bearing that you set in the ufc. The steps that I used in the included track file are as follows: Set required search and destruct ranges for all missiles. Set bearing for the first missile and hit fxp. Step through the other missiles hitting fxp for each. (the bearing on the hsi for each missile is around the first) Fire x4. What I expected was that each missile would aim for the fixed point. Instead, only the first missile turns to the bearing that I set for it in the ufc, everything else goes for 0 degrees which is the default. I'm also happy if anyone can point out any mistakes in the step above for setting up harpoons for fixed point. HarpoonFxPnt.trk
-
So my issue is that if I take a brand new jf17 cold and turn on the batterie or plug in the ground power, after around 10 minutes most systems inside will go haywire (mfcds, the warning pannels, the starter wont work anymore) and it leaves the jet unable to be used and need a repair I have done a bunch of test including flying it before shutting down and keeping just the batterie or the GU on, either way at some point both will result in the same problems after ending the flight/mission there is no reports of any damages to any system so I don't think it's an empty batterie (since GU does not help) so the only I can stay on the parking space while waiting for people or to wait for an interception is to either keep its engine on and have to refuel and all just before take off or turn the batterie off and lose my alignment and other settings I tried with random failures off and no changes if anyone knows better or maybe its an unknown bug for the devs idk honestly. Edit: so yeah it was overheating electronics from so tests ive done it seems that after passing some cool air with the ecs does bring everything back to normal as its not permanent damages
-
not the entire screen
