37mm

Needs must, I'm afraid Your options are, with regards to this scenario... (i) Upgrade your CPU (ii) Play in Wego (ii) Don't play it, instead play another scenario. If this means what I think it does, then that gives you an idea of how many LOS calculations are being performed in this scenario. That "blue bar" turn processing time is NOT a loading process... the vast majority of it will be the LOS calculations for that minute of play.

I know, I was just wondering if there was a issue with the scenario file itself. It really doesn't sound like you have a graphics/settings issue. Which means you're likely having a LOS calculation issue. Playing in RT means all the LOS calculations have to be done in real-time... I don't think your PC can cope with the CPU load (we're talking hundreds of thousands, maybe millions of checks). Try playing the scenario in We-go, then the calculations are performed during the turn processing phase.

Yes... plus some extra Afghan voices from HQS 3.1. Although it took me a while to get it right (there are still arabic voices present in the first few scenes).

Ignoring whether or not 50 fps should be considered terrible for CM perhaps we could test this theory more thoroughly? Play the game with your PC on minimal power settings... that should turn your high end computer into a low end one. Any difference? When you say V-sync make's no difference... do you mean it still stabilizes at 40-55 fps or that it still fluctuates up to 300fps? If the latter then vsync can't be working.

I would've agreed with your conclusions except for one issue... I cannot recreate the effect. I can recreate the "frame rate fluctuations that stabilize into an equilibrium" effect easily enough because, as you suggest, that's happening pretty much all the time. However the fluctuations I have (no matter the settings I used... AA on or off, Best/Balanced 3d model quality, high or low tree details) are only a few fps here or there... even on the edge of a forested map. Obviously, the fluctuations are greater when I pan & move the camera... however 10-20 fps is the usual level of fluctuation not hundreds of fps like you're getting. I can't seem to recreate these wild fluctuations. I'd suggest that you have some kind of driver issue? What happens when you have vsync on Fast & recreate that scene?

I did not say that. At all. But, clearly, you see what you want to see & read what you want to read.

These days, I wouldn't be surprised if BFC are forced to fire you & denounce all "Neo-Nazi" Quick Battle maps as "against our values"... or face the fury of the "press".

No... I do not see the Virgin Mary. At all. However, I am able to figure out what you think you see based upon the 2d map of the crossroads, your thread title & your OP etc.

Nonetheless I can give no advice on whether it's a "good deal" or not. I would advise checking up on it. Altogether, I like the sound of the Motherboard... better than what I bloody have.

Presumably this is the modern version of seeing the Virgin Mary in a slice of toast or whatever. There's nothing there but a 2d map of a crossroads. Anything else is in your own head.

Having a very quick look. i5-7500's turbo up to 3.8Ghz... so that's pretty good. Your motherboard is upgradeable & supports at least an i7-7700K (4.2 Ghz... with mild overclocking, probably 4.5Ghz). All good. Your Graphics card? I can't tell if your proposed Motherboard even supports a 1050 Ti never mind could be upgraded further. I'd check up on that. Another piece of advice... ask your supplier to run a benchmark & send you the results. I don't know if they would do it, but it seems to me that if they don't... f**k 'em.

My apologies. For not even bothering to hint at what the purpose of the experiment might be.

CM is a CPU intensive game... if I was to offer you one piece of advice (assuming the primary games you play are CM) it is concentrate on pure, single thread, Ghz. An i-5 2400 isn't that bad in that respect (it turbo's at 3.4Ghz). However, my Motherboard? I have no hope of upgrading to a K CPU (which would allow some mild overclocking) & probably the best upgrade I can get is an i5-2500 (3.6Ghz).

Shaders/Shadows do affect performance... however it depends on the map/time of day whether it's a particularly noticeable difference. Turning them off when its bright & they're a lot of buildings around can make a big difference*. Turning them off at night is kinda pointless. *I learnt this recently when Task Force Narwick rolled into a large city.

Playing? No. However I specifically said it was an experiment. It might help determine if his lagging issues on this one huge scenario (and seemingly not any other huge scenario) are graphics related or LOS calculation related.

Now that is interesting. I too don't have CMFI (yet)... so I can't test anything directly myself. After doing the googles though, it also appears that you're not the only one complaining about this particular scenario either. I'd ask you to explore a few possibilities... (i) As Howler advises, make sure your tree detail is 'low'. Also experiment by turning all tree's off (ALT-T) then going to your briefing screen, then going back to your game (that resets & reloads everything). (ii) There's another version of 'Hot Mustard' available, is that really slow for you too? (iii) I had an issue a few months back with "threaded optimization" settings on my graphics card profile... make sure they're switched off (especially if you use 'movie mode'). (iv) There are loads of LOS calculations in Hot Mustard because of the terrain, have you made sure your CPU is operating at maximum performance with its power settings?

I've loaded up a few huge maps recently just to check if my system can handle it. I've a relatively mediocre i5-2400, with 8GB RAM & a 1050 Ti Graphics card. With 1080p resolution, all AA off (on both in game options & your graphics card profile), Vsync off & a Balanced 3d Model Quality I can move around a huge map at ~45fps. It rarely dips below 30 fps even when I'm right down at eye level with tanks everywhere. If I turn shadows & shaders off I get ~10 fps onto that. I didn't bother changing the 3d Model quality to fast but I imagine that too would gain me another ~10fps. With so much fps to play around with, it's then usually not an issue to turn on a bit of cheap AA with reshade (might cost you ~1fps). Huge maps (and in CMSF2 giant urban sprawls) are intimidating but if you adjust your settings correctly you should be able to play all but the most absurdly massive/complex maps.

You're the reason I started work on the package... I'd never even heard of Project Reality or Squad until your explosion experiments thread. PM sent

Hopefully the actual modders will show us what they can do when a "one size fits all" approach is dropped.

The helmet files are in 1.2, CMFDR even took a screenshot of them for you. As for the uniform files that remained from 1.1...

Yeah that makes sense, I already have day & night muzzle effects so an intermediate between the two shouldn't be that troublesome.

Thanks for the feedback. I think this might be a personal taste issue because what you describe is very much what I was hoping to achieve... Have you tried the night effects? There's nothing preventing their use during the day & they're certainly a "tad" more noticeable.

I thank you for the compliment but a real main gun blast should be a LOT quicker... ... what I have now is still far too slow.

Perhaps something as simple as "vehicles & moving infantry get a concealment penalty" when under a "flare"? Obviously we have no idea how BFC calculate concealment but I'm pretty sure units travelling along roads get a penalty (or lose their "bonus"?). Additionally we know that units which fire lose a lot, & often all, concealment. So we know BFC can change concealment independent of terrain. Program it such that vehicles & moving infantry under the "flare" give away their position as if they had fired.