IRFC Hawkeye

Disable the on-board graphics in the BIOS, for sure.

Would you post a screenshot of your nVCP settings? Game graphics settings too, for that matter.

No way that should be bogged down; especially if you're only trying for 60 fps.

Is it actually impossible to take off again? Or, is it worse in some areas over others? Does it depend on the weight of the plane, at all? My only experience with it was when I flew a spy mission in the U-2VS, in the current Wing Walkers campaign. I had flown it on a practice server, and although I definitely noticed an extreme difficulty in getting the plane rolling, I was able to take off again. At that time the landing place was not very accurately specified, and it was generally just in a field near a lake. I was able to get the plane moving by using full power, but that was not enough by itself to get the plane "unstuck"; after I started rocking the rudder back and forth fully, it began to move. Once it was rolling, take off was pretty normal after that. Later I was told you couldn't land because you wouldn't be able to take off again. Then they altered the mission such that you had to circle over a specific spot to complete the mission. I kind of thought it was cool the original way. It gave you a real feeling of landing in the bush. But I would not like it if it was like that EVERYWHERE you landed, no matter what; or if it was so severe that certain planes could never take off, regardless.

1070 wasn't it?

Do those axis' show to be working normally in other apps (since you don't use CH Control Manager), such as when you check/test their calibration in the Game Controllers section of Windows, or possibly in DIView? If they work properly there, it is possible to edit that file mentioned by Klaiber above to add the proper axis' to the correct place in the file. However that is something that you shouldn't do unless you completely understand how the lines work, or you have somebody to explain it to you. I know one thing, when you install the CH Control Manager software, it creates some virtual devices. I don't know, but maybe the lack of those (since you don't use it) might have something to do with those axis' not being sensed within the game.

In the nVidia Control Panel, under the "Manage 3D settings" link, under the "Program Settings" tab, do you have a profile established for "IL-2: Sturmovik: Battle of Stalingrad (il-2.exe)"? If so, can you take a screen shot of all of the settings? If not, you could try creating one. If you don't have one, it will automatically use the "Global" settings. If one of those is not optimal, it could easily bring your machine to it's knees.

Yeah, all the Virpil grips and bases are basically interchangeable. I know for a fact that Virpil makes specific profiles in their firmware that allows full function of TM parts on their bases, as well as their own, obviously (I am currently using a TM Warthog grip on my VPC WarBRD base). I did not know that TM had any official support for Virpil grips, as far as that goes; but we know for a fact that Virpil CM grip works on a TM base (how could it not?), just some button variances, which I'm sure could easily be eliminated if TM wanted to officially support them through software or firmware. However, I'm sure Virpil needs them far more than they need Virpil. It is nice that it works, anyway, even if you can't get all of the grip axis or functions to work on a TM base. As for the paddle, thumb wheel and twist rudder axis working on the TM base (the last one being optional and not necessarily used), I would not want to vouch for that, unless TM has new support because of that new F-18 grip. But a lot of those things will still work as a button, and that's better than a poke in the eye with a sharp stick.

I like how the pilot shook the crew chief's hand. The thing seems to handle really well on the ground!

I figured some of you jet guys might like this. Seems to be modeled to some extent after an F-14 grip? Lots of axis, and it even has a (lockable) twist rudder option....which I know is a big thing for a lot of people. I almost thought about getting it, but it doesn't have enough hats for me. It is cool that all these different grips are available....if you can afford them. They're easy to change out if you wanted authenticity on planes that you're flying. There is of course the A-10 Warthog and the new F-18 grip from TM, the T-50 CM grip from Virpil (which I guess is based on the Russian SU something-or-other), and now this F-14 based grip. Any one of them would work on a WarBRD or other Virpil base. And I will say this- their base is TOP quality without a doubt....strong as hell, extremely accurate, tune-able springs and cams, and not a millimeter of play anywhere. Oh yeah....most of this stuff is in stock now, and they accept credit cards and Paypal now too....so far easier to purchase than before. V.F.X. Grip

Yup; and still having fun, mainly in FiF. FC too, but it will be more so once organized events get started; had a lot of fun in Black September, there. Thanks for the info, I'll have a look at it! Good to hear from you again! S!

Thanks folks. Having fun is the order of the day!

A recent "cumulative update" for version 1903 seems to have improved or even cured the degraded performance I was having in RoF. No other changes made.

2.92 GB. Was getting about 14 Mbps at around 3:00 pm Eastern. Installation really took a long time at about the 98% mark, thought it was hung; but it completed eventually.

