Avernus

Which weapon are you attempting to use here? The M64 works using auto mode as intended.

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 required 150 at the maximum endpoint which always resulted in a hard freeze if i loaded a FW-190 in any cold start scenario just by panning the camera around for a few minutes or less. Other aircraft have the same issue to lesser or varying intensity.

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.

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:

Where are we on a fix for this ED? If testers/developers are having a hard time reproducing this horror of a bug. Here are a few simple steps. Edit the server.lua and extend the max FOV to 150 for Fw-190. Select the Fw-190 cold start quick mission. Use the mouse to slew the camera around to all endpoints for a few minutes. The sim will freeze up in a few minutes of constant slewing. All other aircraft i've tested across all three maps have the same issue. The only thing that changes is the time it takes.

It has been some time indeed. Something happened to my account on steam year ago, which has recently occurred again, resulting in a complete removal of my entire list of players. I've contacted Valve support who in turn reset the account. I can now re-add those players, but only once they've attempted to add me first (which always seems to generate some error message). Try add me once more when/if you have the time, ill have to poke it with a stick to get it working properly though. Is Rotorwash still alive too ? :music_whistling:

Yeah, this bug can make things a little frustrating for mission makers since 1.5. Even using combined arms instead of ME waypoints leads to some odd AI behaviour at the worst of times. However due to the horrid freeze issue with 2.x i'm not sure how anyone can actually test this sim and come up with solutions or workarounds. edit: hi there MD

This is still an issue for me with the latest update. Quite easy to reproduce as well. Load up 'FW-190 Cold start-Normandy' and slew the view in cockpit quickly for a while, after some time it will freeze the sim. For me the RAM usage drops slightly, and the graphics process is updated only once every 5 seconds resulting in a DCS slash screen at intervals. Occurs with either 3 or 1 screen setup. Higher settings, Fov, System load and user device input(slewing cockpit view) appear to shorten the time it would take to resolve to a complete freeze.

Indeed, I've had this issue since the 2.0 alpha regardless of forward or deferred rendering. The issue is easily reproducible by loading up 'free flight normandy' with the fw-190 then slewing/zooming the view with the mouse like a spaz. The sim will start to hitch and just give up at some point within minutes or less. GPU usage drops sharply. CPU usage spikes on one thread, but continues consistent load on the other. RAM usage continuously loads, unloads then repeats. DCS shows the splash screen at intervals. I have no crash logs to report in this case, as the sim never truly crashes. I am running a 3x1L setup at 150' FOV @6048x1080 with GUI centered. However testing the sim @1920 with surround disabled 'may' take longer to resolve the same conclusion, however this may just be a placebo effect.

Problem : Fov is locked - Battle of Sukhumi, potentially others.

Mr wolf, as the mission is being updated. Please take care to remove that pesky views folder from the archive. Note: this must be checked on each update, Where 'Prepare Mission' is used. Leaving this file will enforce user options such as field of view rendering the server unplayable for some. Thanks again guys.

Use the brakes! That is, holding the wheelbrake key will ask the ACS to relax, allowing your aircraft to perform a brake harder, or sooner.. whichever comes first!

There's been a few posts since the release of 1.5 pertaining to inputs clashing with performance.. The mouse camera movement is one that i am afflicted with. As Snaut noted though, some of the newer mice are configured for 500/1000hz rate naturally. Set this to 125hz and the problem moves aside. The overhead of 1000hz never bothered dcs 1.2, regardless how high/low the framerate got.

Is it possible to remove the /view folder from the mission please? When this file is present it overrides Fov for multi-screen users Cheers.

You're welcome, The fish eye effect you describe has a little something to do with the fact we're using a flat surface x3 to emulate a 3d world, No real solution for this i'm affraid, perhaps curved screens? or projected holographics erh. :D This thread by PeterP explains a few of the variables here: https://forums.eagle.ru/showthread.php?t=96116 Limits_6DOF is where you would define how far you can pan using trackir This is where you could edit an aircraft that restricts complete freedom of camera movement in the cockpit (the old mig29 comes to mind here) Cockpitlocalpoint works with eyepoint to center the viewpoint and keep the 3d model aligned as viewed from the cockpit. (probly not wise to play with this one) Snapviewsdefault.lua Line #126 A10-C Index [13]=Cockpit This is where you would define the aircrafts default view position. for example a higher seat/viewpoint could potentially mean changing Y_trans to a positive number. Mess around with these and have fun.

