WG, Fix your stupid [edited]rendering bug

[MrDeaf]

Yup, just got the rendering bug, where no ship is rendered on your screen, despite being in detection range and out of smoke.

 

Best part is, this crapis not reflected in the replay.

You literally have to catch it while recording live.

[ValkyrWarframe]

Say it a little nicer, and maybe people will listen.

[Shadowrigger1]

 

      It's your Sheeeetea Game not my Puter !

[Shipness]

"hey my computer is like 5-10 years old and can't run your game! Fix it!"

[MrDeaf]

"hey my computer is like 5-10 years old and can't run your game! Fix it!"

 

ehem

 

i5-3570k, 16GB ram, GTX970, 512GB SSD, 2560x1440 monitor

[Nachoo31]

What color monitor?  Water cooled?

[Guest ArdRaeiss]

Most likely long(slow) ship model loading for whatever reason(busy or slow drive, suddenly paranoid antivirus, some kind of download). We are working on files storage and loading optimization to make it easier/faster. We are also looking if there is something else that could be the reason, but the model/textures loading time is the most usual case so far.

[MrDeaf]

Most likely long(slow) ship model loading for whatever reason(busy or slow drive, suddenly paranoid antivirus, some kind of download). We are working on files storage and loading optimization to make it easier/faster. We are also looking if there is something else that could be the reason, but the model/textures loading time is the most usual case so far.

 

Game file optimizations?

Thank you!

[Skpstr]

 

ehem

 

i5-3570k, 16GB ram, GTX970, 512GB SSD, 2560x1440 monitor

 

"Hey, your computer is too good! Pull some RAM and put your previous video card back in! (maybe run an AI vs. AI game of HOI3 in the background so your CPU isn't left out)

[Wo_9]

this issue sounds familiar...

[MrDeaf]

 

"Hey, your computer is too good! Pull some RAM and put your previous video card back in! (maybe run an AI vs. AI game of HOI3 in the background so your CPU isn't left out)

 

But I only manage 70FPS @ 2560x1440 on max settings!

[1nv4d3rZ1m]

I saw instructions for increasing the cache size on ram that Warships uses(it defaults to 1gb which is totally useless for people that have lots of ram) I dont have link anymore but its on the forum somewhere. That might help with the issue. 

[MrDeaf]

I saw instructions for increasing the cache size on ram that Warships uses(it defaults to 1gb which is totally useless for people that have lots of ram) I dont have link anymore but its on the forum somewhere. That might help with the issue. 

 

now that you mention it, yes... WoWs does only use 1.15GB of RAM... wth...

 

Welp, worth looking into.

[Skpstr]

 

But I only manage 70FPS @ 2560x1440 on max settings!

 

Lol no wonder! You're trying to run an 1/8th mile dirt track in a McLaren F1.

 

That resolution though. Must be nice to have good eyes. I sit about 6' back from a 37" TV, and if I go any higher than 1600x900, I can't read the range info over the target. (I actually use 1368x720 so it's not a strain)

[1nc0mp3t3nt_1]

Most likely long(slow) ship model loading for whatever reason(busy or slow drive, suddenly paranoid antivirus, some kind of download). We are working on files storage and loading optimization to make it easier/faster. We are also looking if there is something else that could be the reason, but the model/textures loading time is the most usual case so far.

 

I will agree with the OP that the pop-in of allied ships is annoying, but I also knew you guys were looking into this issue. its too easily reproducible on older(not necessarily terrible) hardware to be oblivious to. thanks for the update

[Batwingsix]

I saw instructions for increasing the cache size on ram that Warships uses(it defaults to 1gb which is totally useless for people that have lots of ram) I dont have link anymore but its on the forum somewhere. That might help with the issue. 

 

This one maybe?

 

http://forum.worldofwarships.com/index.php?/topic/42946-engine-configxml-fps-loading-stuttering-fix/

[1nv4d3rZ1m]

 

This one maybe?

 

http://forum.worldofwarships.com/index.php?/topic/42946-engine-configxml-fps-loading-stuttering-fix/

 

That would be it, great job. I am on my phone so I dont really want to go searching through old threads. 

[Sir_Apocolypse]

Nope, they found the correct one, I found..."something else".

[Batwingsix]

 

That would be it, great job. I am on my phone so I dont really want to go searching through old threads. 

 

Yeah it took me a few. Trying to sift through the late load threads is almost as fun as the dentist.

[MrDeaf]

 

This one maybe?

 

http://forum.worldofwarships.com/index.php?/topic/42946-engine-configxml-fps-loading-stuttering-fix/

 

thanks!

 

the comments in that file are interesting...

 

What's most interesting is that the game only bothers to use 2GB of ram as default.

[TheDawg]

Say it a little nicer, and maybe people will listen.

 

hahahaha, good one.....

Having been around since 2011....thats not entirely accurate 

[Im_The_Seeker2]

Most likely long(slow) ship model loading for whatever reason(busy or slow drive, suddenly paranoid antivirus, some kind of download). We are working on files storage and loading optimization to make it easier/faster. We are also looking if there is something else that could be the reason, but the model/textures loading time is the most usual case so far.

 

I would prefer if you not optimize file storage, because the upcoming .pkg files are obfuscated and it's promising to kill modding entirely in one fell swoop

[Herr_Reitz]

I mentioned in another thread I was having issues with the models themselves. Yup, I drive an Asus k53e w/intel hd3000 graphics. Yup, everything is turned down to low or off... only recently did that become necessary, next to last update I believe. Long story short - some of the ships had artifacts. 

 

Now it may or may not help your situation but I looked through my registered Microsoft C++ distributions and found one that was not showing as a Microsoft product. So I uninstalled it, ran CCleaner to remove any latent registry entries then installed a downloaded version/release from Microsoft. My troubles disappeared. So my twisted sister logic tells me I made the right move in replacing the "unknown" version. You may want to check your installed C++ distributables to see if they are all MS. 

 

I'm doing the 1/8th mile dirt track on an ATV! 

 

PS: I've always wondered if the rendering issue would repeat in a saved game. If it doesn't that would tend to indicate it is a client-side issue, wouldn't you think? 

[Francois424]

Now I know what killed both my Dad and I two weeks ago.... haha.

Good to know it' getting fixed

[weednot43]

 

thanks!

 

the comments in that file are interesting...

 

What's most interesting is that the game only bothers to use 2GB of ram as default.

 

From the one who made the OP: And the <streamCacheSizeKB></streamCacheSizeKB> default value is 2048 (2 megabytes). It's actually the animation cache. So I quadrupled it as I know that this game is geared towards running on older machines.