Jump to content

Weidlich

Members
  • Posts

    73
  • Joined

  • Last visited

About Weidlich

  • Birthday 02/22/1985

Recent Profile Visitors

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

  1. After playing with the displays I found out what is different from before it got broken/fixed: The cross will be displayed in AG mode, but only if you have the TGP active on one screen and the HSD active on the other screen. In this combination it doesn't matter wether if the TGP or HUD is the SOI, the cross will be displayed and moves when you move around. However as soon as you deselect the TGP on the one screen the cross will disappear on the HSD. Before it got broken the cross was always displayed on the HSD independent from the TGP and always showed the position where your SOI is looking at on the ground. I hope the track and the description is clear enough. Maybe the implemented fix is not perfect or the logic before was better than the original one on the plane. My standard display setup is alternating HSD/TGP on the left and the WPN on the right. So looking for GND targets premarked on the HSD I was able to slew over the target with the HUD and had the cross on the HSD as my reference. Then I could switch to TGP display and fine tune to fire the Maverick. This way of deploying my weapon doesn't work because the TGP display is missing. Kind regards dcs.log Position cross error.trk
  2. May I see a screenshot of your MFD in AG mode? For me it still looks like the attached image not showing any cross.
  3. Hi! The open beta released on 28th April lists this as a fix: Fixed: White cross on HSD when using AG mode is missing However it is not fixed, this bug report still applies, everything is unchanged: I didn't attach any files or screenshots as it is exactly the same. May I ask you to follow up what has actually been fixed?
  4. With the last patch the AG mode the position cross disappeared on the HSD. Before the patch when being in AG mode you always saw a white cross on the moving map whereever your current SPI was (Fixed Waypoint, HAD lock, TGP). This is completly missing now. You could slew the TGP around and the cross on the moving map moved as well so you knew exactly where the pod was looking. Now the cross is completely gone so you have no Idea where you are looking. In the picture I am in AG mode with the waypoint at my 2o'clock selected and the TGP slewed there. I am expecting a white cross on top on the waypoint which moves when I slew the pod to a different position. dcs.log
  5. I am having the same problem. No trackfile but steps to reproduce in Multiplayer (haven't tested SP): Empty jet, so open refuel/rearm and load fuel and weapons incl. the HTS. Once refuelling starts I power up the jet and start it. The HTS is being loaded after refuelling is complete and the jet is completely ready to taxi. Being airborne the HTS works like a charm and I can fire my Harms. Then land and just rearm with the loadout you had before so you restock the Harms. Being airborne afterwards the HTS is blind, doesn't show anything. Cycling the HTS power doesn't fix the problem, only selecting a new aircraft does.
  6. There you go. It is like this since Viper Day 1. Very annoying when you have to repair after a fight or mishap during landing and you have to realign the INS all the time and not even Stored Heading will work. Same behavior when you do a cold start or whatever else you can do to join the seat. INS power fail.trk
  7. https://1drv.ms/v/s!Aqt9J1OkiSdKg6hjDcsLaNSapBx7Kg?e=hwQGBd I press AG master mode, afterwards I click upload in your App. Then you see on the screen what happenes. When I am in NAV master mode it works like a charm.
  8. Bug report: Uploading the MFDs, Harm, HTS stuff doesn't work when you are not in NAV mode. Doing it while in AA or AG an input is wrong and it hangs at the DED. I suggest adding the command to go to NAV before entering anything in the script. Andre
  9. did you set the bomb from AIR to GND under CNTL? that's the only required change, then 2 of your 31/3B's bombs will kill the bunker.
  10. it happens on my PC and laptop. Maybe you can see something in the log (aprox 150MB filesize): https://1drv.ms/u/s!Aqt9J1OkiSdKg6R3D2oZs4XFC2oDAg?e=fQjRjk again your app was open all the time. just in the background of DCS, not minimized, no second screen.
  11. the app is open all the time. I open it before launching DCS and close it afterwards. I only play multiplayer so all during MP sessions.
  12. Using 2.1.1: I keep getting a lot of error messages in the dcs.log (aprox every 30sec one error log): 2021-11-26 14:58:45.915 ERROR DCS-DTC: Error at accepting connection: timeout 2021-11-26 14:59:13.154 WARNING LOG: 1689 duplicate message(s) skipped. 2021-11-26 14:59:13.154 INFO NET: Current ping: 224.7ms 2021-11-26 14:59:13.154 ERROR DCS-DTC: Error at accepting connection: timeout 2021-11-26 14:59:43.169 WARNING LOG: 1956 duplicate message(s) skipped. 2021-11-26 14:59:43.169 INFO NET: Current ping: 227.8ms 2021-11-26 14:59:43.169 ERROR DCS-DTC: Error at accepting connection: timeout 2021-11-26 15:00:13.173 WARNING LOG: 1914 duplicate message(s) skipped. 2021-11-26 15:00:13.173 INFO NET: Current ping: 247.7ms 2021-11-26 15:00:13.174 ERROR DCS-DTC: Error at accepting connection: timeout 2021-11-26 15:00:43.177 WARNING LOG: 2000 duplicate message(s) skipped. 2021-11-26 15:00:43.177 INFO NET: Current ping: 222.0ms 2021-11-26 15:00:43.178 ERROR DCS-DTC: Error at accepting connection: timeout 2021-11-26 15:01:07.265 WARNING LOG: 1613 duplicate message(s) skipped. Any idea what's the reason for it? The app works fine, no crashes or anything. Just a flodded error log.
  13. Correct. I was experimenting with making the commands input as fast as possible while still working. I settled on 100ms value but it seems people have issues with it. I'll revert to the previous value next update (was 200ms).
  14. Yes same here! My guess is that the tool uses an old version of @Comrade Doge mod TheWay. This tool had exactly this issue and only fixed it a few days ago with version V140. I think when @SFJackBauer uses the updated code the bug will disappear automatically. Our problems are too high FPS. best regards Andre
×
×
  • Create New...