Jump to content

Avernus

Members
  • Content Count

    73
  • Joined

  • Last visited

About Avernus

  • Rank
    Junior Member
  1. When you use the target software, the Hotas is combined into one device. As such DCSW will see this as new/other hardware, and use preset defaults as always. Due to certain limitations with DInput, you will not be able to use every button as defined by Microsoft due to there being to many DInput buttons for the API to handle. You may require some of the Hotas buttons to be keyboard inputs used by target instead. As for the zoom slider, re-check the Axes panel in DCSW with the combined Hotas active via Target program. If you run the Hotas wit
  2. If one opens the canopy with MiG 21Bis, flood lighting enabled, look to the left, away from the glass. Flickering gone? sorta?
  3. For me with NV or ATI It is the screen space reflections. Any light reflected back at the canopy may produce a corona effect. This is where i see heavy flickering. Complete showstopper.
  4. Try the Mig-21Bis again. Enable the red cockpit lighting under the warning panel. That's all it takes for me.
  5. Yes, I have this problem as well. The red cockpit lighting responsible for screen space reflections on the canopy seem to trigger this, using the periscope mirror only makes it worse. That being said, i was only able to reproduce this issue on my Radeon. Same test with Geforce card did not seem to have the issue.
  6. Provided are two files modified to 110 degrees fov for most aircraft. This will pass IC check :thumbup: Spitfire, C101, Gazelle ,Mirage, Yak have not been added as i do not currently own them. Place these files in DCSW/Config/View and overwrite. Always make a backup first!. Reference Server.lua, CameraViewAngleLimits for min/max fov. SnapViewsDefault.lua Index [13] for initial Fov. If anyone is willing to provide the /entry/views file for those aircraft listed above, I will gladly add them to the file and upload them here. Please be aware that ED has a rather harsh max limi
  7. Ah, just a random blemish of sorts then. Thanks for the support guys, well met. Those new textures look outstanding by the way!
  8. Hi guys. This one has been around for a while. If the fuel pump switch is enabled/disabled in a short enough time, the sound effects will loop continuously slightly out of phase timing with each other. Is this correct behaviour?
  9. Hi guys, I've noticed a rather nasty issue with the Movenpick hotel. Grid 40R CN 09886 70805 As soon as the window frame texture is drawn (LOD) the FPS may drop by 50% or more. CPU usage spikes, GPU usage drops. Moving the camera one step away (LOD) so that the window frame texture phases out, the FPS/CPU usage returns to normal. Texture and Preload settings were set to lowest to keep Vram in check however this issue remained. If i use Alt-Enter a few times, this problem goes away and "comes good" but not always. It should be worth noting that this issue only s
  10. Hi guys, just a quick bug to report for the nevada map. The parking space E11 at Nellis appears to have some issue with spawning the aircraft on the ground. The aircraft will spawn in the air at low altitude, Even if set to ground start hot/cold as selected in the ME.
  11. Which weapon are you attempting to use here? The M64 works using auto mode as intended.
  12. I've switched from my previous configuration of 3x1L to a single 4k at 110' Fov. The sim hasn't locked up since... unless provoked with deliberate intention! And it Will still completely freeze up if you want to touch it there :) Fov is restricted @ 140' I believe this limit is imposed so that ED may isolate the issue more clearly. To that end.. it would a good idea to remove this limit in a future update so that other multi-screen configs do not suffer. During testing @ 140' Fov on 3x1L or 1x4k the sim still locked up when provoked. My previous config re
  13. Bad news indeed. Unfortunately locking the fov down like this means that i'll likely have to throw away these 3 screens and go out and get a 4k a bit earlier than expected. I'm sure that'l have it's own set of problems too. GJ ED :( Let me know if you need details on how to lock the fov down to lower levels.
  14. Horrible results on my end as well. Using the method i posted above resulted in the usual complete freeze up within 2 minutes requiring task manager to kill dcs.exe. One thing i noted however is that the FOV appears to be restricted to 140 degrees horizontal regardless of what rctrl+enter status tells you. This is not good news for certain multi-screen configurations! The Fov can still be restricted below 140 without limiting your axis with a screw however. :thumbup:
×
×
  • Create New...