Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Fjordmonkey

  1. Even our old AM/BM's with the AFLCC moves the stabs/flightcontrols way faster than they currently do in DCS, and the RNoAF AM/BM's were never updated to DFLCC. Also, from what I remember from my days on the flightline, even the old OCU-birds were quite violent in moving the FLCS during BIT. Glad to see it sped up in the next patch, though.
  2. Will this be an option? For those that don't know what this is, it can be seen used here on a Luftwaffe F-4F. Instead of using a huffer-cart to supply compressed air for engine-start, they use a cartridge-system that inject a jet of high-pressure gas into the engine to spin it up to speed for ignition.
  3. I just went with the latest. No issues with it.
  4. Just make sure your drivers are updated, and you shouldn't have any issues.
  5. Remember: I am under no obligation to make sense to you.

  6. Strangely enough I don't have that issue at all, using OpenTrack as an endpoint for SmoothTrack running on an iPad above my monitors. Will check more on this.
  7. Remember that if you're on an AMD-CPU, install the latest chipset-drivers, install KB5006746, and set a Ryzen powerplan in the controlpanel. That solves the early issues people had with Win11 on AMD. Running on the RTM of Win11 now. Zero issues what so ever, small increase in fps (3-5fps average). Your mileage may vary. Ryzen 5 3600, 32Gb RAM on a ASUS TUF B450M mobo. 1660Super 6Gb GPU.
  8. KB5006746 dropped for me today, which fixes the L3-cache latency-issues for AMD-CPU's. Haven't tested things with DCS yet but will do so a bit later today.
  9. An update on my end: I ended up just wiping the entire system due to the framerate-issues in DCS (yes, I AM that level of maniac) and reinstalled the at-the-time latest Beta-build from USB. Since that time I've been happily running Win 11 without any issues what so ever, and even gained 3-7 fps in DCS overall. Usually sitting at between 45 and 50 on the ground in Caucasus and PG, about 40 on the ground on Syria. I don't run VR, so cannot comment at all on how that behaves. Specs: AMD Ryzen 5 3600 on a ASUS TUF B450M-PRO mobo, 32Gb G.Skill Ripjaws V DDR4 3200Mhz RAM. DCS installed on its own 512Gb m.2 NVME SSD, system running on a 256Gb m.2 NVME. ASUS GeForce 1660 Super 6Gb Vidcard, latest drivers. 32" QHD-monitor with a 27" QHD as secondary. No overclocking of any kind. Have had zero issues with other games (Diablo III, Aliens Fireteam Elite, Battletech, Outriders, Elite Dangerous, Star Citizen etc). Haven't done any direct comparisons between framerates from Win10 to WIn11 on any except DCS, mostly since I haven't noticed any issues in the first place. Wiped my workflaptop (HP ZBook 14u G5) and installed the release-build of Win11 on it. Zero issues with any of the workloads I have on it. Take it for what it's worth, but so far I'd have to say that the main differences for me with Win11 are all visual.
  10. I'd say that unless you have a very specific reason to run what's basically a Beta-OS on your computer with all which that entails: wait with installing it until it's released mainstream into the update-channel. Since I'm a mental muppet with less sense than your average broom and a glutton for punishment to boot, I'm running it everywhere I can, even on my daily driver at work
  11. Quick update on my own post: I ended up just wiping the system and installing Win11 from a USB-stick. Couldn't get DCS to function properly before I did, but after a reinstall it works just fine. Got the same or slightly higher framerates with the same settings I used on Win 10, no issues with for example SRS, OpenTrack or other applications I use with DCS.
  12. I've been spending my workday doing something productive so far, namely researching Win11 and framerate-issues in various games. There's been multiple people that have had lower framerates in various games while running Win11. Some have reported that changing/lowering the mouse polling-frequency from 1000Hz helps a lot, plus not running things in Borderless Fullscreen or with VSync on. Another option is to disable the "Send Optional Diagnostics Data" option under Privacy & Security -> Diagnostics & Feedback, so I'll have a gander at those when I get home and report back. If that doesn't work, I'll try nuking the box and reinstalling Win11 from an USB'ed ISO and see if that helps. There's rumors of a new Dev-build coming today and will test that too if it drops before I faceslam my pillow.
  13. Win11 basically nuked my framerates. Went from 45-55 on Cauc/PG and about 40 on Syria to 15-16 on all of them. Game mode is off, GPU accelleration is off. Zooming in on one of the Harrier MPCDs basically slams my framerates down into the low single digits. Will do some testing later today to see if I have the same issues in for example the Viper. If so, it'll be back to Win10 for me.
  14. I'm running Win11 now, and have two issues. The first is a massive FPS-hit on all maps (sitting at 16-20 where I sat at 45-55 while on Win10), and the second is that I can't even load Marianas at all. Doing a driverupdate on the Vidcard now to see if it helps. Edit: Driverupdate for the GTX1660Super didn't help, but I did manage to get into Marianas through the Mission Editor. Fast Mission goes up to 9% before it just poofs out of existence. The game itself doesn't crash, however. Will do some more testing, but taking that large an FPS-hit is a no-go for me. If I can't solve it I'm reverting back to Win10.
  15. Was lucky enough to server at 331/334 during my mandatory year in the RNoAF, so it was an obvious choice Already running DCS BIOS for the Logitech Flight-panel I have, so it'll be the way I'm going. Hoping to base everything off an Arduino Mega, since that'll give me more than enough room to expand should I need it.
  16. A silly question: What have people plannet for displays in the UFC? I'm in the process of looking into what I'd have to get to build one, but the prospect of the displays and the inputs they'll require is daunting. Especially since I was thinking of making a UPD as well, which takes 5 buttons and 5 displays. That's a wee bit of inputs needed.
  17. I actually figured out what I was doing wrong (i.e. I was being an idiot again and didn't RTFM properly). Two main problems: Not testing that the export actually worked (wrong syntax in export.lua, with a ' that snuck in) through the ConREF-tool, and secondly not reading the part where I have to set up the Export.lua correctly, start a mission and then check that DCS actually exports things before I can actually program the buttons from within DCSFlightPanels. So yep, a clear case of PIFOS/PEBCAK. Right now I'm looking at getting the landing-light status to show up on the panel. Can be programmed through DCS BIOS, from what I was told on the discord.
  18. I get much the same error with the same panel, although with an AV8B-profile. 24.03.2021 10:27:27 version : 1.0.324.6091 System.NullReferenceException Objektreferanse er ikke satt til en objektforekomst. ved NonVisuals.ProfileHandler.set_Profile(DCSFPProfile value) ved NonVisuals.ProfileHandler.NewProfile() ved DCSFlightpanels.MainWindow.CreateNewProfile() ved DCSFlightpanels.MainWindow.WindowLoaded(Object sender, RoutedEventArgs e) 24.03.2021 10:27:16 version : 1.0.324.6091 System.NullReferenceException Objektreferanse er ikke satt til en objektforekomst. ved NonVisuals.ProfileHandler.SetEmulationModeFlag() ved NonVisuals.ProfileHandler.set_Profile(DCSFPProfile value) ved NonVisuals.ProfileHandler.LoadProfile(String filename, IHardwareConflictResolver hardwareConflictResolver) Doesn't matter if I run DCSFP in Admin-mode or not. I can clear the errors by deleting the DCSFlightpanels-folder in %appdata%\Local, but as soon as I load a profile it's back.
  19. I did some testing, and ONLY the Harrier has this issue. I tested the Hornet, Viper, F5, A-10C II and Viggen. Only the Harrier has the issue, and it gets progressively worse as you zoom out. To other aircraft you basically look like Santa Claus. It's a minor issue all in all, but an issue either way. No idea whether this is an ED-specific issue or an RB-issue.
  20. Key words are trim and small stick-movements. I've found that I also have to adjust the nozzle-angle slightly once I enter a hover. Oh, and practice. A LOT of practice.
  21. Understandable :) I'll continue my search :D
  22. Thanks, derammo :) I'll take any hints on things that can do the same as IRIS and that works with Helios eagerly :D
  23. One question I've been trying to get info on: Can I use Helios to export viewports/MPCD's to a networked unit with a touchscreen, such as the Surface Pro 4 I have sitting collecting dust? I know there was a system called IRIS that was used earlier, but that seems to be discontinued.
  • Create New...