This mod will never be ported to console, unless silverlock team manage to port F4SE somehow. This mod is an F4SE plugin and won't work without it. That's why it is not possible to put this mod to bethesda.net.
If you have beta-version of game and love to use this mod, but it is not available for beta yet - you have two options: 1. Roll back to non-beta game version and play until mod will be available for beta 2. Play on beta, but without mod. In either case - please, DON'T write your complains about mod not-working in beta and continiously ask 'WHEN???!!!". Mod will eventually be updated OR there will be a notice if I decide to stop support this mod.
Thanks to all, who support me by donating. It really motivates. Sadly, PayPal is not available for me anymore. If you know how to send cryptocurrency or how to addd funds to my steam account - you're welcome!
For those who can't make mod running or mod stopped running for some reason or some functions of mod doesn't seem to work: 1. Find out your game version (main menu->settings->lower-right corner) 2. Check, that installed F4SE AND mod match your game version. 3. If step 2 is ok, then post f4se.log anf place_plugin.log from Documents\My Games\Fallout4\F4SE dir. To be sure the logs are latest, remove them before starting game, they should be recreated. Put your logs between [ÂÂÂÂÂspoilerÂÂÂÂ][ÂÂÂÂ/spoilerÂÂÂÂ] tags if you have any mods installed, otherwise your post will be too big and unpleasant looking. For those, who have CTD: 1. check if CTD still happens if Fallout4 run without f4se. If it does - it's not a problem of this plugin. 2. If you still think, that this plugin is cause of CTD, then, please, post in bugs section, be more informative: what did you do, when CTD happen, in what place it happened. Also post your mods load order and send me you last save before CTD. Thank you.
I will not answer to such posts, if there was no required info provided. They will be deleted.
Very good and helpful comment by VIitS: One thing I did a while ago is set the permissions for my steamapps\common, Documents\my games\Fallout4, and AppData\Local\Fallout4 folders (as well as all subfolders/files) to Full Control for Users(xxxxx\Users).
It means I have never had to run xEdit/CK/f4se/Fallout 4 in administrator mode, and never have to worry about old log files blocking new ones from being created.
So yeah after making sure I've got the latest F4SE [https://imgur.com/hN5pz0l] and the latest Place EveryWhere [https://imgur.com/qzf7GGY] and both installed correctly. I still get this Error [https://imgur.com/vk5jIvr] randomly when I wasn't getting it before. Here are my logs.
Disabling the PlaceInRed.dll stopped the issue, but now I'm left without a mod I rely upon. Do we know why the incompatibility is now happening when it wasn't before?
f4se has updated again and now before playing it say " a mod you have installed contains a DLL plugin that has failed to load correctly. if a new version of fallout was just released, the plugin needs to be updated. please check mod's website for updates. this is not a problem with F4SE.
place.dll: disabled, incompatible with current version of the game."
I'm getting a notification that the dll is not supported and tells me not to launch the game. Nevermind. I deleted the updated version in my list and downloaded the new version from your page and all is good again. Don't know why but it worked.
I'm also having this issue, but deleting and redownloading does not resolve. I wasn't getting this problem at all, then all of a sudden it just started happening out of no where.
No errors for me, just a CTD whenever I move into a previously unrendered-in-this-session area. If I hold still, no crash. If I remove just this mod, no crash. Alas, I love this mod SO much.
Thanks bro. Just started getting back into FO4 when a file integrity issue forced me to update to NG, this mod is critical for making nice settlements w/ Rebuild and others.
8803 comments
This mod is an F4SE plugin and won't work without it. That's why it is not possible to put this mod to bethesda.net.
1. Roll back to non-beta game version and play until mod will be available for beta
2. Play on beta, but without mod.
In either case - please, DON'T write your complains about mod not-working in beta and continiously ask 'WHEN???!!!".
Mod will eventually be updated OR there will be a notice if I decide to stop support this mod.
Crypto:
BTC: bc1q70uuls8pk5krcfqu8ut6zn23tsz84m04vjaxz0
ETH: 0xd65Ef38b299474A312E5b5D9D4FF9680fAe9CCd3
ZEC: t1e15kArgp44P6a7JHxVyWLwcA5oaLh64tZ
Steam: thedeadmoroz
1. Find out your game version (main menu->settings->lower-right corner)
2. Check, that installed F4SE AND mod match your game version.
3. If step 2 is ok, then post f4se.log anf place_plugin.log from Documents\My Games\Fallout4\F4SE dir. To be sure the logs are latest, remove them before starting game, they should be recreated. Put your logs between [ÂÂÂÂÂspoilerÂÂÂÂ][ÂÂÂÂ/spoilerÂÂÂÂ] tags if you have any mods installed, otherwise your post will be too big and unpleasant looking.
For those, who have CTD:
1. check if CTD still happens if Fallout4 run without f4se. If it does - it's not a problem of this plugin.
2. If you still think, that this plugin is cause of CTD, then, please, post in bugs section, be more informative: what did you do, when CTD happen, in what place it happened. Also post your mods load order and send me you last save before CTD.
Thank you.
I will not answer to such posts, if there was no required info provided. They will be deleted.
One thing I did a while ago is set the permissions for my steamapps\common, Documents\my games\Fallout4, and AppData\Local\Fallout4 folders (as well as all subfolders/files) to Full Control for Users(xxxxx\Users).
It means I have never had to run xEdit/CK/f4se/Fallout 4 in administrator mode, and never have to worry about old log files blocking new ones from being created.
f4se.log: https://justpaste.it/bao17
place_plugin.log: https://justpaste.it/aivb2
place.dll: disabled, incompatible with current version of the game."
KING.