Since I can’t fly the Harrier in DCS yet like some other cool guys here @BeachAV8R (I did prepurchased the module) I’m honing up my hover skillz in some other notable releases.featuring the iconic STOVL.
I FUBAR-ed the landing real good but in my next video scheduled for tomorrow (showing some ground pounding) I promise to rectify that.
Yes, I’m running it on DOSBox with core set to dynamic and cycles to 250000. I can set the cycles up to around 400000 before I max out the CPU usage, but the game will run too fast then (so no cycles=auto/max either). The frame rate limiter wasn’t applied until Fighters Anthology patch 1.02. All earlier titles in the series doesn’t sport one. The games required pretty beefy setups back then though, so that wasn’t an issue at the time.
I never played stock USNF (besides the demo), as I own the Gold version which merged USNF with MF. Isn’t “addon” and “expansion” basically the same thing? From what I know Marine Fighters when first released still required USNF, it wasn’t a standalone title.
Yeah, getting the rate right for F3 is like finding a needle in a needle stack. The last time I tried to fly it was over a decade ago and I recall ripping off the landing gear and exploding within about 2 seconds of throttling up on the runway.
Of course, getting the “magic free RAM” to enable the B-52 cockpits and other details was super frustrating.
In Falcon 3 if you didn’t have enough “low” RAM (the under 640k part), B-52s had no windows on the front, among other lost details.
So many of us made custom autoexec.bat and config.sys for playing F3 that would bypass loading drivers for CDROMs and such. We even found a super-slim mouse driver (it was like 8k resident) so we could use a mouse in the menus still without violating that limit.
I believe you needed to have 610k free (so mouse, system, and other drivers had to total less than 30k) or it was insufficient.
Many switched from MS DOS to DR DOS, or used QEMM386 instead of MS’ own EMM386 because they used less low RAM.
I still have nightmares about that. My grandfather and I (he a retired IBM software engineer) spent an entire month to get the boot disk to work right, and even then we only had sound maybe half the time.
Oh dear messing around with autoexec.bat and config.sys sure was interesting. My dad and I made boot discs for many games.
Falcon and Wing Commander were examples that just needed every bit of power so they could run well.
…sigh…I don’t miss it really. It was a pain in the behind.
I remember that I managed to get around 612kB (or was it 622kB?) of free conventional memory with all the drivers (mouse, CD-ROM, sound card) loaded. I used memmaker.exe from DOS 6.22 to optimize the driver loading and some manual tweaks in config.sys and auoexec.bat. I was able to run Falcon 3.0 without issues with all things working. Had to run it from plain DOS command prompt though as running Norton Commander would eat those extra few kB needed for Falcon 3.