The performance issues. (The Witcher)
All Shalom.That's the problem,the Witcher 1 at low graphene on ultra,the fps is almost the same,30-40,sometimes(in Vizim) sags to 20,while it is steep(frame time jump).I don't know what to do with it.as I understand it,though the download of the cp and gpu the fact that the game works badly with more than 2 cores and threads.
The load on the core is: 80-20-20-20.Gpu load is 50%.
System:
AMD A8-5600K 4,0 Ghz(+400 boost)
750ti(stock)
8gb RAM(overclocking 1666,the timings do not remember,and they are not particularly important in this problem)
The funny thing is that Witcher 2 is flying at a high(50-60),and the third part at a high 30 fps.
Why is the first part so bad I know,but what can you do,I don't know.
Can try the executable of the game through this thing to get rid of: https://ntcore.com/?page_id=371
-NetherLock
forums you are not beguiled?here's your forum here and write: https://forums.playground.ru/witcher/ you guys first in the third climbed?
Alexander_Vesker
Who I will be at the forum first to answer,consider it dead.Here people a lot more,and many passed the first two parts,so the choice is not great.
blackopsmaniac
GOG,but it does not depend on the version pirates the same as the incentive.
-NetherLock
The engine of the game is old - it is not optimized for threading. The screen shows that 1 core of the processor is loaded almost completely (95%) and at the same time underloaded vidyyuhi (43%).
Spoiler
The same thing was on the Athlon II X4 640 and GTX 650 - due to the weak single-stream performance of the processor, the graphics card was not fully loaded (issued 30 k/s). When replaced the CPU on i5-4460, the game even on its built-in (without a video card) began to give out more.
blackopsmaniac wrote:
... version of Stim or GOG?
It's not about the versions, I had the same on GOG face.
Spoiler
-NetherLock
I think the processor and the features of optimization of the game for such processors are to blame.
the game is one-way and with poor optimization for its time, which was not particularly worked on, even taking into account a bunch of patches. The first witch needs a processor much more modern, relative to the date of the game, and preferably with a high frequency on the core. And this is the configuration:
AMD A8-5600K 4.0Ghz
750ti (stock)
it is difficult to name gaming even regarding such projects as the first witch.
Witcher 1 is not friends with Windows 10, there is also a big operation gore and in the Brake Charge !
Thank you all, I'll be updated soon, because as I thought the problem in the process, oh, this performance on the core of the amd percent of the series A.
X_ray_83
It doesn't matter what the shindovs are, I'm at 7 and 8, and 10 is the same.
I remember the peck in the 800s600 or 1024 x768 playing up to the woods and there's a 10-15fts where the driads go with the sis. and ran for the see-it-all tama all the quicker ran at once the processor was bark duo 6600 and as a normal baker gathered drawdown were only in the city when the guards with torches go and you such a torch takes out the shadows honest and camp ret aaaaa
so the brake block if it is something fundamental or it is a problem streaming the engine. hardly modern multi-nuclear chicks in something inferior to all sorts of tsub-sdre2
and so the logic is usual if the shed is laid and it is unclear why it happens over means to drive bandwidth and performance in massive single-thread tasks such as real storm benchmark what is anything
Cardinal Fikalis
Not "no difference" Witcher 2007 was developed under Windows XP and only on it is guaranteed the work of the game, so on the disc with the game written, Vista also flies !
X_ray_83
Ok, throw a poof, take a picture of the screen in the merchant's quarter on the street, either near the house of Triss, or in the square near the bank Vivaldi, where traders, with the withdrawal of monitoring phps, loads of kernels, memory loading, etc. on Shindovs xp and 7, or other any shindovs, after 7. If kp is a stable fps, without drawdowns, even higher than on other chindovs - ok, you dice, etc., you can come up with any other titles for yourself, and without the proffos be kind, do not star here this delirium. I can shorten your time, the phps will be equally sagged, because the only loaded core in the weave, why the processing of objects is extinguished, because the engine is overloaded with these objects and effects, and overloaded because ... This IS MOVOK, which at that time has already outlived its own, it's like grading in 2020 socket 775, put in it 64 GB of ooz and 3090, while waiting 666fts in 8k
X_ray_83
most likely there will be in the instructions of the processor namely, that a number of old igors and applications uses some old shit that do not support the new stones and they consider this case in emulation mode. and in the bit of vinda as it seems to me that the processor especially does not care what numbers to count F32 or F64 and how much memory to address given that modern processors have become many times wider in all directions. so it doesn't matter from the wasp's point of view. the only thing that new wasps probably don't support 16 bit applications, and 64 bit wasps don't support them at all.
then there's the more serious problem it's dh8.x - in short it's slow especially that sh1.1 and dh7 glitchy I think it's still without artifacts won't work. and the slowness of the dh8 correlates as something incomprehensible but in general the new maps work about the same as the old ones. just there before it was not particularly important what drawdown gives a haze against the background of overall performance. With modern maps it's a jump with hundreds of fps somewhere in 30.
and then I vedmaka 1 with the disk on the whist and 7 is not going to let go. predicted on the disk box. and just like it's pretty glitchy or the driver then had glitchy. with the Radeon x1000 series it worked without artifacts. with 3870 there began artifacts if you drink and what to pump up will be a lot of all sorts of effects of shader. and 4870 x2 radeone there was a wave on the water knocked down and went in a strip, a sinusoid.
so graphic apes are kind of a big problem in old games than stupid windies.
MunchkiN 616
some old shit that doesn't support the new stones and they find this case emulating
That's the problem (((
There's also EAX and if the sound is not built-in will plant the fps not hilo)))
And so the game runs even 500 meters of RAM, 1.5 giga needed for a quick transition between the buildings volume of operative accelerated this process.
X_ray_83
X_ray_83 wrote:
There's also EAX and if the sound is not built-in will plant the fps not hilo)))
at one time it was said that the treatment of dhsund takes a few percent of the load of the tpe. then it means cor duy and quads medium yes pretopes.
in the witch as far as I remember there is no eah or it is programmatic because there was an echo in the caves it I had and without a map of the eah. and with the purchase of a card from a creative where there was an even score nothing has changed. in doom 3 so for example there was an eah so it kind of without eah cards and not to sing. there was some super cool card from the creative who had a buffered built-in memory - it was sort of to reduce the load on the processor but it was supported by the current of Batyafield 2142 and a pair of igors and as if on this eak bunch with the output of Windys and DH10. So it's a buffin.