kinggath / WorkshopFramework

Redesign of the FO4 Workshop Scripts
54 stars 9 forks source link

Feature Request - Workaround for interior settlement object bug with Room Bounds #73

Closed amcghee1 closed 2 years ago

amcghee1 commented 3 years ago

I've tried to get in touch a couple of other ways but I found this project here which might be better. Sorry, not being impatient just seeing progressively better contact options :)

I'm looking to get a feature added to WSF to address the problem with room bounds @kinggath posted about here: https://forums.nexusmods.com/index.php?/topic/6183538-baffled-i-am-haunted-by-invisible-objects-at-internal-settlements/page-5

I'm building an interior settlement in the CK & this bug has killed it.

I'm having CK compiler issues so I'm hoping something can be incorporated into WSF possibly as an MCM option to perform the disable / enable workaround, presumably as a manual MCM option or detecting the player being in workshop mode in an interior cell.

Do note though I've seen an issue where if this is done while the item is highlighted in workshop mode the placed object will appear but have no collision. The object will need disabled & re-enabled outside of workshop mode to fix this. I need to do more testing but as long as the item isn't highlighted it appeared to work fine.

I currently use WSF & WS+.]

kinggath commented 2 years ago

I'm not sure how I never saw caught this- hopefully you ended up solving this!

For next patch I've added the script "WorkshopFramework:ObjectRefs:InteriorWorkshopRoomboundHelper" that people can put on their workbench's to solve this for their mods.

amcghee1 commented 2 years ago

No problem bud. I tried the script without success sadly, Thuggysmurf passed it over as well. I did however find another workaround.

I found you can avoid the issue by deleting the room bounds altogether & instead using occlusion planes, the “old-fashioned” way of doing it. I’ve not seen much use of these planes in other mods or Bethesda cells and I saw on some tutorials that it’s advised they not be used in favour of the room bounds but nobody has ever gone into why that I’ve seen. Have you any experience with using planes yourself?

I’ve been working on and off on a V111 settlement expansion & using these planes seem to give the same performance as room bounds (but this is on my one test machine). This also means the V111 elevator doesn’t start vanishing since it’s odd bounds can extend past the room bounds there when modding the cell.

That’s awesome you’re adding the script to WSF 😊.

Cheers, Andy

From: kinggath @.> Sent: 25 April 2022 16:45 To: kinggath/WorkshopFramework @.> Cc: amcghee1 @.>; Author @.> Subject: Re: [kinggath/WorkshopFramework] Feature Request - Workaround for interior settlement object bug with Room Bounds (#73)

I'm not sure how I never saw caught this- hopefully you ended up solving this!

For next patch I've added the script "WorkshopFramework:ObjectRefs:InteriorWorkshopRoomboundHelper" that people can put on their workbench's to solve this for their mods.

— Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkinggath%2FWorkshopFramework%2Fissues%2F73%23issuecomment-1108741469&data=05%7C01%7C%7Cac27b33dc1464202d37808da26d28198%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637864982806981132%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=uMCMZ7zvzV6YbXnRhOMEA3G5TKv78lKev0y9dSvqLoc%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJTUYVKTKDXQVKDBZUPQTYLVG24WNANCNFSM43EZTJDA&data=05%7C01%7C%7Cac27b33dc1464202d37808da26d28198%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637864982806981132%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pAz6HUmtO7GaKuC3azwMZS6if%2FPCm3yd2ujjpZDViE4%3D&reserved=0. You are receiving this because you authored the thread.Message ID: @.**@.>>