Burakin

Hey all, I updated to 17.4 and the latest Ravenhearst, but the newly genned worlds look way different again. Are we using a new pimp Rwg? I must admit the extremely large bands of biomes of the previous were a bit much, now however the biome sizes are a little smallish again. Worse for me however is the towns. We had the nice socket system with some stretched out cities and stuff that sorta looked naturally grown. Yes there were some illogical height changes and some weird empty spots etc but now we just have 'rounded squares' towns all made of perfect square blocks again. I can see the dirt pathing is improved but the towns are largely boring now. Am I doing something wrong? Is there I way I can at at least improved the town part of the RWG? As I'm posting:" I knew this mod is hard, I played it before but damn - I'm getting absolutely destroyed on first horde night (day 17). The walls don't hold up to good and the wooden spikes take a lot of work to make (wood harvest) but don't last very long. Am I Missing something here? (14+x bloodmoon warrior difficulty) edit: Been experimenting with Nitrogen some - the maps look nicer from top down - got me an ok one now I think so ill go and see how it works out 'on the ground'

Seems to run 'fine' now. Most likely was the EAC problem. For others that might visit (if it's duplicate please remove) Problem: 7d2d ravenhearst mod 4.3 (fully updated) get stuck loading or at the menu screen. It (eventually) results in a crash. Analysis: Even though EAC is OFF in 7d2d Mod launcher it appears the EAC ON from the 7d2d launcher (orig) gets priority. Solve: Start 7d2d regular with it's launcher and turn EAC off there. Then use 7d2d mod launcher to start ravenhearst mod. On a plus note: I managed to survive my first day first at first play at this (warrior diff, 150% loot, no loot respawn, no airdrops)

mmm I seem to be making some progress. Even though EAC is off in the mod launcher it was checked in the launcher menu for 7d2d itself. So I turned it off there. Also started 7 days to die 'regular', which went fast and smoothly, to lower the automatically detected 'high' video settings a bit. I'm getting to an active start menu now. Gonna check if I can actually start a game now. Updates as I muddle along.

Hey, I Thought I'd give this mod a try (since alpha (21)17 is gonna take a little while longer ). I'm having issues getting it to run though. I installed 7d2d mod launcher as advised (v 1.0.5.2) I deleted 7 days to die from steam (to start clean - I ran valmod before). I renamed (for savekeeping) my old 7 days to die C:whatever folder I reinstalled 7d2d beta 16.4 I checked the correct making of a new c:whatever 7daystodie directory. I used 7d2d mod launcher to install ravenhearst 4.3 normal 7 day edition. I ran the pre-sync (damn that takes long) Starting the game It recognised my screens wrong (middle screen which is main display gets recognised as 2 - left instead of 1 middle) - but that I figured out. Starting the game takes a LONG time. It crashed a couple of times. Full clean boot, minimal programs running got me to the start menu with the mouse highlighting the mouse-over menu option. I tried to go into options (as physcial ram was MAXED out - running on 8gb here - 7 days to die was taking about 6.5) Crash again. output error log says: ========= OUTPUTING STACK TRACE ================== RtlLookupFunctionEntry returned NULL function. Aborting stack walk.<Missing stacktrace information> ========== END OF STACKTRACE =========== **** Crash! **** I got the crash files available if thats of use to anyone trying to figure it out. B