Search the Community
Showing results for tags 'investigating'.
-
The Laser Maverick / AGM-65-E will not track a moving target. The mav will show acquisition of laser if a static point on the ground is target-designated -- maverick symbology switching from 'X' to square. However if the pod is slewed (to fine-tune the laser designation point) or the pod is tracking a moving target, the maverick will go to 'standby' with the symbology going to 'X' and the MAV being crossed in the HUD. Steps to reproduce: Initial state: Ensure ordinance, atflir, and flight parameters are suitable for maverick employment ( can be verified by shooting a maverick at a static target) Have the MAV display in the left DDI, ATFLIR in the right. Box TRIG in ATFLIR. have a target ahead in the forward view of the maverick seeker. To Reproduce: Use the ATFLIR to track a moving target (point track). use the trigger to laser designate the target. Expected: MAV symbology goes from X to square as happens with a static target Actual: MAV remains showing the 'X' symbology indicating no lock. Second Reproduce: Designate a static target, use trigger to laser designate the target.. then slew the ATFLIR to fine-tune the designation point. Expected: MAV goes X to square when laser-designating target, remains with square symbology while ATFLIR is slewed. Actual: MAV goes X to square when target is laser-designated. When atflir is slightly slewed, MAV goes to 'X' symbology and remains that way for several seconds after the movement/slew of the ATFLIR has stopped. Anecdotally if the laser is moved while the mav is in flight, to fine-tune a laser designation point, the maverick will widely miss the target (likely due to a lost laser lock) The reason to carry a maverick vs say a gbu-12 is because its better suited to moving targets then a bomb, but unfortunately due to this bug it makes mavs useless for that case. TRK: https://drive.google.com/file/d/1XrVtQDrMvnNbbYA-my5trwcqOS96W4yi/view?usp=sharing -
Hi all! According to the DCS F/A-18 Manual (pag.338): "To make the corresponding waypoint an air-to-air waypoint, press pushbutton 2 (A/A WP) on the DATA subpage of the HSI; this will make the waypoint on the bullseye the selected air-to-air waypoint. Note that you may need to use the pushbuttons 12 and 13 at the HSI or HSI DATA subpage to change the current waypoint until the A/A waypoint is displayed. The DATA subpage of the HSI will display “BULLS” at the top of the display, and the HSI itself will display “BULLS” at the top right when the A/A waypoint is selected." In the picture below, waypoint #6 was selected as the A/A WP but "BULL" was neither displayed at the top of the DATA display not at the top right of the HSI. Three options: 1) the manual is wrong 2) something got broken 3) I'm doing something wrong Sometime back I remember seeing "BULL" though...
-
I noticed the Red dot with a '1' in it, over the Modules button at the top left of the main screen. There is nothing new for me to install.. I didn't expect there to be as I had not purchased anything recently. The Red dot does not show if I run the normal OB DCS. -
When using either the 1.78 or 2.24 factors with 4k (i.e., selected resolutions 5120 x 2880 or 5760 x 3240), George's target selection menu is either partially or completely, offscreen. In both cases though the text to select from is offscreen. It's apparent that George's overlay origin/placement is different than the controls overlay which works perfectly with both DLDSR settings. I have a RTX 4090 so I have a good bit of headroom. I limit framerate to 100 FPS. The improvement in image quality from using these settings is amazing. I have tested with the FA-18, A-10 and the Apache. All I have found so far is the problem mentioned above. This is very easy to test with an NVidia card and a 4K monitor. I have not included any mission or log files because they are not required to repeat.
-
In many firing instances, upon firing an AIM-7, the AI immediately breaks the lock by taking an immediate evasive action without any incoming fire. I can see dropping he lock to evade an incoming shot, but not before any incoming fire. Track and mission is quick AI only flight. No human control. F5 set up as target drone. F18 engages from ahead. 1.miz 1.trk
-
Nightmare 13 and 14 go straight for Batumi and land, right after taking off from Tarawa, and hence are not part of the rest of the mission. (Their radio calls still come through, so their absence is not that noticable).
-
When locking a radar contact into STT, no matter of the mode (RWS or TWS), from 40nm to cca 20nm, the target is not moving on FCR. It stays on approximately 35nm range. This applies for following aircraft: F-14, F-15, F/A-18, M-2000, Mig-29S and regardless of the map. Example is in attached track. f16_FCR_STT.trk
-
Hi, I was flying M10 to the point I have to shoot the F16 drone with the AIM9 but I was shot down by him with guns when trying to maneuver behind him. Is it expected behavior of the drone ? Because I was expecting a defenseless drone in such a training scenario, at least without weapons. Best regards, Pierre
-
Hi when you choose gbu 12 ( unlimited weapon on) in configuration 2x on pylon you may drop bombs only for times ( like in unlimited off). Game realoading only 1 gbu on pylon so you cant drop no more bombs. Bug was in ver 2.7 and is 2.8. Have you got such problem?.
-
hi if you commit through F10 to destroy a target (instead of your wingman) and you miss and run out of ammo, the mission is bricked. you no longer have any way to destroy your target - but at the same time, you cant make your wingman attack even though he still has jdams. this happened to me during the APC near the boat tasking. i missed my last GBU. there is still an option in F10 to make dutch attack the APC but it does nothing. no voiceline, no AI reaction and it doesnt disappear from the menu either.
-
investigating Ai affected by pitot ice p47
inpayne posted a topic in Aircraft AI Bugs (Non-Combined Arms)
Hello, I posted this on reflecteds page as this was on mission 4 of the wolf pack campaign. Anyway a bit of a bug, on the rtb back to England the AI started flying very slow and climbing. I noticed my ASI acting as an altimeter. (Pitot Ice or blocked pitot) A few stalled out and crashed (Like rookie IFR students ;) ) then the rest just bobbled along sometimes running into each other at the airfield and not a single one landed. I turned on my pitot heat and was able to land fine. Not sure if there is anything you can even do about this, and I found it interesting that AI was affected by pitot ice at all. It’s annoying to get ice in vmc but that's a different issue. Anyway, maybe it's a one off but thought to let you know. Keep up the good work. Thanks. Sorry no track… I forgot to save it. -
need track replay TRAINING MISSION: Carrier Taxi and Takeoff
trevoC posted a topic in Bugs and Problems
As soon as you move (to taxi to catapult 2) your wingman also moves and then turns into you damaging your aircraft preventing you from completing this mission. -
I was working on a mission, which has Time-Over-Steerpoint as a intergrated element in the mission when i realised the in-game TOS was off. I made another mission file and the issue persisted, and below are pictures from the times in the new example mission file: Time of the mission is set at, 01:30:00 LOCAL Dubai (GMT+4) ↓ ETA of the flights 1st waypoint 01:42:35 LOCAL Dubai (GMT+4) ↓ Now, jumping in the cockpit is were the issue appears, video below ↓ I hope the video is clear enough. Attached below is the .miz file. I did not get a track file for this but if you need itt let me know and ill make on replicating the bug. TIME TEST F-16.miz
- 10 replies
-
- 4
-
-
- crus page
- resave missions
- (and 1 more)
-
I've only been testing this for a short while, but I'm already seeing a trend. Ace AI tends to lose to Veteran and Trained AI in BVR fights. This happens because: A - Ace shoots earlier than Vet/Trained, leading to lower missile Pk. B - AI does not anticipate being fired upon and flies directly at the enemy until missiles go active. To be given a fighting chance, Ace AI needs to have missile launch range set to halfway between Max and NEZ, while hopefully having a longer ranged missile than their opponents in the first place. AI missile ranging logic needs to be looked at. The AI also needs tactics against preemptive missile launches, instead of waiting for a confirmed missile launch to react. I've also noticed that mixed AI skill flights will stagger missile launches (because lower skill levels wait until closer range to shoot) and this seems to provide an advantage in that when flying together mid-high skill AI will take long range shots to pressure targets into maneuvering while low-mid skill AI take high Pk shots that are more likely to kill. By accident, mixed skill flights are using more advanced tactics than homogenized flights. AI Skill Backwards Result.trk -
First of all, what a great mission! But sadly I got the deserter shot down radio chatter + fail message + forced exit while rtb... except HE DID safely land and I got the radio message telling me to RTB. The fail radio chatter happened a LONG time after he actually landed, because before turning back to Nellis I had to air to air refuel which is really hard and took me a long, long time. Really long. Maybe assets dissapear from the ground after some time since having stopped and the mission took this as if being killed? I don't think there's any traffic in that airport that could have crashed with the deserter while parked. -
investigating AGM-84D not reaching target despite IN RNG cue
Ahmed posted a topic in Bugs and Problems
Hi, In close relation to this other bug report : The Harpoon seems to fall short of the calculated LAR and doesn't reach the target despite receiving an IN RNG cue. Regards, harpoon_fail.trk -
Hi, The AGM-84D LAR calculation seems to be hardcoded to ~97.2NM (180KM). FLT profile selection seems not to make any difference. Regards, EDIT: Intended to post in Bugs subforum, please move harpoon_hi.trk harpoon_lo.trk
- 1 reply
-
- 1
-
-
investigating ICP Mark - MGRS displayed with 9 digit grid
Rich_Beam posted a topic in Bugs and Problems
A Marked Position is displayed with Lat Long and MGRS. But the issue is that the DED shows the MGRS grid in 9 digits instead of 10. MGRS.jfif -
With the MT command to enter DCS Syria Map online Rotor - heads server , All my memory is being used and this is leading to Stutters . A total of 32GB System memory is being used . Still testing . Normally only 24GB used Syria Map . Same server . Only 8 players -
Hi, DCS MT works well in 2D. I see a significant performance improvement. But in VR, I get some kind of screen overlap (at least this is how I interpret it - see images below) and the performance did not get better (FPS remains the same). Troubleshooting steps: Repair DCS Delete fxo and shaders Reset GPU driver to factory settings Update GPU driver (6900 XT) Update Windows 11 Use VR headset with cable, with air link Reset VR headset to factory settings Stopped using Oculus tray Several restarts dcs.log DCS MT VR1.trk DxDiag.txt
-
I've never used or installed OpenXR, Is it now required? I thought it was optional. Dxdiag added. Additional logs attached, tried starting DCS many different ways, with and without steamvr, different openxr runtime environments. dcs.log DxDiag.txt dcs.log dcs.20230311-211257.dmp dcs.log.old dcs.log-20230311-211257.zip dcs.20230311-211155.dmp dcs.log-20230311-211155.zip dcs.20230311-211102.dmp dcs.log-20230311-211102.zip DCS.exe.10728.dmp.zip DCS.exe.15628.dmp.zip DCS.exe.18896.dmp.zip
-
Crash on startup VR with SteamVr 5800x3d 32gb 1x16 ram 3600 cl14 gskill rtx3080 nvme tried a full repair and deleted fxo and metashaders2 but crash anyway! simdhaker anf dcsbios enabled dcs.log-20230310-223526.zip dcs.log-20230310-222206.zip
-
Hi, DCS 2.8.3.37556 Open Beta Multithreading or normal made no difference F-16 Litening TGP travels downwards when commanded POINT or AREA track from over 54 NM slant range. In INR (TMS aft) it says in place, but when commanded POINT or AREA track, coordinates start running on the display and the view starts to travel downwards. Steps to reproduce: Fly towards a steerpoint over 54 NM away TMS aft - Note the pod stays in place Enter either POINT or AREA track - Note the pod travels downwards and coordinates change on screen TMS aft - Pod returns to STPT, view stays in place and coordinates are stable Repeat steps 3&4 and keep flying towards the STPT When withing 54 NM slant range, note that POINT or AREA track work as they should: Coordinates are stable and the view stays in place. I say repeat steps 3&4 because it seems the pod might not stop moving on its own even when inside 54 NM slant range, if commanded to track when outside 54 NM. So to test, keep repeating the TMS aft / track commands. Best regards, itn F16 Litening over 54NM slant range.trk
-
investigating Visibility difference in MT?
Hotdognz posted a topic in Multi-Threading Bug Reports (Temp)
First my PC specs , 13700K, 4090, 64gb DDR4 3500, Z690 M/B, HP G2, Windows 10 very optimized for gaming. Playing on Instant action Syria-F16-Freeflight, I have visibility set to Ultra and close by city's are only rendering in at 5kms, switching between Ultra and Extreme I see no difference in visibility distance at all, in the screen pics I have active pause on and you can see what is rendered in the std cockpit view in the F16 cockpit and then what pops in when you zoom in, also a map pic is included shown about 5nm from the city to my plane, I have also included my settings. 1st It seems strange that ultra and extreme settings make no changes at all to the game view distance 2nd I cant remember this much pop in before MT was introduced, has ED dumbed down the graphics distance to help with the getting better FPS, id be interested to see other high end users experience with this.
-
DCS crashes on launch I was able to avoid the crash by going into the BIOS and changing the amount of active cores to 1 instead of all, changing back to the default amount causes the crash again. All of this was done after renaming the SavedGames/DCS folder, Running a cleanup and a slow repair. Same topic as the embedded one (it was created before this section of the forum was created and was requested to post it here). Crash dump hangs and is unable to generate a working zip. Uploading it anyways and the attempted repair of it. List of Attempted steps: Renaming SavedGames/DCS folder CRASH Disabling all mods CRASH Cleanup and slow repair CRASH Enabling/Disabling Hyperthreading CRASH Making sure processors aren't limited by msconfig CRASH Updating windows and all drivers alongside BIOS CRASH Repairing windows image and running scannow CRASH Setting the amount of Active cores to 1 !!NO CRASH!! Uploading Additional MT.lua log files. @BIGNEWY@Flappie@NineLine Requesting Merge with: dcs-nonMT.log dcs-MT.log DCS Single Active Core.log DxDiag.txt dcs.log-20230311-221943.zip rebuilt.dcs.log-20230311-221943.zip DCS-SINGLEACTIVECORE-MT-LUA.log DCS-MT-LUA-CRASH.log
.jpg.3864722e569189b741a236a36491a976.jpg)
.jpg.ed92270de3fcd484c6db24a33402cd19.jpg)
.jpg.d61840d6172da394a29951cc90345c4d.jpg)
.jpg.eb3d2f568728160e1a55f71506c44e96.jpg)