(ATI) Remove intro video => +10 FPS in game
 

Probably some of you already know this, but if you are an ATi user, remove the intro video of the game and you will gain 10-15 fps in game...

It seems the intro video blocks ATi cards in some way they do not use their full potential in the game.

Hope this helps!
S!

Do you mean the splash screen for UBI?

For the millionth time, this is (in most cases) NO LONGER NECESSARY.

Initially the Ubi splash screen was preventing some ATI cards from clocking up to 3D speed, instead getting stuck at the video clock speed used for the logo.wmv - probably because the game was running in a pseudo-windowed fullscreen and not being recognised as a proper 3D app by the card.

That issue was solved several patches ago (I'm the one who figured it out, and I no longer need to delete/rename it). Only do this if:

A: you check your video card whilst the game is running (with GPU-Z or similar) and discover that your card isn't clocking to full speed, or

B: you just don't want to see the intro video anymore.

Removing/renaming it will not give you ANY fps boost unless your card is underclocking, which, after the current patches should no longer be a problem.

ATI 5970 here...it still does it for me, and I still therefore have to disable the splash screen. I am very sure of this.

How do you disable it..I just tired of seeing it & the wild eyed pilot I have to double click to get rid of?

Here you go mate

http://forum.1cpublishing.eu/showthread.php?t=24126

:)

By the way, this does not remove the wild eyed pilot splash screen, it removes the animated ubisoft logo movie.

Have you tested GPU output while the game is running and found your clock speed doesn't hit 3D speed? I'd be surprised if this bug was rearing it's head again, though I don't discount the possibility - but until it's tested I'm inclined not to believe it.

If you run GPU-Z prior to game start, then load CloD you will see clock speeds jump to 3D, then drop significantly when the Ubi splash is played and remain there if you still have this problem. If that doesn't happen and clock speeds jump back up (or do not decrease) after the splash is displayed then it's not the splash screen causing the problem.

Hopefully you can confirm this with a GPU-Z or similar output screenshot - it's no good saying bugs are fixed when they're not, and vice-versa - so if you can prove you still have it, we can advise the use of the fix where it is appropriate, and if you don't, we can stop blaming the ubi splash for the low performance problems (which are nearly all unrelated).

You can see in the stock ati drivers under overclock. The problem is still there! My card would say 400mhz in game with bad fps. Disabled ubi vid and it went up to cards 860mhz. So the problem was not fixed.

Yes, did all that. Don't take this the wrong way mate, but after countless hours of tweaking/testing/logging since release I have absolutely no intention of doing any more. If you chose not to believe me without a screenshot, so be it :) Bottom line is, for me, video card clocks (and therefore FPS) are reduced with the ubi logo, and are not reduced without. If anyone is curious as to the effects on their own machine, it is a simple thing to test and either keep or discard the logo as their results dictate.

Again, no offense intended mate, I am just completely "over" testing/tweaking/logging/benchmarking. The game runs acceptably on my rig now and I am happy to await further improvements from the devs.

Cheers

Problem is still there, i know the game runs on fullscreen now but the problem is ubivideo is not fullscreen and it forces your gpu to 2d speeds and when its over it doesen't go 3d speeds.

Tested it many times and there are much difference on fps.

Rig is listed below. I had to disable the splash screen as well and as soon as i did got a giant improvement even after current patch.

But I am still not able to run it in 1920 x 1080 mode yet without big performance hits. Not sure if this is due to the Crossfire or just the fact that i only have the two 1GB cards.

Hi again Orpheus

I typed my original replies from my office. I enjoy the game and given the childish going ons at several CloD forums lately I really did not want to appear as being flippant or offending to you by not wanting to bother with doing more tests...so, Icouldn't help myself and now that I am home, here are some numbers for you :)

I used the monitor and log function in MSI Afterburner .... If I tried to take a screen shot with MSI, it did not include the onscreen monitor for some reason but I will cut and paste from the spreadsheet I exported the log to,
Hopefully it shows up ok in this format;

The first set of numbers I just cut and pasted the figures when flying. The second set of number include immediately before and after flight (when in the menus as I entered and exited the game - the GPU clocks seem to clock down during the menus).

