Jump to content

Mr_sukebe

Members
  • Posts

    4004
  • Joined

  • Last visited

Everything posted by Mr_sukebe

  1. As mentioned, my guess is that it’s a combination of how many USB devices that you’re using AND how many possible commands could you bind. Basically you’re looking at a matrix of one multiplied by another. I’ve no idea why it’s so CPU intensive. I’d expect it to have more impact on RAM use, but that’s clearly not the case. Hopefully ED will track down the root cause.
  2. For anyone experiencing Control Mapping issues, please use the tickbox “Folded views” and only expand the controls that you’re binding.
  3. Within the controls section for my Phantom, I can see a warning symbol about the binding for the First Person Pilot Body - Toggle. By default, mine was empty. Even if I add a keybinding or binding for a HOTAS button, the warning symbol is still displayed. No, it's not a priority issue and it hasn't stopped me doing anything, but would be nice to get rid of.
  4. I believe that I've found a suitable workaround. Within the Controls section, there's a tickbox called "Foldable View". Enable it and only expand the section that you need to rebind. That has solved what was a major issue for me.
  5. Okay, have done some testing today: Have cleaned out FXO and metashaders (again) Removed most of my mods Thinned down my liveries Conducted a full slow "fix" using the DCS Updater/Launcher Checked my key bindings and removed any with contention Uninstalled the Phantom In short, none of the above seemed to make any significant level of difference, i.e. on opening the Controls section to modify key bindings, at least one of my CPU cores jumped to 100% and stayed there, sometimes 2. Then I tried pulling the USB plug out for one of my powered USB hubs that handles 4-5 of my USB devices, and the CPU loading dropped significantly. There appears to be two key influencing factors, i.e. The number USB devices connected and in use The number of controls that can be mapped. So for example, the F16 has a LOT of control options, whereas FC3 aircraft have far fewer. Opening the F16 control menu resulted in a significantly higher impact One thing that I tried that seemed to help was to use the Option within the Controls section of "Foldable views", which is a tickbox. I've just re-installed the Phantom and using the Foldable Views tickbox enabled has allowed me to finish binding my keys WITHOUT the game basically seizing up. So it looks like we have a workaround.
  6. Similar here. on looking in Task Manager, 2 of my CPU cores were maxed out. i tested it in both VR and monitor mode
  7. Yours doesn’t look that bad. 2 of my cores were at 100%. I’ll be investigating more later today
  8. Tom> Nope, sorry, don't know. It doesn't seem right. At least with mine, memory usage is apparently low, so it's not that it's paging. Pointless me even trying to speculate, as chances are that I'd be wrong. Do you have a lot of USB devices? I do. To see if it might help, I took a copy of current Inputs folder (in saved games), then deleted all the controls for my mod aircraft and also any now non-used USB devices. One thing I believe doesn't help is having too many USB devices.
  9. No solution, but what's your CPU usage like? I was having the same earlier, and two of my 8 CPU cores were maxed out.
  10. I've just loaded up DCS on my monitor, to conduct some further binding work for the F4. I'm running MT. My CPU is an i5 9700 (8 cores running at 4.5Ghz at the moment) I couldn't help but notice that DCS is currently using circa 20% of my CPU. This is having only just loaded DCS, on a fresh PC bootup, NOT in VR and NOT in a mission, or having exited one, just in the home page. My assumption is that 20% is NOT what I should be expecting. I can't upload a track file, as there's no mission involved. In the log file, I'm getting the following, which seems to be having an impact: ============================================================== 2024-05-23 18:11:42.185 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [2560, 1440] 2024-05-23 18:11:54.985 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0]
  11. Really enjoyed my first few hours with the Phantom. I did have some thoughts that I’d like to suggest: - Thanks for the kneeboard already created. However, can there be an option to disable those pages, if I choose to use my own - The kneeboard is great, but there are some things in the rather excellent manual, that are not in the KB, eg the need request external power during a cold start. Could they be aligned? - Any chance of a crew chief being added in next to the external power unit? - when I was conducting a cold start, the external power unit was very close to the left wing. It disappeared when I’d finished the cold start and began taxiing. Could it please be removed when external power is disabled? I was looking for a binding to remove it, not realising that it was automatic, as I was worrying about crashing into it - great to see so many analogue axis available for binding. I was a bit confused about it the naming, ie the use of the […]. Could that be updated to something more meaningful?
  12. Love it. Spent a couple of hours setting up my controls, conducted a cold start and went for a cruise around. Brilliant module, very very charismatic
  13. Did you request via the crew chief for external power to be enabled?
  14. As per the title. I'm aware of the current "areas of opportunity" that exist with ED and Razbam, so I was pleasantly surprised to see enhancements on the Falklands maps.
  15. Read the manual? ensure that your kneeboards are ready? Have a suitable map scenario in mind of where you fancy staring to fly it
  16. Agreed. After all, I still regularly fly for example the Huey and Harrier, both of which I’ve owned for 6+ years. I can’t think of another 6 year old game that I regularly use.
  17. How many people actually buy modules at full price? Most of mine were either on one of the regular sales, or at pre-release discount. I have nearly everyone module and the only ones I remember paying full price for were the Huey and Nevada. The Huey was because it was my first module and I didn’t know about the regular sales. NTTR was for release 2.0.
  18. I found this and thought that it was a potentially really useful asset: https://www.ww2.dk/lwairfields.html
      • 2
      • Like
      • Thanks
  19. Just to be sure, when you press the fire button, are you keeping it held down, as against just a rapid click?
  20. I believe that the incompatibility issue (reversed VR axis) is now fixed
  21. Probably easiest to read online material: https://en.m.wikipedia.org/wiki/AN/APG-68
  22. I’d love to see both a Ka27 and a Seaking
  23. So far, just one issue. In general, good performance, fairly comparable to Caucasus. This is using a Quest Pro with DFR. Ground textures low, medium draw distance. Have flown the Mig 19, Mig 21 and Viggen at a variety of altitudes. Above 1000', pretty much always 72fps. In the Viggen and on the deck, generally in the 60s. Near the base, a little lower. The issue was towards the end of a 2 hour session in the Migs, when the frame rate dropped to sub 30 fps. The felt like a VRAM memory leak. I changed the Hangar to "black" and I haven't seen another re-occurence as yet. The Hangar is a single file that you drop into the main DCS directory, such that on first loading DCS, you don't see a hangar, it's just empty black space. Apparently it saves VRAM memory.
  24. That looks like ED were obliged to release Kola on a certain date, and pushed it out with a simple hotfix, whilst saving the real update for 2 weeks
  25. Like this? If so, what’s the question?
×
×
  • Create New...