Jump to content

Scotflieger

Members
  • Posts

    46
  • Joined

  • Last visited

Personal Information

  • Flight Simulators
    P3Dv5, P3Dv4.5, MSFS2020, DCS
  • Location
    Scotland, UK
  • Interests
    Flt Sim, programming

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The HMD designated target diamond does not appear to be indicating the correct target position. After selecting a waypoint and pressing WPTDSG the HMD shows the target diamond positioned significantly short of the waypoint position. The Targeting Pod is correctly pointing at the waypoint and can be moved and used as JDAM target coordinates. Is this a bug with the latest beta?
  2. That was the problem. The DCS_updater.exe was set to compatibility mode. Stable 2.7.1 now installing. I would point out that this is how it downloaded straight from the server yesterday. It was not previously installed or run.
  3. I run the stable download link for 2.7.1 again this morning. It started by reporting that 2.7.1 was available but after updating the updater version (2.11.2.89) again it gave the warning that Win 8.1 was required and reported after a short delay that it had successfully install 2.5.6.61527.3. There appears to be a problem with the fresh install procedure. It is using 2.5.6 not 2.7.1. Files attached. dcs.log dcs beta.log autoupdate_log_old.txt autoupdate_log.txt
  4. As I said I only previously had open beta 2.7.1 installed, This was an attempt to install the full release for the first time.
  5. I run a fresh installation of DCS World 2.7.1 today and got a warning that Windows 8.1 or later was required. I am running the latest version of Win 10. After many hours waiting for the install to complete I ran the DSCUpdater.exe and got the same message. The splash screen also showed v2.5.6 not 2.7.1. I have been previously using DCS open beta 2.7.1 without problems.
  6. I carried out 2 further tests to check whether INS alignment state was a factor. From Cold and Dark Instant Action I carried a full start and waited for the INS to report OK and selecting NAV. I then entered the GRID coordinates as reported above. It worked as expected on both occasions. Unfortunately, when I click Quit to save the TRK file, DCS crashed.
  7. Having worked on a number of real world military aircraft (Jaguar, Tornado GR1, Harrier GR5) it would be strange if the mission data can not be entered while the pilot waits for the INS to align.
  8. Thank you for clarifying the decimal SS.SS entry method. No further action required.
  9. Original problem found in Multiplayer. Tried to reproduce in Ready on Ramp Instant Action without success. However, when I started in Cold and Dark Instant Action I was able to reproduce as described above. After engine start and during INS align, HSI selected on right DDI. WPT11 selected and DATA/POSN entered (N444017 E400117). WPT12 selected and PRECISE input OBS pressed. Repeated pressing of GRID caused 'colon' to appear briefly and disappear. It was necessary to completely exit HSI and restart attempt. This time GRID 'colon' remained selected and Letter Gird Selection appeared on DDI. GRID Entry 2.trk
  10. When inputting Lat/Long Coords for AGM-84E/H SLAM/-ER missiles using the UFC TOO / POSN it is necessary to click on ENT twice for the input to appear on the weapon's programming page. This is needed for both LAT and LON inputs. Only one press of ENT is required for all other inputs to appear (eg. HDG/ANG/VEL/ELEV).
  11. When selecting HSI/Data/UFC/Grid entry the UFC GRID button does not always highlight (colon) and display the letter grid. When I mouse click on the GRID button it self cancels. I had the Precise coord input button selected. Previously, I had inputted a LAT/LONG using POSN option. It is necessary to completely deselect HSI/DATA and start again for the GRID to be selectable.
  12. Apologises @BIGNEWY for reopening this issue but I do not believe it has been fully reported as you noted in my previous thread now closed. I have been able to record a shorter track file detailing the problem for developers. It shows a JDAM TOO attack on WP1 using LITENING pod. Initial target designation works correctly and weapon released. Aircraft turned 90deg to starboard to place WP1 on port beam. WP1 deselected and reselected but target appears directly ahead of aircraft; waypoint circle disappears. Repeated several times with same result. Sensor Select moved from FLIR display to HUD. This time WP1 correctly designated as target. Again apologises but this bug makes precision attacks almost impossible to execute. Test01.trk
×
×
  • Create New...