I use my own custom profile, its the "standby instrument cluster" for the Hornet. Nothing fancy, just ADI, RWR (including viewport) and the VSI, Airspeed and altimeter gauge. I have knobs for the ADI CAGE/UNCAGE, Altimeter setting and RWR intensity, I use this in a 10' touchscreen. I want to emphazise that I've been using this like, forever, couple of years perhaps (with no issues of anykind) UNTIL I started using the Color Adjustment Effect for NVG effects. Problem is easy to replicate but requires patience as you simply need to fly around and take a look at the gauges, the more time it passes, the slower they get until I get a crash (out of memory) and DCS gives me the dxdiag dump option. I shared the crash log with ChatGPT and it basically said, this iis 99% an out of memory problem. Since it seems progressive, I assume this to be a slow memory leak in the Color Adjustment tool probably triggered SPECIFICALLY by the way I use it. (again, an assumption). See below for reproduction steps:
Steps to Reproduce the problem
Steps to reproduce the behaviour:
- Just open Helios Profile Editor
- Locate / Load your custom profile
- Add the color adjustment effect from special controls, doing it as follows to get NVG effect:
In appareance Leave BLUE, GREEN, RED at 1.0 in the color adjustments section
Now, go into the input, search for the action in the F/A-18C corresponding to Instrument Panel Lights and drag to both BLUE and RED (not green). Now, Blue and Red properties should have Lua selected for value and return (1.0 - TriggerValue) * 1 so that I can go from NO color to green.
So far, the steps above work 100% and initially everything will work 100%. Its after 10-15 minutes that you get the crash and slow down in the fluidty of the gauges until memory is exhausted.
By simply REMOVING the effect, everything is perfect and I get no crashes. its the effect what causes it.
The problem happened while using
Additional context
As I said, it might be the way I'm using the control what causes the issue, I'll be more than happy to help troubleshoot more but I'm not sure how can I provide aditional info to help identify the issue
I use my own custom profile, its the "standby instrument cluster" for the Hornet. Nothing fancy, just ADI, RWR (including viewport) and the VSI, Airspeed and altimeter gauge. I have knobs for the ADI CAGE/UNCAGE, Altimeter setting and RWR intensity, I use this in a 10' touchscreen. I want to emphazise that I've been using this like, forever, couple of years perhaps (with no issues of anykind) UNTIL I started using the Color Adjustment Effect for NVG effects. Problem is easy to replicate but requires patience as you simply need to fly around and take a look at the gauges, the more time it passes, the slower they get until I get a crash (out of memory) and DCS gives me the dxdiag dump option. I shared the crash log with ChatGPT and it basically said, this iis 99% an out of memory problem. Since it seems progressive, I assume this to be a slow memory leak in the Color Adjustment tool probably triggered SPECIFICALLY by the way I use it. (again, an assumption). See below for reproduction steps:
Steps to Reproduce the problem
Steps to reproduce the behaviour:
In appareance Leave BLUE, GREEN, RED at 1.0 in the color adjustments section
Now, go into the input, search for the action in the F/A-18C corresponding to Instrument Panel Lights and drag to both BLUE and RED (not green). Now, Blue and Red properties should have Lua selected for value and return (1.0 - TriggerValue) * 1 so that I can go from NO color to green.
So far, the steps above work 100% and initially everything will work 100%. Its after 10-15 minutes that you get the crash and slow down in the fluidty of the gauges until memory is exhausted.
By simply REMOVING the effect, everything is perfect and I get no crashes. its the effect what causes it.
The problem happened while using
Additional context
As I said, it might be the way I'm using the control what causes the issue, I'll be more than happy to help troubleshoot more but I'm not sure how can I provide aditional info to help identify the issue