Drack, try this Notepad++ //DCS/Config/Views\Server.lua --perform backup first The A-10C appears to use a common index for the view settings. Line #27 'Defaultfighterplayer' All aircraft using this index will be using these settings unless where specified. Line #80 has the information related to the A-10C. As you can see it refers to 'defaultfighterplayer' for any data not contained here, Data like 'CameraViewAngleLimits'. Add the missing data pertaining to Fov to the A-10C index. Or simply edit the referred data, In this case #29. :thumbup:

Hi guys, Just figured i'd chime in here with a workaround/fix for all aircraft currently using their own view.lua file. Here are two files with the Fov set to the original 110 for the MiG-21Bis. Simply copy the info from each file and add it to their respective DCS files. This should help single screen users to avoid having to tweak the zoom axis, as well as sort multi screen users as well. Just remember to copy the defaultsnapviews information for other aircraft usually located near the bottom of the views.lua file else the viewpoint maybe off center!. Snapviewsdefault.lua server.lua

Badhabbit, It might be worth taking the ram out and taking a good close look at the legs in the slot. I've had a fair few boards sent to me at a shop i worked at with some seriously tight ram slots. Customer installed additional ram/touched it/killed it apparently. No POST. Customers pc failed to POST with gpu and ram removed cpu installed. (usually they beep like mad!) However the atx leds near the 24 pin connector was signalling a reset. Upon closer inspection, One of the ram legs had crossed over and shorted with the leg next to it, halting the entire system in the process. @bitmaster Will the board post with just 4 pin atx? This sounds like vrm failure to me.

I'll chime in here as well, Not sure if it's related. I've been able to fly the 21 around a bit on 104th. For me it appears to be more forgiving if i load into another aircraft first, then switch to the 21. I remember the hawk having an issue where this could help, quite random. Once in the air, i switched radar from standby to on, i watched as the framerate dropped progressively to the single digits. flicking the switch a few more times seems to alleviate a little. (was about 20km S/E maykop very low). If i load up the 21 right away and go fly. switching the radar on will once more(randomly) cause fps to plummet, until it drowns the cpu out,gfx updates stop, sim stalls out, no crash error for me. Unfortunately, no DCS logs for me due to the nature of the crash. Specs however I7 950@4.4 (stock clock didn't help-tested) creative ZxR 12g ram gtx980 3 scrins 3x1L Thanks for all the support so far LN ;)

Outstanding!. Cobra, may i ask if there will be a slider akin to the mi8?

Hi guys. Got a big problem with various modules that have their own 'views' file/folder. It would appear the new Integrity check has blacklisted all field of view settings with the exception on the aircraft located within the server.lua I have attempted adding the info for the misc aircraft which give me more problems. Firstly the original file located in the aircrafts own folder must be renamed or moved, or changes have no effect. Secondly it seriously warps the cockpit view with the mig21 pitot tube sticking out of mid air for example, along with other unusual graphical mishaps. Other than throwing out 3 monitors in favor of a 4k, which i think is a bit extreme just for DCS. Please detail me alternatives Cheers

HI guys. Been forced offline due to Eagles new IC system. The files/folder pertaining to 'views.lua' is blacklisted as of then. I request an alternative method to remedy this horrid issue. This is also affecting the other modules with their own view.lua files within their own folder. Cheers

Hi guys, Just a quick one here. I've noticed that using the F10 view will send the map to the left-most screen, with the UI element still locked to central screen. If the view is not set to anything other than F10, the issue will affect the main menu GUI and background as well if you exit the sim somehow. Using UIMainView = Gui with centered resolution cfg.

Hi there. It would appear the Ka50 has a few keyboard conflicts present in the default configuration.. Problem only resolved with editing: DcsW/mods/aircraft/ka50/input/keyboard\default.lua --line 663 493 Cheers

I'm using a Logitech G700s mouse here. The software for most gaming mice should allow you to tweak DPI and Polling Rate independently. Check the website for your model and leech the tweakware if available. Hopefully the kind developers will squash this bug soon enough :smilewink: