Search the Community
Showing results for tags 'bug'.
-
Doing the Su-25 T Mercury pod training mission, the screen looks bugged after turning the pod on. Screenshots of the view with just the Shkval, and with Mercury on. The Mercury has the top right flooded with something very bright, while the rest is dark. This stays constant as you maneuver the aircraft, or slew the pod. This is both in VR and normal.
-
I've assigned the TDC slew to a mini joystick on my HOTAS. This bugs the target designator: diagonal inputs with one component too strong will not move the TDC, it just locks up. To reproduce: In A2G mode, move the mini joystick in full circles, the TDC will behave erratically. This is in Su-25 T only : in Ka-50, which also has the Shkval, this works perfectly fine. -
I just recently bought the Viggen and was going through the startup tutorial until I got the the qfe part. The tutorial asked to set the qfe to 1031 and press the space bar when I had done that. I did what the tutorial asked but when I pressed the space bar it wouldn't go to the next part. Is this a known bug or did I just do something wrong?
-
AI UH-60 explodes every time on Andersen AFB taxiway K after landing on runway 6L. Andersen AFB Bug.trk
-
In this mission, you're supposed to intercept some bombers over the sea. The radio call places them 15 nm off the shore when you're near the shore, so they should be almost within visual range. However, they are nowhere to be found. No bombers are present in mission debrief, and the mission passes with score 100 without doing anything. fail.trk
-
The model rendered in the side and top mirrors of the Su-25 is missing huge patches of textures, and you can see into the plane. This is both in the side and top mirrors. Additionally, the position of the side mirrors is very bad - you only see the engine basically, and if you lean just a little, you will see the missing textures. On the Su-25 T, the mirrors are aligned much better and are useful, but if you lean enough, you also see missing textures, although it's not nearly as bad as the Su-25.
-
Since 2.9 the custom liveries in the saved game folder seems not to work anymore. In my Saved Game folder I have multiple liveries that were visible from the loadout menu before 2.9. Now these liveries are still there but not available from the loadout menu. Did something changed in 2.9 ? I checked the folder names and folder structure and I everything looks fine. Anyone else has the same problem ? ...any solution ?
-
Spawns at El Arish, parking stall 1-10, will have the AI taxi up the primary runway, across the linkage between the two runways, up runway 34R, and then alllll the way back down the taxiway adjacent to 16L, to runway 16R again where it started, and THEN takes off on 16R. The entire time AI wingman/other AI will also not taxi while one ai is taxiing, resulting in horrible traffic jams VERY quickly. This whole process takes some ~25 minutes for one aircraft to finish a taxi process, to get to the runway end they spawned at.
-
In VR, when peeking over the nose, there is an area, highlighted in red, where textures are missing, and you can see into the nose of the aircraft.
-
flares-bug.mp4 Targeting pod thermal view shows flares as big heat rings -
My game Stuttering every 20ish seconds, and when launching missiles and explodes, in 2.8 it never happened like this. I have i7-10700 ,32GB RAM,NVIDIA 3070 8GVRAM, game on SSD. Loving DCS hope this can be heal soon. @Flappie Thank you and Hi Flappie, saw you been tracking some similar issues, hope this won't bother you. Performance monitor like： Screenshot\log\track attached. HEAVY STUTTER.trk dcs.log dcs_frame.log The performance had a big issue at the end of the Trk. If the AI play their things correctly. I got shot down by the end and all the explosions and cracking~ I can see dozens of peaks on the FPS monitor window, even when I'm Over G blacked out.
-
As per the title. In VR, sometimes, going to the map and back causes the overall brightness to increase significantly for a few seconds - very uncomfortable. I only experience this in Ka50, on both Pico 4 and Pimax Crystal headsets.
-
using the APACHE NEVADA RWAY TAKEOFF mission dcs.log shadows are in pieces and strange bars is that the SSS? or else? dcs.log
-
Open Beta 2.9. Landing gear appears to jitter, see attached video. When GPU cart is attached, it jitters in sync with the wheels. I have not observed this on any other official module, whether from ED or 3rd Party. The same bug can be observed on the unofficial OV-10 Bronco by Split Air. 2023-10-25 01-09-00.mp4
-
With a mission running from my server or our wings our tacan is inop land sea or air. Same missions running single player works fine. When launching from ship MP we may have tacan for about 20 miles after that its gone. Here is my south atlantic template for mission building no scripts triggers or anything. It fails in MP but is fine in SP. South Atlantic TEMPLATE.miz
-
Love the campaign so far, but this mission hung up on me. After the explosions and I'm directed to Al Minhad and to contact them on 30.4? FM for CAS, it says to press spacebar to continue, but refuses to accept my button presses. About 30 seconds later, the story continued and Steep reports to Whiplash that that frequency is dead, and they give him a new frequency to try, 32.7 FM I think it was, and the subtitles instruct you to press spacebar to continue once the radio is set. I tried with the 3rd radio and the new Arc-210 radio but the game refuses to accept my spacebar input and nothing more ever happens. I tried to triple check to make sure I had things set correctly in case the game can tell if I don't. Manual mode, FM, the correct freq, etc. Eventually the text box times out and disappears, but still no more events or dialogue happen after that. -
Runways reported by lua using the airbase class function getRunways() returns a table of data for runways - most of this information is correct, except for length. Length is off for almost every single runway, except al mansurah 35/17 (which is only off by 20m, good enough for me, its functionally correct, and looks it on the map at a glance if used for marking the strip) Lengths are not off by a lot, it varies. Some are only off by about 100m, others off by closer to 400m. not a particularly severe bug, the lengths are all 'close enough' but for those of us that use that data to mark runways on the map, for various lua functions, etc.. its imperfect. Looks like a simple oversight of a placeholder slipping in, as many are sharing the same numbers for length. Possibly just unfinished? low priority bug for sure.
-
Hi everyone I was going to test something until I noticed the Hornet has a ghost weapon weight of 130 lbs with following conditions : - no weapon - all pylons removed - 0% gun ammo -0 chaff and 0 flares I noticed it in the mission editor so no track files are needed for verification. - It is good to mention that the M61 weight is not considered as "weapon weight" because internally it is part of an aircraft hence its weight is around 202 lbs not even close to 130 lbs , - [Correct as it is ] I checked the Viper and it had 0 Weapon weight with a clean zero ammo configuration. conclusions : this could be either an error in the mission editor, an error or bug to deduct pylon weights or really an extra dead weight on the aircraft. Sincerely - Cipher
-
Half the dialogue in Mission 9 cant be heard because overlord base comms isnt muted, so when the scripted dialogue plays you cant hear it, as overlords giving constant updates !! -
Hello everyone, The DCS P-47 is very well done. However, improvements to the module will always attract more consumers. So, there are some inaccuracies apparent in the DCS P-47D cockpit. My Background: I have been involved at the CAF for 7 years. Specifically, CAF SoCal Wing. Have spoken and worked with vets from WWII, Korea, and Vietnam and friend of during this period. We also have a private library with hundreds of technical manuals and documents. With this, I provide only precise information with my findings. For the DCS P-47, there are 4 features missing that I would like to bring forth. 1. The P-47D-30 with gyro sight features a dimmer knob and sight selector on the same unit. The same unit left of the DCS P-51D K-14 gyro sight as well. The DCS P-47D is missing this control unit on the right thigh panel. Picture: (4th photo) 2. Tail Warning Radar – same as DCS P-51D (Field mod). The light and bell are located left of the K-14 sight in the P-47D-40 (Only model with evidence). The control unit for the field mod is located behind the IFF destructor box. Picture on unit in cockpit: (2nd photo) Picture of unit for proof on P-47N manual: (3rd photo) 3. Rear View Mirror – in the form of: plexiglass on canopy, truck mirror reused on front canopy, dedicated mirror inside cockpit. Field mod. This was more favorable than the tail radar. Not every P-47 had this, but experienced pilots knew the mirror was important. -Picture of Variations are included: (1st, 6th, 7th) 4. Pilot Headrest – this should be factory. Pictures provided. Again, the module is very well done and it’s obvious the developers have created a warbird module never done as accurately and precisely as this depicted. However, improvement is always a beneficial virtue to seek and so I believe these additions will only make DCS stronger in WWII. Thank you all, Rob
-
I can go all the way from F1 to F5 in realtime game, but couldn’t switch to any POV in replay, I got lock in the pov of my actual game
-
the game would crash after about 10min into mission 2 of the campaign. any ideas? dcs.20210212-234437.crash dcs.20210212-234437.dmp dcs.20210212-234437.log dcs.log
-
Finland never had AIM-9L Correct one would be AIM-9M or X Small but easy fix :)
-
Hi everyone, In the absolutely stellar update for the Viggen, a fairly major issue has unfortunately been introduced. Regardless of whether you're starting cold, hot or airborne, waypoints cannot be selected using B1-B9 keys, only LS, L1, L2 and Bx points (including undefined Bx points - not sure if that's right) can be selected (using mission editor defined waypoints). In the air however, B1 gets automatically selected, however, pressing B1-B9 results in LS being selected, at which point only the aforementioned points can be selected. I have a hunch this might be related to this issue, that has also appeared this update. AJS_37_Cant_select_waypoints_cold.trk AJS_37_Cant_select_waypoints_airborne.trk AJS_37_Cant_select_waypoints_hot.trk
- 3 replies
-
- 1
-
-
- bug
- navigation
- (and 1 more)
-
Hello, good morning, afternoon or evening, today I come to talk about a problem that has been around forever, which is the issue of height editing in waypoints, that when you try to set as for example 20000 in the mfd question marks appear or directly put 0, and in the ufc comes a random number from 6093 to below, I can not currently upload a trk file but I have a video unfortunately in Spanish from a well-known channel in our community that shows the problem, in minute 7:08 to 7:14
