shazam253

options to a_out_picture -- a_out_picture (fn, time to stay, clearview, delay, x [0..2], y [0..2], size, 0 original / 1 window

hello Ops. As you stated there is not outPicture with the trigger class, but you roughly elaborate on the arguments of above command? I'd like to create a timer based on numbers with particular fonds. At best, I could scale it to like 10% screen size and put it at the buttom left corner. thanks!

HIP reading out for changelings remarked it as well that the cargo buttons are missing for the other helos...

oh, and by the way. I think the autopilot should be named Karl!

Hey there, I love the module! Simple but rewarding. And most stuff I found to be 'bugs' was just me not reading the manual correctly I wish all DCS modules would come out like this! I completed the training missions in one go and the way they are made are just perfect. Concise. Not too much fuzz and long stories, just straight to the point. Often times I just skip the voice-over anyway, since I read a lot faster than I can listen ... Anyhow, not sure if its the right place to ask, but is there a way to transfer the _stare point_ of the UAS to the target point list without typing it out manually? good job!

I tried firing it in all three modes (DIR, COO, LOS). In DIR mode I tried designation through either radar (SEA1) or TGP (which is not on my default, but mentioned during the mission). However, the missiles just fly past the ship and explode mid-air. A turning point is also not given from within the mission and needs to be added manually during the briefing. I tried modifying the mission myself, to no avail. After manufacturing a simple test mission with just the JF-17, two C-802 AK and a single ship, everything worked fine and expected. I skipped the mission as there seem also some odd triggers in there as well related to rockets being fired. please fix the mission, or redo it. It seems there is some strange behavior with no apparent reason in my opinion. Even trying several modifications to the mission did not change this behavior.

I can't finish mission #7. As soon as I destroy the leaving vehicles, it states that the column vanished, mission fails and I get kicked after 15 seconds. Usually I'd fix that stuff myself, but the mission is locked...

Also from a less heated point: I fly a Georgian hammer mission today and I was able to make out ground units that were behind trees. After seeing the SPI in the HUD and then slewing the TGP to it, I only see trees. So in my opinion the dots shouldn't do this, but I can see that it requires more computional effort. As for spotting in general, I'm also using a G2 and have the issue that the dots are larger at a distance than when the airplane starts to be resolved. My proposed solution to this: don't make the dots larger than the aircraft. Also, the rough color should match, not just a dark dot. I can replicate the issue easily when going to F2 view and zooming out. At some point the aircraft becomes a larger big spot than it was when still resolved. Different LOD settings didn't have an effect. Interestingly enough, in the Syria hot start with the Apache, I can zoom out and see the Apache and F16s as large dots, while the static cargo aircraftb already disappeared.

Yep, I agree, we should test it out. I think in general, you want to limit the FPS though. It started somewhere that if you're CPU bound that DLSS will not be off much help. With allowance for unlimited FPS you'll likely end up CPU bound at some point. So limiting it will likely also help with stutters, as you maintain some overhead for trickier scenes. BTW, with a 4090 limited to 50 FPS are rarely dropped below that limit in any scenario. However, my science will have to wait till next week, when I'm back home ^^

I wasn't able to try out it yet, but for those experiencing reduction in FPS, stutters and such: I would recommend to do a slow repair of your DCS install and disable any community mods. If that still fails, move your save game folder and start fresh. If it helps, gradually put the old pieces back to see where it breaks. Potentially this will also help the devs, as you uncover where it is coming from.

interesting. but has it been fixed? If it were only 2 mirages, then you could handle them with the PL10s, but four is a bit too tricky, even if you load the plane up with 4 PL10s...

Awesome, thanks!

Sorry for digging out the old topic, but wouldn't it be possible to put it as a script in the user files, instead of going to overwrite it every update?

Sorry. Yeah specs 7950x3d with RAM at 6 GHz and CL 32. Graphics card is a 4090. Before the bios update, I didn't use XMP/DOCP and RAM was at 4.2 GHz and CL 40. I fly DCS in VR with a G2, but currently feel I'm GPU bound according to oopenxr-toolki. so I use 70-75% of the resolution with FSR enabled and medium visibility to practically always stay below 11ms frame time. CPU frame time is somewhere between 4-9 ms depending on the scenario. But I found maps like Mariana, Normandy and Syria quite demanding in scenery rich areas. If it were Caucusus only, I would go 85% resolution and high visibility. Then again, no hard science, I just took off with the F16 bunch of times from the Mariana got start map to tune out my settings. I wonder if DLSS will be better performing than the FSR tweak from openxr-toolkit. At 85% resolution I don't see a picture degradation, but at 70% it's noticable.

Short remark, after the stable BIOS update came out for the ASUS TUF x670e plus, I decided to give DOCP tweaked as well as PBO in enhanced mode level 2. In the 3D Mark, I managed to get 9% more, 8.7% are from the DOCP tweaked - it ramped my RAM from 4.2 to 6 Ghz. Interestingly enough, the graphic score went up by 5% itself, and the CPU score by 20%. I know its not DCS, but I'd say 'doing the OC' will be difficult to measure, but I would assume somewhere between 3-5%. I guess you should ensure proper cooling, all my components stayed below 80 degrees while using an 240mm AIO watercooler for the CPU.