Search the Community
Showing results for tags 'fixed internally'.
-
fixed internally Bomber gunners do not shoot enemies when close
EnvyC posted a topic in Bugs and Problems
Hi. While looking for potential fixes to an issue on 4YA's WW2 server I came across this strange phenomenon. When you get too close to enemies they will cease fire and in some cases forget you're there entirely. You can fly formation right in the center of a combat box and the bombers will refuse to fire at you. Not only that at many angles the bombers won't even use their full arsenal to shoot at you. Attached is a video showing the issue, with commentary, and I have attached two tracks and the scenario itself. There is an argument to be made that this is intentional as to prevent fratricide but the extent of this issue seems far far too extreme. If all the LW had to do was sit right in the middle of a formation they'd have absolutely ruined the concept of daylight bombing. Not only that, the degree to which the AI can't hit a stationary target is a bit suspect as well as per the A20 footage. test 1.trk test 2.trk Bomber gunner test.miz -
DCS 2.9: The manual gain control of the TGP doesnt't work anymore.
-
On multiplayer servers when trying to join as a AH64 CPG, the ACCEPT button will straight up not work (the DENY will), and some other times it will work and I will be slotted in but the BREIFING button will not allow me to get in the cockpit. This only happens on the Apache as far as I know. Has this ever happened to you and how did you fix it?
-
As the title, if any aircraft is connected to Catapult 1 no F-14 can taxi up to and get directions to connect to catapult 2. I know this is a legacy of the og undersized Stennis model, where two F-14s wouldn't fit side by side without wing overlap and the risk of collsion on launch but given that this legacy issue is now a non-factor can we please amend the logic to consign this now needless restriction to the waste bin? As the CO of a multiplayer Tomcat squadron, this is providing needless nuisance in getting our Air Wing off the deck in a timely manner. Many thanks. -
despite the changelog listing things as fixed, the issue as described in this post, the triangle indicating the position of OA1 is showing up below ground, despite its altitude being set correctly. track attached Offset-Aimpoint-location_bug.trk Offset-Aimpoint-location_bug2.trk
-
Hi guys, Are the offset aim points broken? They don't seem to work? Also...are there 2 ways of setting them? 1: from the TGP and 2: from the destination page? Thank you. They don't work well for me. I set them but they look else where. Used to work for me.
-
The SA-6 SR destroyed vehicle model has flipped normals.
-
Please can we fix the SA19 Tungusta missile. Alas on public servers it is being used often innappropriately to kill MBT's in combined arms. The point is there is no way this system should be killing tanks with the rocket warhead, AP its not. Also the main AA guns will shred tanks in seconds, HE shells are causing huge damage. Which also brings me onto another issue of HE rounds in tanks being able to kill other tanks. Both issues need to be resolved please. Track file attached , the Tungusta is a priority however. SA19 armour killing.trkSA19 armour killing with he guns.trk
-
Please see attached screenshot. The HSD cursor radial is wrong / twisted. Start F-16 marianas freeflight. Set bullseye to waypoint 1. (LIST-MISC-...) Make HSD sensor of interest. (DMS aft) Slew HSD cursor exactly on own aircraft. HSD cursor bullseye position should be same as ownship bullseye postion. Ownship bullseye seems to be correct. 054° for 11 nm HSD Cursor radial is way off. 178° for 11 nm It seems like the north direction for the hsd cursor bullseye calculation is wrong. This doesn't exclusively affect marianas but other maps as well. Sometimes to a less extreme extent.
-
Instant action - Mosquito - Caucasus - Train strafe End mission - hit fly again button. It doesn't put me inside the Mosquito. Can see the Mosquito and Yak in exterior view, but cannot Alt+J into it. The Briefing picture reverts to the Spitfire mission this was converted from. Repeatable - at least for me. -
The task of the test is to determine in which modes the FCR transmits information to the HSD page (A2A mode) Test conditions: One jet scanning and designating air targets and the other observes the situation on HSD page. Target consists of two jets. Result: - In RWS SAM mode: attack aircraft after designate does not see the targets on HSD page; observer aircraft sees only one target. - In TWS mode: attack aircraft sees only one of two (from FCR) target on HSD page which is designated by the FCR; observer aircraft sees only one target. Before today's patch: - In RWS SAM mode: attack aircraft after designate sees the targets on HSD page; observer aircraft sees targets. - In TWS mode: attack aircraft sees all targets (from FCR) on HSD page without designate ; observer aircraft sees all targets too. As you can see, this is a very significant change, if in the previous version everything was configured correctly, now there is a big error in the work of the FSR connection with the HSD and Link 16. Track
-
fixed internally Mossy no longer has thrust control option
ctguy1955 posted a topic in Bugs and Problems
I downloaded and installed the new 2.78.16140 update, and now it has tons of new items to choose, but no where can I find a setting to use my TM Warthog Throttle in the Axis area. *********************************************************************************************************************** I just found: input. generic throttle slider and it worked. I should most likely delete this whole thread, but others may now also now know that throttle is now not near Pitch Roll and Rudder. -
Hi everyone, This might be intended behaviour but is there suspposed to be a line on the HSD when the FCR is in STBY? Normally, the HSD displays a sector showing the coverage of the FCR (with the radius and angle of the sector being dependent on the range and azimuth settings on the FCR), but with the FCR in STBY, this changes to just a line, extending out to whatever distance the FCR was last set to. As the purpose of this indication is to display the coverage of the FCR, I'd expect it to not be present with the FCR in STBY, right now it appears to depict the FCR with antenna centered, but still scanning out to the set range (like a boresight mode). F-16CM_FCR_STBY_HSD_line.trk
-
fixed internally Nighttime Cockpit lit up like floods are on
uidotcom posted a topic in Bugs and Problems
I am running the latest Beta release with an Oculus Rift S with a 1080Ti. In VR, whether I perform an in-air or cold ramp start at night, the canopy reflections and the panels look as though they are rendered for daytime, making NVG use impossible. This is especially noticeable on the Nevada map where the canopy reflections without NVGs now hinder seeing lighting from Las Vegas during night-time flights. If I adjust the panel and flood lighting, I can see a faint change to introduce the green tint of the lighting on the panels, but all surfaces still appear to be bathed in daytime environmental lighting. Toggling global cockpit lighting causes no change. I have updated my graphics drivers as well with no change. While I have the majority of other modules, this only happens in the viper, and started with the last update. -
When will it be reigned in, like the hornets was? Is it a high priority? On the Back-burner?
-
I went through the triggers in mission 2 to see what stops the jeep. It's quite complicated actually. The jeep will stop at wpt3 until at least parts of groups of vehicles designated "FD1" and "FD #001" are within the crash site zone (designated "boom" ). The firefighting vehicle from group FD1 designated "Unit #40" will hold at its wpt2 until whole C-130 is within the crash zone. In any case, this firefighter called "Unit #40" from group "FD1" gets stuck there, at the base of the runway and this makes "Follow me" hold forever at its wpt3. I did a bit more clicking around the mission and there are a bunch of other vehicles bound to this same trigger (C-130 within crash zone) - none of them have this issue, only "Unit #40" firefighter gets stuck - might be a bug in DCS, not in the campaign/mission.
-
fixed internally SAM still do not loft 7/23/21 Update
AlexCaboose posted a topic in Bugs and Problems
Missiles launched in SAM still do not loft as they should after today's hotfix. F-16 SAM bug 2.trk -
fixed internally HARM pullback mode does not pull back
oldcrusty posted a topic in Bugs and Problems
Regardless of the active master mode, we should be able to fire the HARM as soon as the HARM's SP mode selects the critical threat (master arm on of course). Say, I'm flying toward an S300 battery and the SAM's tracking radar locked me up. My HARM was set to SP mode and it reacts giving me messages across my HUD and LDDI that it's ready to go. At the same time I'm locked on a launched S300 missile with my A/A radar and ready to fire an AMRAAM towards it, I should be able to do it and almost simultaneously fire off the HARM. Currently, we have to switch to A/G master mode to be able to launch HARMs set to SP. Pullback should work across all master modes. PLBK.trk -
As you can see in the video: https://youtu.be/xDn1ugHtZi0?t=104 The signal flares are positioned in the tail part of the helicopter That would be the equivalent to this part of the helicopter in DCS (the colors of the flares should be painted in the texture also) But when you shoot a signal flare you can see how it comes from a weird position and angle compared to the KA-50 or Mi-8
-
In the replay attached below, I have 3 large static objects set up with 2 hostile trucks in front of them. Additionally I have a separate group of 3 trucks just to the right of that. Petrovich has no problem locking and firing at those 3 trucks, but will not "see" the trucks next to large static objects and will not launch ATGMs. PetTargetBug.trk -
I'm currently playing the Raven One campaign for the 2nd time and I notice that my wingman keeps disconnecting from the tanker during a/a refuels. He does eventually complete the refuel but it does take longer than it would if that issue would not be present. When I played the campaign for the 1st time earlier this year, I did not notice this issue so I don't know if it's related to one of the recent DCS updates or if it has something to do with the campaign itself.
-
Hi all, I'm having an issue during the night F-16C missions and TGP that produces unusable image quality in WHOT and BHOT. The image is blurred and there is almost no help by using MFD brightness/contrast etc. to improve it. What could be the cause? I've uplaoded some screenshots from Syria quick mission Stop rockets rolling where you can barely see that there is something there (vehicle column).
-
The ground crew is blocking blaze from moving. Tried everything. Exiting and restarting. They are right in front of him.
-
fixed internally F-14 crashing when lowering gear in a hosted server
NotChar posted a topic in Game Crash
as the title says, relicable on missions when doing a case 1. gears dosnt seem to make the game crash when opened up at the very beginning, but it happens after a good minute or more when you try to lower gears again Currently, I've tried reinstalling DCS, removing all mods, removing my saved games folder, installing latest GPU drivers, removing dcs temp folder EDIT: added dcs.log dcs.log-20211024-025833.zip dcs.log-20211024-031628.zip dcs.log -
While the "Draw" mode is selected, the coordinate field is not updated with the mouse cursor's position - this makes it rather difficult to draw airspace boundaries from Lat-Long coordinates. Is there a way to fix it? Cheers
.thumb.png.69aee217f391afddc9737efe79c247b3.png)
