bfr

Yeah, its a much firmer commitment now rather than a wish on his part.

Which is why I qualified the statement. If Windows self-management of page files is borked then fine, but I can't find evidence that it is. Also, i've never had a problem with it previously in the context of DCS prior to the last few days since the last OB release, nor have I seen any evidence this crash is memory related yet. And if tinkering with such things was necessary for DCS it'd be in the requirements and not what appears to be a lot of 'it worked for me' posts with little evidence to back up WHY it was necessary to take matters out of the OS's hands. And yes, the swap file in on my system SSD which is NVMe (and the majority of drives on my system are either NVMe or SATA SSD with a couple of mech drives which just hold data).

Ah yeah, the max is 3x on Windows 10/11 and not 1.5x as I said. Yeah, I hear you regarding it being a hail-mary and i'll maybe have a tinker later just to see. I'm just a bit wary of stuff in those areas as the practices have changed a bit with different versions and iterations of Windows (as you alluded) but the advice dispensed doesn't always move with the times. And Windows should be able to manage it itself as-is to a hefty size (which may or may not be the case) provided you're not space-limited on the appropriate drive (which i'm not).

Cold start tutorial Mk 2 is up now as well

Yeah, with a more granular damage model you could have something like 'operational', 'degraded', 'incapacitated' & 'destroyed' as states depending upon hit damage. e.g. armour that has sustained enough of a hit for a track to be blown off or to have properly caught fire is probably not going to see its crew sticking around to find out what happens next. Same goes for ships where there is a huge difference between hitting them enough (and/or in the right areas) to take them completely out of the fight versus actually putting them on the ocean floor.

I'd say more like a picture of your food and some information on current best operating procedures for said knife & fork. Something to pass the time with though. From what I remember then the last comms on the manual being out before release was 'best intentions but can't promise', so its at least a genuine promise now.

Don't think i've seen anyone else mention it so i'll throw this into the mix. Seems the manual will definitely be made public ahead of the actual release.

Good spot. Whilst 2048MB sounds small (i'd just left page file settings as system managed), isn't resizing it to the equivalent of 100% of RAM a tad excessive? The recommended sizing in the Virtual Memory dialog for Windows seems to suggest a smidgen over 4GB (4964MB). EDIT: Also i'm not seeing anything in the log that its run out of memory anyway? EDIT2: Having had a bit of a dig and the recommendations I can find being min = 1/8th of RAM and max = 1.5x RAM then if I was going to set those values manually then they should be 4GB and 48GB respectively? I guess you could go 48GB across the board for min and max but why permanently give over ~5% of an SSD when the page file will hardly get touched most of the time? Still had a headscratcher though why current allocation when Windows manages it is 2GB (I realise now its probably dynamic but its still a curious starting point) when Microsoft's own recommendation is double that.

I have been having fairly regular crashes in multi-threaded SP ever since the last OB update (2.8.5.40170). Not in particularly taxing missions, just flying around. Zip from the last crash attached. I think any mods have been removed (did have the Blackhawk and F-104 unofficial mods installed) but I am still running with export entries for Tacview & DCS UFC for now. I have tried rolling back DCS to the prior OB version and it seemed better (would like to clock more time up to be certain about that). Any ideas/suggestions? dcs.log-20230521-211826.zip

I've been having issues in SP with repeated CTD since the last update (don't do MP and i'm not on VR either) but also on the Syria map. Not really clocked up enough time to definitively prove the theory properly yet but so far it has been more stable for me rolling back to the previous OB build (which I realise might not be practical if you're playing MP a lot).

Thankfully I do normally bail out, hence I haven't found out exactly why she keeps that jerry can of paraffin nearby.

There are arrestor cables on the runway at Mount Pleasant but purely decorative and you can't catch the wires.

Indeed. If you can't know (due to lack of some kind of feedback) you are on the edge until you are over it and are hurtling towards your new career as a smouldering crater then where is the enjoyment? I've no problem with the older jets trying to kill me every 5 minutes, and I quite enjoy the challenge. Just as long though as I have some kind of indication i'm getting it angry. If that includes adding/embellishing some cues to replace the lack of actual motion/forces/feedback from the Mk 1 Butt then that's fine.

I ask my partner to stand behind me and stretch my face and pull back on my head depending on how hard/sudden my pitch movements are.

I think VJoy put me off a little too when I initially opted for Joy2Key but its not been a problem so far. Yes you're right though, Joy2Key would be absolutely fine for the problem presented and its a great utility.

I used to use Joy2Key for a very long time (liked it enough to pay for it). Having used Gremlin for a few weeks now i'd say the one thing it has a distinct edge is if you use multiple modes. Namely it can inherit from other modes if you have common functions per button (e.g. weapons release, TDC) rather than requiring copy & pasting over, plus you can make it send additional keystrokes when you switch mode (e.g. when I switch to AA or AG specifics mappings in the F-18 it sends the appropriate keystroke to DCS to set the plane's master mode).

Drop me a DM if you get stuck and i'll try and help as much as I can. I'm assuming the 3rd program you mentioned you saw might've been HID Guardian? I didn't need this for DCS. The game detects both the virtual controllers and the 'real' controllers but you just make sure you're only binding to axes/buttons on the virtual ones (just make sure Gremlin is running and the profile you're using is enabled).

No. Having never tried before (I just knew it was an option) I just managed to set it up in under a minute only using Joystick Gremlin (mapping the analog mini-stick X & Y axes on a CM3 throttle to the mouse). This video gives a decent representation of the process. If you're setting up Gremlin for the first time you'll want to set up virtual controllers (for which you use VJoy, which is a dependency of Gremlin) but its a one-time process usually and pretty painless.

I agree. RAF retired them from inventory at least a decade ago and I don't think they ever carried them on anything but the Tornado.

Yeah, who doesn't love the idea of having a big number of very accurate bombs to lug around that still pack enough of a punch to do the job? Almost like baby unitary JSOWs.

There's no conflict as such. If you don't need to use a Gremlin profile for a given title then just don't enable the software and your controllers will just work however you flashed them to work with the native utilities. I have a VPC stick and Virpil throttle and only use respective flash software for calibration and setting up the axes etc. All the button -> keystroke and mode management stuff I do with Joystick Gremlin on a 1 profile per module basis (then just load whichever profile for whatever jet i'm flying). For some games like MSFS where I don't want multiple modes configured then I don't use Gremlin at all and just configure directly in the game.

Joystick Gremlin doesn't do anything to the device. It's basically sits as a layer in-between the device and the game (hence you bind in-game to the virtual devices it creates and not the underlying hardware), whereas the VPC software obviously does affect the controller at the firmware level.

I've got quite long digits so I can quite easily reach that lever with my thumb or forefinger (depending on where the throttle is advanced to) without my hand coming off the throttles. I like the idea of that finger slider, i'm just not a fan of how its been executed.

Fair enough. I just found the slider a little too fiddly to be precise versus the longer throw (and lack of detent) on the flaps axis and didn't want the faff of fiddling with the axis settings in DCS to get an acceptable 'normal' for me at the detent. I'd love to swap it for something momentary if I had the time/means/skills to do it.

Had a CH Pro for a number of years, only recently upgraded to the big heavy expensive Virpil. It worked pretty well and the switches lasted. As its mostly old school tech then the throttle axis potentiometer got a bit flaky after a few years but you can still source spares for it and it was easy enough to change yourself with nothing more than screwdrivers needed. The only other criticism would be the CH software is unsupported and now flaky on Windows 11, although the device works perfectly well with free alternatives like Joystick Gremlin and Joy2Key.