Jaus

I really don't remember. Are there certain ones that have issues to be aware of?

I don't know how to tell what the fan speed is. I'm pretty confident that this is not heat related. The problem usually occurs when I first turn the computer on and start the geme. Once I restart the game (during the same computer boot) I have no more problems no matter how long I leave the computer on or play the game.

I remember this post from a while ago and I did use if for a while. It may have been around that time i started noticing the problem. Probably just a coincicence. I have been using the setting I posted above for a month or so now with little improvement. I have switched on MSAA vs FSAA and unchecked SSAO, HDR, and Sharpen. We'll see if that limited change helps. I also experience a crash in RoF evertime I start a mission. I have to restart and then everything is ok, just like in IL2-GB. I have a suspicion some important component is not being loaded on my computer and IL2 just handles it a little better.

No, Jan 20th was the last post I put on the IL2 forum in response to a request for direct x settings. Nothing since.

Here are a couple of my favorites....

No, it was just a fun project that we played years ago as a series of one-off missions. I'm not sure why I brought it up. Just reminiscing I guess.

There is a setting in VA that lets you specify a key that when pressed suspends listening for VA. I have this set to my Pause/Brk key which is my TS push to talk key, but VA is still listening. Has anyone gotten this to work?

I hate to see the possibilities of an intense, varied, combined arms theater like the Pacific lost in a debate over individual aircraft matchups. I know this is an aviation sim, but what about the recreation of the historical experience? Of course I am one who values the historical immersion far more than the rock-paper-scissors of warbird debates, but there must be a way to create a positive Pacific experience for both single and pvp players.

It is true that the continuous-campaign map design of IL2 these days does make it hard to do a steady, balanced Pacific mission area. I sure do miss Pacific theater though. Back in '46 I put together a historic/fictional Guadalcanal mini campaign that included: Raid on Tulagi the morning of the 7th. Aug 7th afternoon air battle as the first wave of Japanese bombers met the Wildcat CAP Aug 8th air battle when Japanese tried low approach to landing zone Attack on the Ryujo (Eastern Solomons) Pre-dawn sub-hunt Low level surprise raid on Henderson by Japanese floatplanes (this one was a favorite...no time to taxi, full flaps, firewall it, try to avoid hitting freindlies doing the same ) Cactus AF strike on fleeing Tokyo express vessels. Cactus AF strike on Japanese landing at Lunga Pt.

Guadalcanal campaign is an excellent choice for Pacific focus. Tight in air, land, sea action, day and night, could use air starts to represent carrier/Rabaul strikes. Henderson field, Japanese float plane bases, strikes on landing zones. I've always wondered what it was like to see Hiei and Kirishima pound Henderson all night.....(not that great for an air oriented sim, but wow.....) My favorite focus areas have always been those that occurred when the outcome of the war was still in doubt.

Well, the problem didn't go away. I have perhaps identified a pattern. Here is my post from the IL2GB tech forum :

I did a re-install just to clear out any residue of Reshade, but no change. Just an hour ago I followed advice from another poster who had viewed a track I uploaded and said it looked normal to him. He advised manually setting the "full" and "win" resolutions in my startup config to 2160x3840 which I did (not sure what they really mean...). Also advised setting all NVIDIA control panel settings for IL2.exe to defaults. I did both and viewed the the track I had posted and did not see the problem. Also tried the mission again and did not see the issue. keeping fingers crossed. The other aspect of this change is what it will do to spotting as I had set my NVIDIA settings to maximize that (not that it did a whole lot of good)

hmmm, I was using Reshade, but deleted the files (the ones I could find). a week or so ago when I stopped using it. Maybe a complete re-install is in order.

Posted to the tech issues forum.

Updated graphics driver for my 1080 ti..... didn't help much/

I decided to give BoS a try while it's on sale. It has given me the opportunity to finally get a shot of the kind of graphic glitch I've been talking about in FC. In the attached shot the layer of green that runs through the gunsight is actually above the plane. From above it appears as normal terrain, until you try to land. The light blue is graphic dead space, and the real terrain is the green layer below the gunsight. A moment before this I had flown directly into trees that appeared to have tops above me, but flew right through them. Ever seen this before? This is actually worse than what I've seen in FC. Is there a cure?

Thanks for the suggestion Tobin. I think I have found a solution to my particular situation. I have all of my game controllers plugged into a hub with individual port 'on' switches. If have them switched off when the computer boots, then turn them on in the same order each time, allowing a few seconds between each port, I don't seem to get the id shuffling. Interestingly, having all of the ports on when the computer boots does not solve the problem. I might try the config file solution in the future, but it seems like it would be hard to keep track of all the config files you might wind up creating (?) S! Jaus

Has anyone found a solution to the constantly changing controller ID's in Win10? I've done some searching and found reference to a third party software that allows you to specify joystick ID's but, as you might expect, the posts are old. I seem to recall hearing mention of a file replacement or the like that cures, or works around, the problem.

Usual time?

JG1_Jaus JG1 UTC-4

Ah, I wasn't aware you have to have mods on in ROF to see skins. Too bad. I wonder if an approved skin can be modified and used?

So, for me the steps were: copy the 2k .dds from FC to ROF (for 4k dds use PS to reduce size to 2048x2048) Then in the ROF copy: use levels in PS to reduce the brightness of the main layers use levels to increase brightness of alpha channel save the .dds

I found the method to get rid of the holes directly in the .dds. You have to considerably brighten the alpha channel in the .dds I used levels to alter the alpha channel thus:

You may be right. My next tests are going to be: cloning over the holes in the .dds, and removing the alpha channel in the .psd and saving a new .dds to ROF.

It looks like skins from FC can be ported to ROF just by copying the skin into the appropriate folder. I did this with my Alb skin and it worked without modification. There were two drawbacks however: The colors as rendered by ROF were much brighter than they appear in FC. I had to reduce the overall luminosity of the .dds considerably to get the colors I had seen in FC. Also, ROF may not be able to handle the effects of the alpha channel from FC. On my skin, areas of high reflectivity appear as holes in the skin. It is noticeable up close, but to me it didn't appear significant in the air. This would probably be fixable with a little work on the .dds in Photoshop.