Search the Community
Showing results for tags 'investigating'.
-
The ADF bearing circle on the HSI works fine in Track Up, but it doesn't follow the magnetic bearing when you switch to North Up. Instead it maintains the same position on the outside of the compass rose. I.e., if it is at the 12 o'clock position in Track Up flying west, it remains at the 12 o'clock position in North Up instead of moving to the 9 o'clock position to maintain the correct magnetic bearing. Track attached. adftest.trk
-
After takeoff 45 minutes a stable 60 fps constantly flying over las vegas, and suddenly the drop to 43 fps, GPU and CPU reaches 100%, in this mission there is nothing but free flight, there is nothing to drain resources there. I can't upload track because of size. dcs.log DxDiag.txt
-
Just came back from two week vacation and ran DCS. On start it suggest to install Apache DLC. Once I confirm the DCS closes but nothing happens!!! Could anyone please help with this? TY Sent from my iPad using Tapatalk
-
need track replay BUG - A/S button not synced with WEP page
JIGGAwest posted a topic in Bugs and Problems
I've noticed the issue where the airframe is armed -A/S set to ARM (this track has ground override armed as well) and the WEP page shows hellfires are still set to safe. When this is the case, you will not get a George CPG AI constraint box. This may also effect Multiplayer crews. Pressing the A/S once, will flash the ARM status and not SAFE the airframe, but GEORGE AI has an override on the ARM state and will remain armed. Pressing the A/S several times rappidly will finally unsafe the hellfires. track 20MB below https://drive.google.com/file/d/1iY6Ub1AqnbBQFytzZl5lrib-qS5m-xqK/view?usp=sharing -
As title - the stabilator position indicator on the flight page and the shutdown page is not synced between CPG and pilot, nor is the EUFD manual stab advisory. Stab position on the aircraft appears to be synced. Track replay to follow. -
investigating AH-64D Crash after creating point with LOAL
Account 42 posted a topic in Bugs and Problems
when i switch from the back seat to the front seat Use Hellfire LOAL mode crashes after ranging and creating points dcs.log https://drive.google.com/file/d/1deZu3Jpcp3ZLTSxZkfYmwCyE8rygHkMW/view?usp=sharing crash video https://drive.google.com/file/d/1fhGnPDahEZidmEjLKMSmI_zPVQBMZgV9/view?usp=sharing dcs.log https://drive.google.com/file/d/1deZu3Jpcp3ZLTSxZkfYmwCyE8rygHkMW/view?usp=sharing crash video https://drive.google.com/file/d/1fhGnPDahEZidmEjLKMSmI_zPVQBMZgV9/view?usp=sharing -
Currently aircraft equipped with TPODs can only point track other fighter sized aircraft at a range of 20nms. This is even though in IR modes (WHOT and BHOT) with the new FLIR system you can distinctly see a contrast between the aircraft and the sky behind them at a range of 40nms (around the range of where planes render visually) and a TPOD should be able to lock this pretty discernable target out of the sky. Can we expect an increase in the range where you an point track other fighter sized aircraft? LITENING pod on the F-18 seeing a target (J-11A) at 42nms. This target cannot be locked up even though there is a clear contrast: -
investigating AIM-120 still can not chase simple Split S manuever.
opps posted a topic in Weapon Bugs
Tacview-20220609-013357-DCS.zip.acmiAMRAAM.trk -
Currently unable to share SPI over network when using the targeting pod. Only steerpoints. Work around is to create markpoints which can be shared. TGP is set to point track mode to track target, HSD is the SOI, COMM-in long press. To my understanding reading the manual you should be able to that as described below. When the HSD is the SOI: - If a ground threat is boxed, the location of the boxed point is transmitted. - If no A-G threat is boxed, the location of the System Point of Interest (SPI) is transmitted if a sensor (FCR or TGP) is tracking the SPI; otherwise, the current steerpoint location is transmitted - When the HSD is not the SOI, the SPI location is transmitted if a sensor is tracking the SPI; otherwise, the current steerpoint location is transmitted
-
I think I've found a potential bug with the RWR indicating a TWS launched AIM-54 at some rather long ranges that seems to be present in the ED modules I've tested but absent from the third party modules. I've just made the same bug report in the Viper bugs subforum, but I'll add one here and in the Warthog bugs subforum too. I would expect that a TWS-guided phoenix would not give much or any warning prior to going active at relatively close distances (I'd have expected less than 12nm depending on the usual variables). Right now, the Hornet detects a TWS launch of any phoenix variant from any AI Tomcat variant on the Caucasus map. System specs are: 5800X, RTX 3070, 32gb ram with DCS on an SSD. I haven't yet been able to test against humans, and I haven't yet tested the Hornet on other maps (although the same bug with the Viper is also present on the Persian Gulf). FA18CvsF14B.trk dcs.log
-
Title and video already indicate the problem. Apache hellfire.trk
-
I appear to have found a bug which is non consistent, but does appear in the attached track file. This anomaly can appear in SP and MP it can also appear and during a long session in MP and it can revert to normal behaviour during that same session. The track file pertains to the Instant action NTTR 9X Mission, the error appears after the 3rd drone is shot down. It is not the only occasion this has happened. In short when cycling between Dogfight Overide/Nav Mode/Missile Override during an engagement and I return to Nav Mode (HUD) NO RAD appears at the top of the HUD and the FCR MFD is locked at 10 miles and cannot be changed cycling the TMS switch in 4 directions changes the display graphics and appears to restore the RADAR but the range remains fixed at 10 miles. Changing to Missile override allows RADAR range to be changed. Dogfight mode appears to function normally. However, if the HUD is then set to Nav Mode the ACM Lock reticle can lock any aircraft in 10 mile range complete with the audio “LOCK” while in Nav Mode with the range fixed at 10 miles. This is not shown in this track but I can try and replicate if that would help. I have run the DCS repair and I have checked switch bindings on my HOTAS. FCR BUG.trkFCR BUG. I wonder if this might be related to other reported RADAR detection/locking issues experienced by community members but which continue to be elusive.
-
need evidence ATFLIR Drifting when slewed before TDC depress
Swift. posted a topic in Bugs and Problems
ATFLIR will drift when you slew before depressing the TDC to 'unlock' the pod from the waypoint. However, if you dont slew before TDC depress, it wont drift. 1. Designate WP 2. Slew 3. Depress TDC 4. Slew and release: Notice the pod drifts as if in snowplough 5. Redesignate WP 6. Depress TDC 7. Slew and release: Notice the pod stays fixed as it should Drifting.trk -
can not reproduce ATFLIR 2nd Undesignate not removing TGT
Swift. posted a topic in Bugs and Problems
With ATFLIR, the second undesignate action will not remove the TGT indications from the HSI. 1. Designate WPYT 2. Undesignate 3. Designate WYPT 4. Undesignate: note the HSI still shows TGT rather than WYPT on PB11 2nd Undes.trk -
Is it me, or something odd is going on generally with the A-10C II Nevada CAS instant mission: the wingman reports targets of opportunity at the beginning of the mission, yet he's not answering to FM radio calls. I can't give any orders to him I double checked the FM frequency in the mission editor: it's 251 MHz, so tried to use that frequency in man mode and preset channel 1 also, with no luck after successfully completing the mission on my own with an unusable wingmen circling around we made RTB along the planned route and I manage to land correctly just to struck in the back moments after touchdown by my own wingman Somehow the AI understands that we're about to land (based on speed, landing gear and flaps status). Yet he's moving erratically (jumping up/down in the air) or worse - as I wrote previously - is completely out of sight (behind me) just to be in the worst place the worst time seconds later. Ain't the the AI somehow sense that I'm in front of him on the runway and acts accordingly? This way this SP mission is no joy...
-
As mentioned here: https://forum.dcs.world/topic/299572-jsow-sms-cntl-page-does-not-open/?do=findComment&comment=4956795 The CNTL page isn't functioning, but the double launch parallel or in trail work and 2 weapons are being deployed. however, during testing, i found some inconsistent behavior with the JSOW. as one can see in the track, sometimes one JSOW of the first pair (very rarely also both weapons) that is being dropped (no matter if in trail or parallel impact selected) will slow down significantly and at times (especially seen in track JSOW4) not even reach the target. see tracks + tacviews attached. so in short: deploying the weapon is not the issue, but weapon behavior is not very consistent when using pair releases. i have not tested single release here, so i don't know if that happens there too at times. not to speak of the rather underwhelming effect on target upon impact, but that's another issue with cluster bombs that aren't SFWs it seems. JSOW4.acmi JSOW3.acmi JSOW2.acmi JSOW.acmi JSOW.trk JSOW2.trk JSOW3.trk JSOW4.trk
-
Hello, I do not know if this would be implemented or not. As it’s a real capability of the SPO-10 to change tone as range decreases, since it only shows signal when under direct illumination, and the closer you are the more time spent in direct illumination, the beeps become longer, referencing the user and technical manual from 1976, page 62 and 63 “and when the irradiating radar approaches, the frequency of the alarm will increase, and decrease when moving away. This occurs because, as the aircraft approaches, the time of irradiation of the aircraft increases, while the time between irradiations decreases at the same scan periods, which gives the impression of an increase in frequency.” In the track I am engaged by MiG-25 from 50 km away, tone is about more then once a second, and does not change until merge. I have placed units up to 100 km away and tone is the same. However I do appreciate that all four lights are lit when very close. Even though I know it is tricky becuase signal frequency is also determined by scan rate, and that would take a lot of time to implement for all radars in game, if frequency could increase as range closes as this document instructs it would be a very welcome feature, thank you Mi-24RWRissue.trk
-
I think that the effect of changing the antenna elevation while in ground radar mode is modeled incorrectly. Expected behavior: when moving the radar antenna up, the nearest radar returns should vanish first (for small upwards elevations), those furthest from the plane last (for largest upwards elevations). When tilted towards lower elevation (downwards), the furthest radar returns should vanish first. Observed behavior: when tilting upwards, the radar image gets dimmer overall. When tilting downwards, also the full radar map stays on the screen. At sufficiently large downwards elevation of the radar antenna, the radar map starts to look through mountain ranges and suddenly is able to display valleys on the other side (F16-GM radar elevation.trk) F16-GM radar elevation.trk
-
As per title the MPDs and TDU are currently rendered twice in the main simulation viewport if their viewports are exported. Effect is demonstrated by two things that happen when displays are exported: TDU in the main viewport shows a ghost image. One copy respects the day/night setting on the TEDAC rotary switch, the other does not. If render_purpose.GENERAL in line 81 of viewporthandling.lua is commented out one copy of the TDU in the main viewport disappears. The KU/CMWS/EUFD are removed from the main viewport (as per behaviour in other modules), but the MPDs and TDU remain (although with improved framerate suggesting some rendering workload is reduced).
-
When pilot uses the trim, CP/G's joystick if is with FFB changes the forces center point according to the pilot's trim. This is very unwelcome situation in situation when for the CP/G the joystick is the multipurpose device used for TADS targeting or for the helicopter steering depending of the modifier switch state. So if the CP/G's joystick is in the TADS steering mode (determined by modifier switch state), the FFB for this joystick should be disabled (preferably). -
Tried running repair, nothing. Tried ticking and unticking the show IHADSS box in the special menu, nothing. It shows up just fine in 2d, and Ive seen it once in VR....where my head was offset to the left and re-centering made it disappear. Running DCS in VR at DCS resolution was the only way to bring it back for some odd reason and showing in right eye, but as soon as I bring DCS resolution back to square in VR and recenter my view in the AH-64, the monocle disappear again. The display doesnt move, its just the monocle disappearing. https://www.dropbox.com/s/s9nua6wmh73xktf/AH-64_TRNG_04_CAUC_Gun.miz_06052022_14-56.trk?dl=0 track file This has started happening since latest patch came this week. -
If the CPG loads into an aircraft after the PLT door has been closed the door shows open to the CPG. Requires the PLT to re-open and then close the door to re-sync.
-
Hello. I suddenly noticed today that the Rgh polarity switch no longer changes the polarity of the CPG FLIR TADS display. At the same time, the FLIR GAIN/INT switches have stopped affecting the actual screen. I can confirm that they are working when using the TADS trough IHADSS (both polarity and the Gain/int knobs, when I pull the symbology up on the monocle both as sight and as sensor. I have confirmed that the keybinds are still working in DCS, and I have tried repairing the installation etc, to no effect. I am also aware of the difference of FLIR and DTV, and I have had this work in FLIR before, it just suddenly stopped working for me. I also have no problems changing the polarity on either the PNVS or TADS when called up in the backseat. Anyone else had problems to this effect? -
Hi, during a couple of MP sessions (with both pilot and CPG) slots occupied, I have had this issue when shutting the aircraft down for repair, upon getting the aircraft restarted, the cyclic controls are out of sync. Specifically, the stick wouldn't push right past the centre position and front and back was also not right. However, when I checked the controls in the controls menu, it stills shows full and correct range of motion. When taking off the aircraft is affected by the apparent range of motion seen visibly in the game on the cyclic and not what is showing in the controls menu. I am trying to get a track file off our cloud server to provide. Thanks
-
This only goes for MP-servers. As a CP/G you can't switch the cursor from the left to the right MFD. If you push the button on the LHGrip, or use a binding, you will see the cursor switch, but immediately return to the left MFD. Occasionally it wil freeze there. The track is 11.1MB and too big to include here. Please download at http://www.marctelkamp.nl/GR_TTI_v1.81cf_winter-20220503-224441.trk
