q123

you're welcome 🙂

you're using incompatible A19.2 Mods in A20. Delete your Mods-Folder and try again 😉

The fullscreen option ingame is per default a borderless window only. But if you use to start the game from steam and chose "show game launcher" - there is an option for "exclusive fullscreen". This together with the "show Unity Screenselector" gives you a real fullscreen.

Sorry, but you can't just add the memory of two different cards. Is your second card identical or does it maybe have 2 GB? If it has more VRAM, than play on that card. And if you can't see your toolbelt - resize the window a little smaller. The toolbar is maybe just moved out of your visible area 😉

here ya go: 😆

I don't know how actual Steams listed min requirements are - but it tells about a 2 GB VRAM at minimum. But your GTX 660 has only 1.5 GB - it's actually less than minimum. Besides the driver update, it may help to lower your screen resolution a bit.

hmm, your installation differs a litte from mine. I don't have a subfolder 'x86_64/' - these dlls are directly under /Plugins/ in my 19.6 installation: D:/7dtd a19 Stable/7daystodie_Data/Plugins/x86_64/easyanticheat.dll D:/7dtd a19 Stable/7daystodie_Data/Plugins/x86_64/XInputInterface64.dll Why is it different for you?

I can't help on topic - but mine is still showing "Game 17" and you've seen it in this thread 😉:

here is an example for trader Bob (taken out of the actual Compopack-list) with min=1: trader_bob,41,27,46,-1,2,burnt_forest/snow/pine_forest/desert/wasteland,wilderness/city/town/rural,any,1, hope that helps 😉

there is a property in 0-SphereIICore\Config\blocks.xml named UnlockEnemyHealthBar. Try to set it to "false" - this should work 😉 <property class="AdvancedUI"> <property name="Logging" value="false"/> <property name="DisableXPIconNotification" value="false" /> <!-- Don't like the UI element for XP? Set to true to disable. --> <property name="UnlockEnemyHealthBar" value="true" /> <!-- Unlocks the enemy health bar--> </property>

wow 😲

found it 😉 "It's Done When It's Done" is an HDRP game that is a unique combination of a thingie shooter, with stuff in it and things everywhere. Play the definitive Raytracing DLSS sandbox HDRP that came first. Madmole awaits! https://store.steampowered.com/app/251570/Its_Done_When_Its_Done/

Your site is already using a valid SSL certificate. You should just add https to the links above - it should work fine 😉

What you're looking for is in Compopack, check for IZEA 😉

2021-06-25T12:47:05 8.874 INF [MODS] Trying to load from folder: War3zuk 100k Stacks (Datbird Edit) 2021-06-25T12:47:07 10.673 INF User joined: datbird looks like, you have edited yourself some of the mods by hand, right? I've never tested it, but "100k Stacks" for example sounds like a game breaker for me.

@BadAssHeigl are you really still playing with A19.0 (b180)? This (vanilla) issue should be fixed in A19.5 - you should upgrade your game 😉

yes, settargetfps 😀 for example, 'settargetfps 60' locks the framerate at 60 fps, 'settargetfps 75' at 75 fps and 'settargetfps 0' releases the lock again (no limit).

I personally haven't seen any ghost blocks for more than 2 weeks playing 19.5exp with CP47. Seems like its fixed with 19.5 🤗

It's the opposite of light - it's the shadows 😉 Try lowering the Shadow Distance in settings (note: tree farms casting many shadows...)

@Roland I’m not familiar with it, but according to google it may be "War3zuk Alpha 19 All In One" 😉 (https://www.google.com/search?q=war3zuk+site%3Acommunity.7daystodie.com)

Fixed in A19.2 b3 (at last for me). Thx 😃

2 hours ago I downloaded both, the nitrogen version and the modlet and I noticed some prefab.xml s differ in the packs: RotationToFaceNorth: - xcostum_powerplant(byKam) - xcostum_ShoppingCenter_Galleria(by_Laz_Man) - xcostum_strange_cornfield(by_magoli) TotalVertices + TotalTriangles: - xcostum_Courthouse(by_Stallionsden) 😉 xcostum_Courthouse(by_Stallionsden).xml.html

If I'm not counting wrong, b3 is done already - the question is, if it will pass the tests for an exp release or not. We will see tomorrow if they'll make another build, maybe...

Sorry, I'm not a server expert, so I'm just guessing Check the server log files and compare the version number - is it really the same as the clients (did the update work correctly)? Some people reported they had done the update in a seperate folder - so they had 2 installs later, one old and one was new. Something like this...