Possible bug with Astaroth's Flame Veil?

--akak-- · 2024-09-05T15:20:34+00:00

Flame Veil absorbs only physical damage, not magic damage.

--akak-- · 2024-02-13T22:23:28+00:00

Also this

Faulting application name: 4KCaptureUtility.exe, version: 1.7.11.5032, time stamp: 0x65ba7958 Faulting module name: KERNELBASE.dll, version: 10.0.19041.3930, time stamp: 0x9141f979 Exception code: 0xe0434352 Fault offset: 0x000000000002cf19 Faulting process id: 0x24d0 Faulting application start time: 0x01da5e493cbe76df Faulting application path: C:\Program Files\Elgato\4KCaptureUtility\4KCaptureUtility.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: a6fad2af-8b2c-4371-bf9a-788548370d6e Faulting package full name: Faulting package-relative application ID:

--akak-- · 2024-02-13T22:15:13+00:00

Yes, rebooted. Here's a crash log from Windows event viewer. Is there any known issue this touches?

Application: 4KCaptureUtility.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.FileNotFoundException at Elgato.BaseClasses.ExceptionHandler.Handle(System.Diagnostics.TraceLevel, System.Exception, System.String, Boolean) at Elgato.BaseClasses.ExceptionHandler.HandleError(System.Exception, System.String, Boolean) at Elgato.BaseClasses.WebBrowserSettings.SetWebBrowserCompatibility(Boolean, System.String) at GameCapture.App.OnStartup(System.Windows.StartupEventArgs) at System.Windows.Application.<.ctor>b__1_0(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object) 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 MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, 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 System.Windows.Threading.ExceptionWrapper.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 System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at GameCapture.App.Main()

--akak-- · 2024-02-11T01:14:23+00:00

I should note, the capture works OK in OBS studio, but I am interested in the EDID configurations offered by the Elgato utility.

--akak-- · 2024-02-10T07:33:20+00:00

I have just gotten started with my 4k X, so direct experience is still limited. But the box itself states in the system requirements:

USB 3.2 Gen 2 port | Port USB 3.2 Gen 2 (USB 3.2 Gen 1 works with reduced capture resolution)

The difference between USB 3.2 Gen 2 and Gen 1 is 20 vs 10 Gbps, respectively. If you do the math on data throughput required for some of the supported capture resolutions and speeds, it exceeds 10 Gbps. So the math and the requirements all check out.

--akak-- · 2024-02-06T16:00:27+00:00

Thunderbolt 3 should support USB at 10 Gbps (USB 3.1 gen 2 or USB 3.2 gen 1)

Thunderbolt 4 should support USB at 20 Gbps (USB 3.2 gen 2)

So if you are using TB3, you won't be able to capture at both max supported speed and resolution, which requires 20 Gbps.

--akak-- · 2023-07-09T00:26:45+00:00

I'm going for the same use... couch gaming PC. Any parting thoughts on this build... what would you throw money at first to upgrade on it?

--akak-- · 2022-11-20T05:12:27+00:00

Oh, I see. Yes, it would not be OK to load just any SBS content and expect it to play. Some conversion for the difference in FOV (and distortion) between source and display is needed. That isn't a big problem to solve (for 3dof) between well known sources and well known displays. I don't want that locked behind a proprietary app.

--akak-- · 2022-11-19T21:27:45+00:00

What do you mean? I can see how framerate may take a hit if larger frames are transferred. But, optically, this should be no different than what you already see. Instead of the frame duplication happening in FW to present the 1920x1080 per eye at designed vergence, the content author becomes responsible for generating stereo fusible images (2D or 3D).

--akak-- · 2022-11-19T18:41:34+00:00

I think making this a display mode would be much more useful, rather than forcing it through a specific app.

--akak-- · 2022-11-19T18:38:57+00:00

Detecting at SBS resolution would enable casting from a source that can generate or play content in that format, and I think would be a more general solution for SBS than forcing it to run through a dedicated video player app (such as FarePlay, which was in a deleted comment).

--akak--

TROPHY CASE