As posted elsewhere, I did already update to that newest driver. It didn't really change anything. I turned on my monitor's FPS counter and it showed frame rates in the 40's and 50's area. Way down from basically what it used to be, always near the max of 100 for my G-sync monitor. I tried various changes to the nVidia Control Panel settings, but nothing improved anything. The only thing that actually helped was to downgrade some RoF game video settings, such as as forest view distance, and grass quality. Really? A game this old, and a 1080 card to boot, and I have to turn the settings down to get smooth play. BS! FPS went up to the 60-70 range....very playable, but not what it once was. I don't know what they did to Windows but there must be a lot higher CPU demand for some reason. I noticed that there was no turning on or off of Capture Enable anymore in the "Win-G" settings, but still you can capture video (I don't know how much). That leads me to believe it's recording everything, all of the time, no matter what. It's F'd up, compared to what it used to be, that's for sure. Change, for the sake of change. I can hardly wait to see how screwed up FC is compared to what it was like before, which for me was damned good. Message to Microsoft: Sorry Klai, couldn't resist. Delete/move/censor as required....

Shhhh....don't tell anybody. Superman view!!!

The more I have to drink, the less they sit still

These are outstanding; a great basis or starting point for anybody who is creating a JG1 squadron based skin. If you're thinking about making your own FC skin within JG1, I highly recommend checking out these high quality templates which will give you a firm grounding in any of our 4 squadrons, to add your own ideas to. Thanks, Larner!!

As posted on another thread, now have some microstutters in RoF, especially near the ground. No changes to Nvidia Control Panel or game settings made.

People still have fun, it can be challenging, and it's often exciting; and it provides a well established time when a server full of people can all get together for a guaranteed good time. That's never going to go out of style. How that will transfer to FC remains to be seen, but great minds are working on it. If it turns out a lack of plane variety squelches it, there's always RoF to fall back on. You are right about the devs, though; although RoF did reach a state far closer to perfection than Great Battles has. They could have gone far further with the planes they released, but they basically just quit in the middle of an unfinished job. It is a betrayal when all is said and done. Now they've started from square one again, and are already giving every indication that they will stop at any time. I will say that after I updated from Windows version 1803 to 1903, I now see some microstutters at times in RoF, when I had absolutely none before; and not a single change was made to any setting in the Nvidia Control Panel or the game itself.... so what does that tell you? I haven't even tried FC/BoX yet. It is possible that Windows may have changed my video driver during that update. I am going to try the latest Nvidia driver, which just came out yesterday, but I haven't installed it yet. I'll let folks know if that helps at all.

Update on this. I never did get updated from 1803 to 1809. 1903 came out, and so of course I skipped 1809 and tried to install 1903....that was way back in around May, 2019. That version wouldn't install either, showing an error code just like the other. At that point, I just said screw it....I'm not trying to install "feature updates" anymore. I just let the regular updates to version 1803 install when they came. 'Round about a month ago, I started seeing indications that support for 1803 was going to end in November. Well, let the chips fall where they may, I figured. What exactly is "support" anyway? A bunch of updates you don't even need. Ya, ya, security. Well I've never had a virus in my life, although others in my family have. I just don't open attachments in emails or anything I don't KNOW somebody is sending to me; and I stay clear of shady websites. The sites I go to are pretty limited and I know they're safe. I have zero anti-virus installed, except what's part of Windows. So, I was all ready to keep this 1803 version for as long as I still had this hardware; and all that time, after it initially failed to install, it never asked me to install version 1903 again. Well today I powered up, and checked the usual notification about updates needed; and today, at the top of the list, was "feature update version 1903". So I said what the hell, the worst that will happen is that it won't install again, and revert back to version 1803. Long story short, it installed without a hitch; it took a long time, basically like a new install from scratch. I even left for a while and checked later. I didn't have to change any setting in the BIOS. I didn't have to update the BIOS to a newer version. I didn't have to disconnect any hardware. I just let it run as-is; and it worked. What does that tell you? I don't know what their trip is with these feature updates that don't install, but it's obvious they can be made to work right if they try. Hell, it only took them a little over 6 months to get it to work on my machine, which has absolutely nothing unusual about it. I can hardly wait for the next one in a little less than 6 months.

Pretty drastic step.... maybe try letting it ride for a while. Is space that tight for you? Is it really a one-or-the-other thing? No updates ever for RoF is certainly a good thing from the reliability standpoint; nothing ever gets screwed up and people generally understand the cause of every performance issue. But there is little going on in RoF except FiF, and even that may move to FC soon. Would love to have you back flying with us on the WWI side, whatever the reason. Hope things are going better for you soon.

Yes!

And every year, many of us say we wish there was no such thing as daylight savings time!