Search the Community
Showing results for tags 'reported earlier'.
-
The axis labeled in control setup don't correspond to the axis in cockpit - RSI-6K Volume Knob in setup moves RSI-6K Antenna control handle lock knob in cockpit - RSI-6K Wave control handle in setup moves RSI-6K Volume knob in cockpit Why the Antenna tuning or the remote receiver knob are not available as axis but a handle lock knob it is?
-
Check out one of the ED ship models to see how its done now. Older mods no longer have funnel smoke - that's a LOT of mods that are affected and I dont see an easy solution.
-
(Re-written after reviewing replay) TACAN can stop updating. DME and bearing to the station stops updating. Station position on the HSI becomes inaccurate (it still moves around when you turn but it's no longer correct). It seems this can happen when not interacting with the HSI. If you watch the video below you will see me flying towards the CV and the HUD counting down the DME until it hits 12.3 and stays there. I was just looking around when this happened. It happened again in some minutes later into the flight when I decreased the HSI range from 20 to 5 when at 9 DME, putting the CV outside of the HSI's range. You can see both of these in this video: https://www.youtube.com/watch?v=MA66pKHLJvw Drop box link to the trackfile: https://www.dropbox.com/scl/fi/pxiln9k6ejotp3ftqizs2/TNN_release-2.0.66-20231028-203150.trk?rlkey=mww4m7rhbit8asj4br3dbv67l&dl=0 You'll have to FF a lot to get past all the boom booms =( Once you realize there is a problem you can reset the HSI by changing stations and then returning, or by toggling the TACAN Off/On. Easy but it's a bit more painful because you may have contacted the carrier, gotten the BRC, entered it into the CRS line then losing all that when you toggle the TACAN settings. Not to mention the time wasted figuring out there was a problem in the first place and flying an embarrassing long time in the wrong direction (like I did lol). Here is a list of actions for reference that are also chapters in the video 00:11 TACAN on to settings set before takeoff. Seems to be working 00:50 CRS line set 01:02 HSI dropped from 40 to 20 while Carrier 23.1 DME (still works) 02:30 Notice hud DME goes to 12.3 GWA and stops. 02:47 Notice HSI station also frozen at 12.3 DME. 03:25 HSI dropped from 20 to 5 while still frozen. No change to DME or station position even though it's no longer in front of me. 04:47 More TACAN settings changes to no effect. 05:36 I'm starting to realize there is a problem 06:00 Double checking TACAN settings 07:13 I finally change TACAN station to a random number and back again fixing it. 07:34 I change HSI from 20 to 5 while at 9 DME which immediately breaks it 09:25 I toggle the TCN button on the HSI. Does not fix it. 09:29 I turn TACAN off and ON. This fixes it. -
Hi everyone, Quick disclaimer: I've recently had a tendency to report already reported things, so apologies if this was already reported. As the title says the texture on the FARP does not seem to follow the season. This issue was not present in 2.8. I'm using the latest 2.9 patch (2.9.0.47168). FARP_Texture_Season.miz
- 1 reply
-
- 2
-
-
the waypoints skip every other point in 2.9
-
The static L118 105mm light artillery gun has been added to the list of possible cargo (can be cargo) but when you want to sling it with the Mi-8 (both in hovering and on the ground) the gun seems to go into the ground and the Mi-8 is damaged or destroyed. -
i have two issues currently with NS430 in the recent update a) NS430 popup in VR does NOT appear (via LShifit+LAlt+B) when running dcs from bin-mt for Multithread Preview. Single thread version works OK b) with the NS430 popup working in single thread, the NS430 is still floating in front of my face, please make the NS430 popup remain in a fixed position, just like the FPS counter, the SRS overlay, the kneeboard..etc, etc.. PLEASE!! the floating NS430 is annoying to use...
-
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.
-
I wasn't sure where this should even be reported, and just noticed this today. I don't think it was doing this the past few days, and I've changed settings so many times this week I couldn't say what triggered it to start. It looks like bad video recording but this is exactly what it looked like, with the sweep line being broken and ghost trails following along behind it. 2023-10-24_14-49-39.mp4
-
The zone size for the destruction zone (and remove scenery trigger) is inconsistent and often ends up bigger than what is set in the mission editor. It's a real pain in the ass to work with, especially in this case where the units are supposed to cross the only bridge in a wide area and then remain in position because that bridge is destroyed. Example: How big the trigger zone is set up (note the bridge with the many waypoints outside the zone) And now behold: The bridge and the city just under the zone are destroyed.
-
reported earlier DED and datalink bug when STN first digit over 0
itn posted a topic in Bugs and Problems
Hi, Running DCS 2.9.0.46801 Open Beta DLNK DED page and datalink feature are bugged when using STNs with first digit over 0 (i.e. 1xxxx-7xxxx). Working range is 00000-07777, seems to work correctly as long as first digit is 0. Did not test every combination... Seems related to the previously reported Hornet CTD when ownship STN first digit is over 0. Symptoms are: STN representation is incorrect on the DED page. First two numbers of the five-digit octal STN are incorrectly represented: For example 70xxx becomes 1Sxxx. STNs change when cursor is on them, and back again when cursor is moved off (the aforementioned 70xxx becomes 45xxx when cursor is on it). And most critically: Adding members higher than 07777 does not work on DED page. They can be entered to the list, but do not become members on HSD. If you edit an incorrectly shown member STN on DED page to "correct" it, you lose the member. Datalink members added in ME work even if the number representation in DED is incorrect, and as long as you don't try to correct them as stated previously. So you can add members like 10202 and 50123 in ME and it will work. See the track attached, me flying STN 70201 with 10202 on my right and 00203 on my left. The track should have everything necessary for reproduction: 00203 works, 10202 doesn't, and the demonstration on DED page. F-16C STN ID bug.trk -
reported earlier new F18 pilot model head tracker issues
ChaosRifle posted a topic in Bugs and Problems
not a bug, just a problem.. The new model has a helmet that when looking left/right you can see your own face. the head really should not be rendered when you are in first person, like the old model was. or at least have an option in special settings to turn the head off - much preferred the old model because it didnt get in my way with the head when it was enabled, because it lacked a head. -
If the HARM is fired in PB (or EOM in the F-16), the expected behaviour is that the HARM will loft and turn towards the selected steerpoint or target point, then dive towards the target area and start looking for a radar of the selected type to home in on. What appears to be happening, is that the HARM seeker activates immediately upon launch. If it doesn't see a radar, or if the radar is active the entire time the HARM is in flight, it will fly the correct flight path. However, if the radar turns off at any point during the flight, the missile will go dumb and forget its target position, and glide straight past it. In the first two tracks, which is the same scenario in the F-16 and F-18, to show there is no issue with a particular aircraft, there is one SA-6 radar at steerpoint 2. First one HARM is fired against a non-existent SA-2, and one against the SA-6. When the first HARM is about to strike the SA-6, a third is fired, also against the SA-6. Observe that the first two missiles loft and dive towards the target area as expected, even though there is no SA-2 radar for the first missile to spot. The third missile fails to initiate its dive, and as such will completely miss the target area. In the third track, the radar respawns (placeholder for a radar deactivating and reactivating), and since the second HARM does not follow the correct flight path, it misses the second radar since it is outside of the HARM's FOV when it activates. The fourth track demonstrates that the HARM seeker activates far too early. Even in EOM mode, which is supposedly the most restrictive in terms of precision required of the target location, the missile turns to seek onto a radar more than 20 nmi away from its given target position. HARM_EOM_Tracking_bug_F-18.trk HARM_EOM_Tracking_bug_F-16.trk HARM_EOM_Tracking_bug_F-16_radar-reactivates.trk HARM_EOM_Tracking_bug_F-16_activation-range.trk
-
3 minutes 37 seconds after the start of the mission, while taxiing onto the runway, I accidentally crashed my TF-51D into the rear side of the Yak-52. The TF-51D's propeller jammed and the left wing was torn off, but the Yak-52 did not receive any visible damage at all and took off successfully. Неуязвимый Як-52.trk
-
I crashed the helicopter - just for testing - and noticed that the airflow is still displayed but there's no rotor. The airflow only stops, when the engine is off. You should add the condition - rotor available and moving or gone. See picture:
-
Since 2.9 the Manual Gain Control Up/Dwn OSBs don't change anything. As far as I can see all the other OSBs are good. Cheers, Dr Spankle
- 1 reply
-
- 1
-
-
Using a Samsung crg9 5120x1440 49” ultra wide monitor. Game looks fantastic, everything is great, except the HUD’s. The lines and letters are fat and blurry. Its not a brightness thing. I’ve had to modify the .lua files in each of my planes ( and make ovgme mods so I don’t have to keep redoing them) to get the HUD lines and letters to be crisp and clear, like when using a non-ultra wide monitor. The rest of the graphics in game are great. I’ve seen people mention having similar issues on ultra-wides in the past, just thought I’d bring it up again, maybe ED can add to the list to figure out better native support for ultra-wides Oddly enough its not as bad in the F-18 as it is in the AV8B, F-16, and A-10. The harrier is the worst as it also affects the mfd’s as well. A-10 I have not adjusted* couldn’t fine the correct file/ lines to edit.
-
In many cases it's so difficult to boresight the Maverick, because of the font color on the display. Check how is the font color compared to the sky in the background. Impossible to see anything. Can the font color be changed to something different? null
-
Don't know if that is normal behaviour. 1. Go to DEST page OA1 and create the triangle offset point. 2. go to TGP and move the target STP point so it moves also the offset triangle. 3. press CZ in the STP point. The Triangle disappears, but still the DEST page has the info in it. I have to put back all info again and enter to make it appear again. I use this mission in steerpoint 1 kkF16.miz -
I haven't noticed this before today's patch - but the TGP model appears to be stuck in a forward looking position - even though it's working fine in (moving) in the cockpit. Sorry, no track file this time.
-
.JPG.ed3f014e0d08730c18194b07f8bfbd10.JPG)
Hello, I would like to try simulate "false" VOR approach with using NS430. I need precise heading of runway and this heading should be set to an OBS mode for URMO. I am at FARP next to RWY 08 with the same heading asi RWY is. In editor is absolute same heading. When I start up my NS430 and set OBS mode for URMO with heading 087° (RWY heading from ED maps at kneeboard). Magenta line should go exactly through URMO point with exactly the same heading as RWY. It is not. The line should be go exactly through both NDnullBs. It is not. Where I making a mistake please? Thank you Jiri
-
Hello, The distance of a valid bomb pickle does not match, the bomb falls short, see track. GBU-38 does it as well. Thank you and best regards rng_cue_bug.trk
-
Pressing the SPC button on the UFC inserts 2 spaces, one for pressing and one when releasing the button. Happens when clicking on it with the mouse too The CDU SPC works as expected, inserting only a single space for one press+release
-
Hi, @Moonshine @Lord Vader @twistking @BIGNEWY This has been raised more then a year ago and even though it was reported as fixed it was never fixed. In this post and in several others. The triangle indicating the position of OA1 is showing up below ground, despite its altitude being set correctly. Is this still on the Bug list? When will it be addressed?
-
Hello, Today I was practicing some CASE III recoveries and while approching the carrier the map and TACAN ranging stopped updating mid flight. I don't believe the signal was intrerrupted by terrain. This is not the first time I have observed this issue. Please find attached the track. (The F18 flight comes after the F14 flight) F18 TACAN and Map Stopped Updating mid flight.trk- 1 reply
-
- 1
-