With ubi
22/07/2011 15:25:56, GPU1 core clock ,GPU2 core clock ,GPU1 memory clock ,GPU2 memory clock
22/07/2011 15:25:57, 724.992 ,156.999 ,1000.000 ,300.000
22/07/2011 15:25:58, 724.992 ,156.999 ,1000.000 ,300.000
22/07/2011 15:25:59, 724.992 ,156.999 ,1000.000 ,300.000
22/07/2011 15:26:00, 724.992 ,156.999 ,1000.000 ,300.000
22/07/2011 15:26:01, 724.992 ,156.999 ,1000.000 ,300.000
22/07/2011 15:26:02, 724.992 ,156.999 ,1000.000 ,300.000
22/07/2011 15:26:03, 724.992 ,156.999 ,1000.000 ,300.000
22/07/2011 15:26:04, 724.992 ,156.999 ,1000.000 ,300.000
22/07/2011 15:26:05, 724.992 ,156.999 ,1000.000 ,300.000
22/07/2011 15:26:06, 724.992 ,156.999 ,1000.000 ,300.000
22/07/2011 15:26:07, 724.992 ,156.999 ,1000.000 ,300.000
22/07/2011 15:26:08, 724.992 ,156.999 ,1000.000 ,300.000
22/07/2011 15:26:09, 724.992 ,156.999 ,1000.000 ,300.000
22/07/2011 15:26:10, 724.992 ,156.999 ,1000.000 ,300.000
22/07/2011 15:26:11, 724.992 ,156.999 ,1000.000 ,300.000
22/07/2011 15:26:12, 724.992 ,156.999 ,1000.000 ,300.000
22/07/2011 15:26:13, 724.992 ,156.999 ,1000.000 ,300.000
22/07/2011 15:26:14, 724.992 ,156.999 ,1000.000 ,300.000

WITHOUT UBI
GPU1 core clock ,GPU2 core clock ,GPU1 memory clock ,GPU2 memory clock
22/07/2011 15:34:55, 156.999 ,724.999 ,300.000 ,1000.000
22/07/2011 15:34:56, 156.999 ,724.999 ,300.000 ,1000.000
22/07/2011 15:34:57, 156.999 ,156.999 ,300.000 ,300.000
22/07/2011 15:34:58, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:34:59, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:00, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:01, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:02, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:03, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:04, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:05, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:06, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:07, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:08, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:09, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:10, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:11, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:12, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:13, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:14, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:15, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:16, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:17, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:18, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:19, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:20, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:21, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:22, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:23, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:24, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:25, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:26, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:27, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:28, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:29, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:30, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:31, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:32, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:33, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:34, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:35, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:36, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:37, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:38, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:39, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:40, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:41, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:42, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:43, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:44, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:45, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:46, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:47, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:48, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:49, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:50, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:51, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:52, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:53, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:54, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:55, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:56, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:57, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:58, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:35:59, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:36:00, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:36:01, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:36:02, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:36:03, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:36:04, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:36:05, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:36:06, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:36:07, 724.999 ,724.999 ,1000.000 ,1000.000
22/07/2011 15:36:08, 156.999 ,724.999 ,300.000 ,1000.000
22/07/2011 15:36:09, 156.999 ,156.999 ,300.000 ,300.000
22/07/2011 15:36:10, 156.999 ,156.999 ,300.000 ,300.000
22/07/2011 15:36:11, 156.999 ,156.999 ,300.000 ,300.000

Yes, I know it is a cut and paste from a spreadsheet instead of a screenshot...yes, I know I could have simply typed these all out to be a trouble maker. My previous posts on this board hopefully show I am not here to waste anyone's time...these numbers are accurate on my system.

So that suggests to me the Ubi logo still has an effect on GPU clocks, for my system at least.

Cheers mate

I can confirm also the problem is still there, so Orpheus, For the millionth time, this is (in ALL THE CASES) STILL NECESSARY.

Just delete it, Because its rubbish, and i dont need rubbish on my computer:)

I don't need to see UBI laughing at me when I start CoD.Even if it GAVE me 10FPS, I would still delete it ;)

5570 here and i gain 15fps with deleting the ubi logo!!!
so orpheus you are wrong on that.

I must admit. I thought this was just a bunch of whiner baloney so I run a test. :-P
Dusted off the game after couple of weeks (not playing it until fixed) and run couple of tests using a portion of The Black Death.trk.

Results:
With logo current: 50, average: 44, maximum: 64, minimum: 7
Without logo current: 55, average: 51, maximum: 69, minimum: 10

All max @ 5760 x 1080
Another blatant bug resolved by the community and ignored by developers. :rolleyes:

Reported!

That's great, thanks mate. Quite happy to believe you now, especially as a few others have popped up still experiencing it as well. Just surprised to find that this is still a problem - as I say, for me the issue was solved around the second patch, so something even stranger is going on. Before I was under the impression that it was all ATI cards doing this; now it seems some do and some don't. I might have a look myself this afternoon and see if I can replicate the original error I had, or at least figure out why I don't get it now!

I'm also at the very edge of my patience for testing so I know exactly how you feel ;) Appreciate you taking the time to confirm it, and apologies if I came across as snotty - just didn't want to see the bug issues flooded with 'false positives' as it were. Those of us who've been here from release have had quite the time of it and proper bug tracking is the hardest part, both for us and the Maddox team.

