speed-of-heat

i just force everything to 2 pixels , its not perfect .. but compromises

same, though i am also using DLSS or visa versa Antialiasing always comes with disadvantages ... alas but DLAA comes with the least number of disadvantages for me ... what irritates one person another doesn't notice ...

It is possible to get into a deadly embrace with the Taxi at the beginning between you and Blade, if you signal to Taxi at the same time Blade moves off both Directors tell you to stop and it never resolves ( you need to wait until Blade has started Taxing before you request to taxi).

So... I sort of had this bug a few different ways having gone through the prescribed started up procedure: - the first time, was when i was using VIACOM and Voice attack, and forgot that the Salute trigger does not work when using VIACOM (dumb me) - the second time, i used a mapped button for a salute, but I waited, to move until i had fully finished my ground checks, a little while after the Graphic shows the Yellow shirt saying ready to taxi... and Olive gets hung up in the same way - similarly, if you don't taxi until Olive is taxing her and the S3 and you all seem to end up in a deadlock ... - the only reliable way to ensure that it all works, that i can see is that as soon as you get the yellow shirt image, start your taxi request, then it all seems to go fine this sort of clashes with a note in the briefing document which implies you should wait for Olive to take off before you Taxi... side note 1 (in all cases the Yellow shirt image is with you right up until just after the cat launch) which is a bit ... "irritating" visually, as the image blocks sight to taxi directors side note 2 we seem to wait a long time for the launch of Switchblade, with power down except battery ( because we don't permission from the ground crew because they are dealing with the Buccaneers) so no power to comms ... but we still get the Switch Blade comms but not the AirBoss comms to Switchblade..

It takes a while for content to come for a map… it requires a number of factors not least of which is a campaign creator to take an interest…

that's just strange ... no wonder i couldn't work out what was wrong if it was hardware specific .. glad you got it "working"

had the same problem today

Have you ever fiddled with views.lua ? Any mods installed?

Wouldn’t the consequence of this be a double button press, once by vr hands once by your physical hand leading to an unpredictable outcome, like if you reached for an osb you would press it twice…

bind a button to Center VR headset? it's NumPad 5 by default.

it apparently the number 1 that collides... i guess its the 1.1,jpg

Ok I found the issue, it’s a collision between where the mission designer places their knee board (ala 1.png) and where Viacom places its kneeboards… not your fault at all, not Viacom’s either just a collision in an undefined name space.

i

OK, there is a page that has the JTAC information on it ? Is that an in game feature if so a) sorry and b) learn something new

Hi @Badger633, I'm in the process of replaying SH2, and I see you have added in a JTAC page? is there a way to disable that? as it seems to interfere with Vaicom's kneeboard function ?

Try a salute? Remember the super carrier changed its process with deck crew, salute to start engines, salute when ready to move

Damn , I did tell him to uninstall the a4 mod, thanks for working the problem

The guy who taught you how to document a bug… well done

so close; now add a track and *then* you have a well-documented bug... However, before you do, try uninstalling the A-4EC mod (preferably all mods) and seeing if the speed differential is replicated... like all mods can and DO have very odd impacts; i have seen the A4E-C mod impact other aircraft AI in campaign missions for example ... so start with a clean install of DCS (do a slow repair/ or uninstall your mods via a mod manager) ... and show the bug on a *track file*... then and only then do you have a *well-documented* bug with the Forestal... Stop talking about the A-4E-C because nobody is listening, to a bug that impacts an unofficial mod (how is this so difficult to understand) show it with a native in game S3B and you have a different proposition, albeit unless the S3 goes for a swim then it is less likely to hit the top of a priority list.

you don't need to launch the hornet in AB if the weight is low enough ... from memory 44000lbs or less

nobody in particular, but the only evidence you have shown that i can see is with the A4E,, show a track with an F/A-18 or a Tomcat and you have yourself a different argument... my 0.02GBP

also with the FPS counter, it says CPU limited ... what it means is not really that the CPU is limited; rather DCS just can't use any more CPU processing power... which is different, it will likely be the case that some CPU cores will still not be fully utilised, faster individual core performance will help some... but ultimately you will as @Hiob says be limited by something... a couple of things that *WONT* change the CPU limited status, is making sure that DCS does not use core 0/1 (which is what windows uses by default) and the same with other DCS performance related processes like your VR stack or voice attack , beyond that other than a CPU with faster cores not much can be done by us

Tne answer is a little technical ...

I think @SUNTSAG has something like that in his mossie campaign?