Jump to content

Coug4r

Members
  • Posts

    566
  • Joined

  • Last visited

Everything posted by Coug4r

  1. Were the latest updates supposed to have this fix yet? I'm seeing an fps of roughly 80-120 depending on the mission but the max fps is set to 30 in the autoexec.cfg.
  2. And thank you for the fix!
  3. Tested on Caucasus, PG and NTTR and the results are the same so it's not a map issue.
  4. Seeing quite a bit of increase in the dedicated server CPU usage (DCS core), it used to be 30-40% before the update and now it's like 85-100%. Anyone else seeing this?
  5. You can also try set a FOV in the viewport config in your monitor setup file. 1.0 is the default value >1.0 is FOV+/zoom out <1.0 is FOV-/zoom in This is what i'm using atm: Viewports = { Center = { x = 1080-250; y = 0; width = 2560+500; height = 1440; [color=Red] FOV = 1.30; [/color] aspect = 2.1944444444444444; }, }
  6. Maybe this was fixed in the meantime but this doesn't seem to work anymore. OB v2.5.4.28090
  7. You may wanna try https://fly.elise-ng.net/immersive-lcd-pro/ It used to have a trial period (after there were some free RC versions) so maybe give it a shot.
  8. BUMP!?!
  9. Got the exact same thing, also visible in daylight. The flashing appears to be a light that comes on when the probe is fully deployed. The light seems to be in the aircraft but it's not the floodlight, it's further in the back but also on the right. It's even reflecting on the probe itself and the flickering is also visible from an outside view. The only way to get rid of the flickering is to disable all lights by pressing L. Perhaps it's an AMD issue, not everyone has this. Using latest drivers though.
  10. Modelviewer2 is pretty buggy (for me at least), i've seen my livery already get mixed up with other liveries (didn't happen in MV1), you should be able to save your session and auto load it the next time you fire up MV2 but that doesn't work. Loading a livery like you could do from the autoexec for MV1 doesn't work. I'd stick with MV1 if you have that opion.
  11. Nope, not fixed. Maybe we should connect a 2nd mouse :)
  12. Thought that was the old bug which got fixed. Consider this a confirmation of the issue :)
  13. When i tried to change my payload manually i noticed the dropdown menus are in the wrong spot. As soon as i try to move my mouse cursor over the bomb/rocket/etc menu, the menu disappears so i can't change the loadout while in the pit. Repair made no difference, can't use cursor keys either. Not running DCS in full screen (for SRS). Using Res: 5760x1080, viewport 3000x1080. The menu appears on the right side of the center monitor. It also happens in the ME:
  14. With the map view option set to 'Map only' and you press Ctrl-F10 inflight the map view will still zoom and position to your location on the map. That's a bit of a cheat and basicly the same as the 'My A/C' option. Any navigation related mission is basicly shot to pieces with this 'cheat', would be nice to see this fixed!
  15. Yeah got the same issue.
  16. Hi all, new user.. good stuff! I've created an app which sends button presses/releases for the UFC in the Hornet, all peachy and works like a charm but when i look at the dcs-bios.log i get tons of these messages when i'm in the Hornet: value -755.000000 is too small for address 29908 mask 65535 value -4.000000 is too small for address 29910 mask 65535 value 1900515.000000 is too large for address 29934 mask 65535 value -105543.000000 is too small for address 29936 mask 65535 value -485.000000 is too small for address 29908 mask 65535 value -8.000000 is too small for address 29910 mask 65535 value -5863.000000 is too small for address 29916 mask 65535 value 1900515.000000 is too large for address 29934 mask 65535 value -633020.000000 is too small for address 29936 mask 65535 value -303.000000 is too small for address 29908 mask 65535 value -10.000000 is too small for address 29910 mask 65535 value -5979.000000 is too small for address 29916 mask 65535 value 1900515.000000 is too large for address 29934 mask 65535 value -815560.000000 is too small for address 29936 mask 65535 There's nothing sending data to DCS(bios), no app/application running. When getting into the pit of the Viggen and the P-51 i see the same messages. Not in the F-15, Harrier, L-39 e.g. Is this a profile bug?
  17. Yeah the side monitors don't clear but the map is fine now, it's usable this way. (side images are white because of reshade)
  18. In attached mission an AI F-14 takes off from the carrier runway, once airborne it seems to have 2 alternating positions (check map). Only tested with the F-14 AI, also happens when spawning the aircraft from script. This started today after todays OB update. F-14AI_FromCarrierRunwayTest1-1.miz
  19. My buttons are partially gone too, others have reported the same issues.
  20. Just to make sure, are we supposed to use 'parking' or 'parking_id' for the retrieved Term_Index?
  21. This might get you going: http://multimonitorcomputer.com/best-8-monitor-video-cards.php Some cheaper cards can already have up to 5 outputs. If you could use 2 of those you could already go up to 10 monitors.
  22. I know i've located the issue but can't remember if i fixed it, been a while. Maybe you can check if an update is available for VPC, alternatively you could disable the mod or just not notice the bug or get an AMD video card. For some reason this bug would only appear on NVidia cards.
×
×
  • Create New...