huppel

Hi, I was experiencing some FPS problems (please see my specs and settings below). Normally my FPS was quite okay (around 60) but in some missions I noticed quite some stuttering and low and jumping FPS numbers. For example in the enemy within campaign mission nr. 2 FPS dropped at start already to < 20 and if I just started the "create fast mission" (A10C, all defaults besides summer, clear and 12:00) then FPS < 10. As I could not understand this (GPU and CPU's seemed not even being used to the max) I started investigating. After disabling hyperthreading suddenly the stutters were gone, FPS numbers more stable and higher in the missions I had problems with. For example in the "create fast mission" I now get around 60 FPS stable. When doing a search on the forum I could not find much info on this. Am I correct and does DCS not like hyperthreading or is that just on my system? One question, I'm thinking on upgrading to a 3440 x 1440 monitor. Would that be doable with my system? Is there a big performance drop when coming from a 1920x1080 monitor? My system: I7-5930K (running @4,6), 16Gb memory, GTX 980 (overclocked) settings: all high except - vis range: ultra - civ traffic: medium - 1920x1080 - res. cockpit dis: 1024 - MSAA: 16Q - HDR: On - Depth o f: Off - Lens effect: dirt + flare - clutter/bushes: 0 (I don't like the effect when flying helo's) - tree visibility: 15990 - preload radius: max - anisothropic: 16x - Flat shaddows: On Best, Marcel

Sorry, I indeed refered to the initial point button on the PVI-800. I read the desciptions in the manual. Indeed there can only be one, you should be able to set it in the mission editor and I found out it can be changed from the PVI-800 itself. It indeed must have something to do with the initial point for an attack but what I don't understand is what purpose it has when turned it on. You can turn it on together with a waypoint or target point, but when should I turn this on and what will happen? Best, Huppel

Hi, I'm learning the Ka-50 and have a hard time understanding the init point button on the PVI-800. I searched the forum but still do not completly understand it's use. I see that I can select it next (together, both lights are on) to a waypoint or target point and there can be only one init point. I cannot update it with the position of the Shkval but I figured out I can set it to the position of an existing waypoint or target point in edit mode. Can somebody perhaps explain what it is meant for and how it should be used? Regards, Huppel

Okay found it, my mistake. I changed the helicopters country to the Netherlands (blue) while the airport was still 'red' -> no respone from ground crew... I thought I used the same mission in 1.2 but there it was still a Russian helicopter.

I'm not trying to talk to ATC but to ground crew (to establish ground power) so no need to set a frequency as far as I'm aware. I tried the same mission and doing exactly the same procedure in < 1.5 does give a ground crew response. I'm doing this on an airfield, not a FARP btw. But if it does work for others I must be missing something so I'll try again.

Hi, Am I missing something or is the ground crew not working correctly in 1.5? I tried with door open en closed (engines off, batteries on, inverter on, intercom power on and mic set for intercom) and I get no respone. Best, Marcel

Had this happening a lot in < 1.5. Hoped the new game engine would solve this but it happened twice to me already when running 1.5. I'm using a GTX670 btw. Funny thing it only happens with DCS, no other game. Now planning to upgrade to a new videocard.

Hi, For those of you who might be interested I uploaded a (rather extensive) DCS A10C VoiceAttack profile: http://lockon.co.uk/en/files/1459461/ For the ATC commands the static ATC mod must be installed (http://www.digitalcombatsimulator.com/en/files/1270182/). A file describing the available commands is included. Best, Huppel

Thanks!

Hi, Indeed the link seems dead and I cannot find them elsewhere. I would like to receive a copy of the mods, please, if possible. Thanks, Huppel

To give you an update I managed to get rid of the frequent resets of the GPU. I 'underclocked' the videcard until the problem went away. Is it normal that one must 'underclock' a videocard ot get it stable (at least for DCS)? The "Voltage Limit" and "Overclock voltage limit" are still triggered though. Is this normal and what does this mean? Regards, Marcel

Hi, I also have trouble running this application. The problem reported in the windows event log is (windows 8.1, 64 bit, .net 4.5 installed): Application: KneeboardBuilder.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Reflection.TargetInvocationException Stack: at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri) at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri) at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean) at System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext) at System.Windows.Application.LoadComponent(System.Uri, Boolean) at System.Windows.Application.DoStartup() at System.Windows.Application.<.ctor>b__1(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Application.RunInternal(System.Windows.Window) at System.Windows.Application.Run() at KneeboardBuilder.App.Main() Does somebody perhaps have a clue why it is failing? Some more info: I unzipped again and this time did not choose to install the update (so I'm at version 1.4.1.0 now) and now it does work. Thanks, Marcel

New update: tried also to lock my fps (set it to 30). It didn't help (although it reduced the GPU temperature with about 10 degrees) I had a look at the core voltage and right before the driver crash both the voltage limit and the OC voltage limit were triggered. Note I have not overclocked the card at all. What does this exactly mean and should I change something to the GPU voltage or does it mean that something is wrong with the card? Regards, Marcel

Hi, To update you on what I've tried in the mean time: I went back to driver version 331.82 and set pci express setting to Gen 2 (it was indeed in auto and I'm running windows 8.1). Both did not help. About the voltage, I can easily change that for my card using MSI afterburner (using it already to monitor the card and set the fan speed). I didn't dare touching the voltage yet, is there a change I ruin my card playing with that? Thanks for all your tips, Marcel

Hi, I am also troubled by the video driver crash problem more people seem to suffer from. I'm running on a MSI GTX 670 and somewhere within playing for half an hour the screen goes black. Sometimes the driver resets itself but most of the times I have to reboot my computer. Most of the times there is nothing to be found in the windows event logger and also nothing in the DCS log files. I monitored the temperature of my GPU but that does not seem to be the problem, it does not het hotter than about 70 degrees and sometimes it happens imedialtely after the game starts. I already tried everything I could find in this forum (complete reinstall, set some windows timeout registry key, changed some settings). I'm now trying to revert back to older drivers. I tried the 377.88 driver but that didn't solve the problem. Is there anything else I could try (or there a certain driver version that is gueranteed to work?)? Thanks, Marcel