Search the Community
Showing results for tags 'cannot reproduce'.
-
I didn't found any change in Open Beta "change log" so I'm opening this as a BUG because I suspect this is a regression. Problem statement: All F-16 ECM pods are not making any difference (both in Deception and Noise Jamming modes) to legacy/old SAM radars and it's tracking, after one of recent DCS updates. I remember it worked pretty well. For SA-2 it was quite easy to break a lock, means was effective for Fan Song up to 12nm. In recent version of OpenBeta I not only cannot break a lock even at 20nm but also seems there is no difference in locking range under jamming conditions. To backup the story it worked some time ago, measurements for "DCS skynet IADS mod" of effectiveness of ECMs which simply does apply anymore. @NineLine@Raptor9 You seem to admit ECM is effective for AG. So was it changed recently without notification in change log or this is a regression ?
-
keep getting this issue that pressing wpdsg or tdc depress from the tpod does nothing. can't designate any ground targets. even tried hud designate but won't work. Operation_Roach_II-20240118-215537.trk
-
When going into A-G and cycling to CCRP with the NWS/AR switch, the FCR will stay in the last selected mode (in my track CRM/RWS) instead of going into GM (which I believe is the standard preplanned FCR A-G mode), CRM is not available in the A-G mastermode, so this shouldn't be possible. This only happens with the NWS/AR switch, if you select CCRP via the OSBs on the MFDs, it will work correctly (and then NWS/AR switch also works correctly). Steps to reproduce: 1. Get into A-G mode with bombs that can use CCIP/CCRP/DTOS (anything except IAMs If I recall correctly) 2. Cycle with the NWS/AR switch through A-G submodes, the FCR will stay in the last selected mode instead of going to GM when in CCRP Track attached, I can also provide evidence in PMs if required. HOTAS A-G submode selection FCR bug.trk
-
Hi all, I'm experiencing screen flickering during twilight or dimm conditions in general (dusk or dawn). I've tried turning off G-Sync, different screen settings, different detail settings and nothing has any effect, also it doesn't matter what module I have and what map it's flying on. MT or ST also has no effect. I tried to record video, but unfortunately you can't see it in the video. Log attached below. Thank you very much! dcs.log
-
Hello, Experienced CV operator here, returning to the F/A-18 in 2.9 after a hiatus. Is anyone else noticing distinct ground effect over the ramp of SC causing flying out of slot and bolter? TIA
-
Prior to the patch on 19.12.2023, the key assignment "Default Zoom" would correctly change the FOV setting to match the "{--default view" entry for any given aircraft in SnapViews.lua. After yesterday's patch, the default zoom is now 124.4 which basically turns the camera into a fish-eye lens and it's completely unplayable for me. I tested different values for the Apache in SnapViews.lua, but it won't use whatever value is set for the "default view" entry. As a test I set "90" for the default FOV in the Apache: But when I hit default zoom, it goes to 124.4. I've tried deleting SnapViews.lua from the Saved Games\DCS.openbeta\Config\View directory and let DCS rebuild it after saving a custom SnapView with no change. I've tried running a repair with no change. The issue of default zoom not resetting the FOV is a bug that has been around for several open beta versions. Before this latest patch, the workaround was to briefly select a snapview (windows key + numpad number) and then default zoom would work. Now, I'm just stuck with an FOV of 124.4 unless I manually change it with the "Zoom slow" keybinds, but you have to leave the console window open to get back to your desired FOV if you decide to zoom in or out at any point. Can this please be hot fixed?
-
Hey all, I just installed .49940 and jumped into a hot start mission. The first thing I noticed was a light green tint to the IHADS, the second thing I noticed was that I became quickly airborne in a right spiraling rotation and immediately crashed. Both were not the case before. The first thing I can deal with. The second thing I am looking for a work around. It would probably be by editing a LUA file? So is there a way to force the collective value to be at zero when the collective is physically at zero (full down) when the mission starts? This is instead of having to quickly raise then lower the collective so that it is so. I have "Synchronize Cockpit Controls with HOTAS Controls at Mission Start" checked, as it has been since I started playing. But I know that doesn't always work (Exp: Throttle on the A-10C) I have no idea why ED decides to change this stuff like this, but they do. It can be frustrating. Thanks in advance, Caldera Ah Oops... The first thing, as it turns out was a switch out of position on my HOTAS. Caldera
-
need track replay F-18 Comms Menu works "off and on"
CyberJohnny posted a topic in Bugs and Problems
Hello, post the update I have been having problems with the "Comms Menu" ( Only with the F-18 module). Both in the Air, deck or ground it does not work (at least not consistently). I re-binded the keyboard, and HOTAS buttons -- no change. Frequencies were correct, even tried the "easy comms" option. Anyone else have this issue? Any Solutions? Thank you -
-
Hi Just recently I lost access to the communications menu in all my aircraft. I will hit the bound keys on my joy stick and keyboard and the menu will not materialize. I believe I just had an update. I have tried all avenues and nothing works. Does anyone have any ideas how I can solve this problem. Thank you.
-
Could somebody confirm, if the CCRP lofting is working or not? I cannot get it working, tried with mk82's and cbu87's. Something seems off with the release!? It seems to jump forward or not releasing, when it needs to be released. Please confirm! Maybe I'm doing something wrong now, something changed during the procedure. CCIP is working. FYI: cleared all meta, fxo and disabled mod's, also repaired and created a new dcs Openbeta folder. Did not change anything. f16 lofting not working.trk
-
Hello, I've noticed that it's very easy to jam the guns of the Dora under G. This may be realistic ... or it may not (personally I suspect it's over-modelled .. the 190 was well known for its ability to pull lead at high speed). However, what is definitely not realistic is that the Dora appears to be the *only* plane in which it is possible to jam the guns. None of the others suffer from this problem at all. This is surely countable as a bug: either all planes should have the effects of G jamming the guns ... or none of them should. Tomsk
-
cannot reproduce Should HARMs be able to target SA-6 launchers?
norman99 posted a topic in Weapon Bugs
As per the title, should HARMs be able to target SA-6 launchers? I thought the Straight Flush was the only radiating unit in an SA-6 battery? -
Anyone else notice that the trees in Normandy because almost bear as they get close? Only happens in this map and only since 2.9.
-
Hi all, anybody else experience this? Never had it prior to 2.9. Was CPG for approx. 6-10 minutes, and upon returning to the back seat, only my collective was having any effect on the aircraft. A number of times prior to this (same mission on same server) I switched to CPG for 1-2 minutes, and back again without issue. Will attempt to reproduce in a single player mission to enable a small enough track replay to post here. Have a good flight. '52
-
In training missions before, gates used to all stay the same size, now when I fly through one, the next one suddenly becomes much bigger, and slowly shrinks over size. When you restart by pressing Ctrl Shift Tab, a gate randomly becomes massive, and slowly shrinks as you approach as well, although it is not the next gate. DCSMassiveGateCompressed.mp4
-
Checked all of the Soviet- and Russian-made SAMs and MANPADS, from SA-5 to SA-18. There is a kind of booster noise when missile starts (looking from F7 mode), but there is no sound of rocket motors in F6 Missile view mode. And SA-2 does not have even launch sound, missiles take off in vacuum silence. Firstly, I thought its because of supersonic missile speed, but from the rear there is no sound too
- 9 replies
-
- sound bugs
- missiles
-
(and 1 more)
Tagged with:
-
Just wanted you to know I experienced some AI issues in this mission from Weed. I had to fpy it 6 or 7 times because I was anticipating at least some mutual support based on the dialogue but was never supported by Weed. He would not engage the MiG-23s and would only engage the Brushbacks with a single AIM-9. The mission works fine for progression (i flew it a different way successfully after realizing Weed would not help in either engagement), but the player receives no help or support from Weed which makes it much more difficult. It's my second time through this campaign and still love the challenge of it! Thanks for the great work!
-
For several months now, random engine failures have been occurring repeatedly on the A-10C II. Without any external cause, one engine is on fire. This can be the left or right engine. If you are unlucky, even both within one mission. It does not always happen to the same A-10 within the mission. Birds are turned off in the missions, as is the random failure of system components (I checked this in the mission file). There is no strafing either. So I don't see any reason why one engine keeps going up in flames. Are there any other reasons for the engine failure listed above?
-
hi, @NineLine, Merry Christmas, and a coming New Year! I keep noticing some weird 'resilience' problem with the ai ju-88's. With P-47 it takes 5-10 rounds and they 'explode' or whatever the fireball effect is called, obviously catch fire and sink. Was just flying on some Channel MP server and I was able to destroy the whole wing of 25 or 30 of Ju-88's. Pop, pop, pop... lol.. It seems to happen when I hit them dead on the center of the fuselage from straight 6, the resulting fire can start on either side between the fuselage and a motor. If I hit them directly into the motor they take damage and eventually catch fire, so are the sections from the motors to the tips, they catch fire like normal (I guess). I'll attach a track tomorrow (the mission I flew ended up in a game crash (d'oh)).. although i'm sure you can load up some quick test mission with a p47 and a ju88 and give it a test yourself... The behavior seemed too intentional, can't just be me...
-
i have issue with kord door gunner position i believe it is relative to multi threading preview (i cant seem to run single thread anymore, since both DCS.exe in both bin and bin-mt show DCS as multi thread preview when the kord is rearmed, you can see the ammo boxes toward the back of the hind cabin. when all the ammo is depleted, the ammo box objects still remains. before patch 2.9 you can see all the ammo boxes disappear, one box at a time when the kord fire all available on board ammo.
-
Hi, Today i took the Anton for a spin on a singleplayer training mission and during shooting on AI P51 in a turn the left MG 151/20 stopped shooting and according to debrief it was due to "gun overload jam". Heres the debrief: Random failures are off. What exactly are the conditions for this to happen? They seem really strange and ive never read anywhere about MG151s being prone to jams. Also to my knowledge allied planes do not suffer jams or stoppages (I own the P-51). Whats the difference between these weapons that the 151 jams and the Hispano on Spitfire for example does not? (Which by the way is ironic because early and mid generation Hispanos were notorius for jamming because all sort of reasons) Second part of my bug report and question is that ground crew does not unjam the jammed gun when they reload it. How exactly ground crew does this? Are they magicians? Attaching TRK and DEBRIEF file: FW-190A8_training.log FW-190A8_training.trk
-
I was in the Hoggit GAW server and was attempting to make use of the Data link page. When you get to the page that shows which flight numbers you want on the data link and dobber down. My game immediately crashes\freezes up and doesn't respond. I went back in and tried again and same thing happened thinking it was a fluke. I Don't get any crash report tools that pop up. (Not 100% sure how to find said crash report).