Jump to content

escaner

Members
  • Posts

    786
  • Joined

  • Last visited

Everything posted by escaner

  1. Display the fps counter in DCS and deploy it with the arrow to see the graph. I had microstutters every second due to Tacview in highly populated maps, they appeared as CPU spikes in the graph. If not, is the fps counter stable at 120? If the graph is a more or less a flat line (no spikes) but gets below 120, the panning with TrackIR is not smooth. Maybe try locking it at 60fps then or lowering the graphics settings for low level flights.
  2. I uploaded the missions here: Full mission: https://drive.google.com/file/d/15t1iwaDLB3Lb_3T3jMA5Os8Meaqv4Rw3/view?usp=sharing I guess this will be the quick action mission: https://drive.google.com/file/d/1k26Bp-SzZBCmITOMrYG6W3YtgITyezZD/view?usp=sharing
  3. When did you last try it? Draconus fixed the mission, but I don't know if it made it to the official distribution. This is the thread. I see that his links no longer work, I probably have it still in my drive. If it does not work for you, ping me and will look for it.
  4. Wow, this bug is nasty in the Hornet and Tomcat. I can be clearly seen in any light texture. After an upgrade on my computer I finally can enable SSAO, but both on Low and High settings they look the same, with that fixed pattern on the screen that does not move with the view. Too bad, because otherwise SSAO looks great in DCS. I see that this was reported over two and a half years ago... anyone has found a workaround other than disabling SSAO?
  5. The cross on the designation point was removed years ago because it was not correct. There is no mark now.
  6. I tried today this full mission, it worked great, thanks a lot!
  7. How do you disassemble the button? I removed my pickle button from the stick (lately it is doing double clicks), but I was not able to open it up for cleaning or fixing. I tried pressing on the two tabs that go through those two rectangular holes with pliers, but did not seem to compress them down and I fear breaking it.
  8. I have tried three times the last version and all of them the convoy moved, awesome! If you want to fix the full mission I will definitely try it.
  9. Hello draconus. That fixed the script error popup, unfortunately the convoy still does not move. I am attaching the track and dcs.log. All mods, scripts, keeboards and liveries were removed and shaders deleted. watching-the-devildog-instant.trk dcs.log
  10. Over a year later and new computer, I figured to try it again. The mission is still bugged: as always, the convoy never moves and now on top of that I get this popup from time to time. It would be nice if this mission got fixed... nullThanks
  11. Just that: I wanted to know if there is a planned timeframe when Jester will be able to operate the TGP in the F-4E. I remember that it took some time in the F-14 too. Thanks!
  12. Go to the bin directory in your dcs installation and type: DCS_Updater.exe update 2.9.5 I am back at 2.9.5 because I was fed up with those constant freezes. And so are my friends who fly with me because I always serve the missions. As a bonus, fps have also increased dramatically.
  13. I am talking about those 125 combat missions.
  14. I guess dropping bombs that kill people is completely fine as long as you don't curse them in the process.
  15. I just wanted to report that for me sight depression, heading and course selection are perfectly usable now after the patch. Thanks a lot!
  16. Hi @Zabuzard, Obviously I was not double long tapping to lock in that mission. As I said, it worked in the previous and next (after restarting DCS) missions. Actually I think this was the only time I had this problem and still had the track just because it was MP and they always auto save. Anyway, what you say about receiving the input twice makes sense. I have been watching the video and Jester was replying twice in that mission, e.g.: "Locking bogey right 5 21 miles - Alright, focusing on your guy" or "Copy - Copy I've got that one" or "Roger - Alright, focusing on your guy". I didn't notice at the time, but watching it again it is pretty obvious.
  17. This breaks a lot when pulling g's. Is it WAI or a bug? It is weird that this is the only thing that always breaks... nav-comp-failure.trk
  18. Oh BTW, in my case I had the new setting "CPU: Radar Performance Mode (WIP)" enabled.
  19. This happened to me last monday. I flew 3 times the same mission with a friend and the second one Jester would not lock on long press of context action (instead he just focused). I restarted DCS and it worked again the third time. At the end I managed to lock through Jester's wheel, but lost the lock immediately (might not be related). IIRC, boresight auto lock worked fine. I am attaching the track. Also have a video recording if needed. BTW, it is the default Ground Alert Intercept mission modified for MP. server-20240610-195033.trk
  20. Hi, while you are at it, please check also the Reticle Depression bindings. It is way worse than Heading/Course.
  21. That is great news, thank you! @AeroGrappler Do you know that you can navigate the exterior ring in Jester UI with Q and E keys? Sometimes it is a matter of how many times you need to press E in the macro.
  22. Right now, when we press A to open Jester menu, it opens sometimes in the menu we last used instead of always in the same place. In order to be able to program macros in Voice Attack and/or HOTAS that automatically navigate the Jester menus, it would be nice to have an option (new keybinding) to open the Jester menu in the home menu. E.g., in the F-14 you knew that pressing A twice you would go to the main menu (first press for "context" menu, and second to back up to the main one). But in the F-4 is is impossible for the macro to know how many levels it needs to back up to get to it. Thank you!
  23. That is how it works for me, I spent like an hour yesterday until noticed that the symbol for the deadzone is not % but o/oo. The manual is correct although confusing, because to set that 2% deadzone, you need to input a value of 20 o/oo.
  24. Dead zone is not a per cent quantity. It is per thousand. If you set it to 50, it will be 5%
  25. I have removed all mods and liveries and done a full repair the problem persists. This is the instant mission, where you arrive directly to WP1, no FP involved. What am I doing wrong? https://www.youtube.com/watch?v=yAj90_TthxM
×
×
  • Create New...