I removed splash screen intro as per instructions(BTW:Thanks!) & I think I got better FPS as well .I say "think " because I haven't got FRAPs to work with CloD and don't know how to get an FPS indicator to work in game.
Gameplay does seem better really better , but my shooting is still 'orrible!

For in-game fps, bring up the console and type FPS SHOW START. To hide it, type FPS HIDE STOP. :grin:

I can't seem to find th ekey stroke to bring up consol ,can you help?

Just assign a key stroke in the options/control menu:)

My card does not care if the logo is renamed or not it will not alter its speed unless I force Use Maximum Clocks. :confused:

When I force Max clocks I get a 15 - 20 fps boost.

Also no matter what I do I cannot get crossfire to activate? I check it with other games and it works as advertised, just will not work in CLoD. Is it a common problem or does it not work yet in game?

By default it is the " ~ " key that brings up and closes the console.

If you do not want to force clocks manually you can create a Game Profile for steam.exe and launcher.exe in ATI Tray Tools to load it automatically.

For crossfire there is a thread explaining how to activate it using Lost Planet (iirc) profile in RadeonPro. Probably it also has Game Profiles to force clocks.

Overclocking doesent help for right speed, only disabling that logo is way for me? Weird but true.

Tried this for myself...the difference is insignificant in my case.

Black Death track all settings on high: (Average fps)

44 fps with splashcreen enabled.
45 fps without.

Hi mate

When bringing up the FPS numbers in game, the "case" of the lettering is important....it should be;

fps START SHOW (the "fps" part needs to be in lower case).

I cant remember what the "activate console" command is by default, I changed mine to the tilde key ~

To check what key will bring up the console in your game, or to change it, go to controls from the main menu. Make sure "keys" is selected, and the drop down box says "game" . On that page, the first entry is "Activate Console".. that is the one you are after.

When in flight, you then need to obviously activate the console and type the fps START SHOW command to see your FPS.

Cheers

PS, my shooting is worse than yours, guaranteed! ;)

its 16.10.2011 now, i have just bought the game and i find after all these patches and months of time that the UBI logo problem is still valid !!! My AMD 5970 still refuses to clock over 400 Mhz when the UBI logo is not deleted...

what does that say about the developing team ????? SHAME on them, if they are not even able to consider that such an easy to solve problem still is unresolved and will for sure bring many people to desperation until they find these threads here... or maybe they wont find these threads and just shelve the game....

I'm sure that most people who buy any game, will immediately look for patches or updates online so that their game is current.. not only that, if they are like you or me and have more than one brain cell, if they find they have any kind of problem with the game, will look on the official game sites for remedies and advice.
I have had many games that have had problems in the past and have had to do some 'research' to get the game functioning correctly.
Yes, it's very frustrating for any game not to 'work straight out of the box' but it's not unheard of.
Before I play any game I have bought, I always check out the official site to check for updates and problems/solutions..

So your problem is solved now is it?

yes, yes, so do i... but after so many years of dealing with buggy, sloppy programmed games i am getting a bit tired sometimes of having to invest endless amounts of time just in order to get something running normally which i bought for good money.
If it would be the only bug in CLOD i wouldnt mention it.. i had read the forums before and knew it was buggy, but i hoped it had become somehow playable by now after some patches... unfortunately i find it still a major example of general sloppiness of the programmers...

This video bug for example could have been eliminated long ago... its a known bug, easy fix i would assume.. but no... it lingers on...
Crossfire is not really working....
My FFB keeps cutting out and in and sometimes has no centering at all..
Antialiasing is a mess..
General performance is still horrible...
with other words:
Simple basic functionality is still totally crappy and buggy.

I am pi..ed that i was so stupid to buy it out of curiosity...i should have known better...
Maybe i ll check it again end of next year...

1) LOL. Get the ATT and set launcher.exe game profile to run at desired clocks.

2) Never buy a dual-cheap(!) GPU again.

yeah.. problem solved...
fps better...
but game still horribly choppy over ground despite nominally ok fps (in the 40s)...
will give it another try next year when i am going to buy a new gfx card..
and when AI doesnt roll any more like tie fighters...
back to UP3 and ROf until then...

and lol to you too...

and the card wasnt exactly cheap when i bought it.. and it still delivers incredibly good fps and gfx almost EVERYWHERE except CLOD...

Just FYI:
ATI Saphire Radeon HD 6850, latest drivers installed -> Ubi Logo Bug is greeting :-)

The interesting thing about this is that it worked a few days, even with the Logo displayed... strange things happen inside of my PC... ;-)

I renamed the ubilogo-movie and got a boost in FPS!