oxnxdragon666

I think that the robots are supposed to shut down permenently when you reactivate Star Control. If you listen to the holotape in the Star Control build and the error message on the Star Control terminal, you get the impression that Star Control was meant to deactivate robots that went haywire (which is all of them at the moment).

For some reason my pipdoys screen has gone very dark and there appear to be one or two shadow obstrcucting the screen. If it helps this is my Load Order This should be a link to a screenshot, because I'm apparantly not allowed to post images in the forums. https://postimg.org/image/mjosyteu1/

I never had these issues with other Bethesda game being stealth patched and breaking various mods, mainly because I mainly moved to pc after Skyrim had been fully updating. Also Bethesada can stealth patch at will on pc because unlike consoles they don't have to wait for Sony and Microsofts permission to upload an update (so the "pc master race" ends up being Bethesda's patch beta testers for the "console peasants").

I think FO4SE will upadate about approximatly 72 hours after a patch.

If you haven't noticed yet the third person controls are also somewhat buggy, for example I infrequently ran into a bug that locked the direction I could move to left and right regardless of what direction I moved the right stick (I use a gamepad). This would persist unitil I actually took my thumb of the right stick and stopped moving, so it wouldn't suppirise me if the camera was buggy too.

Been having trouble with 2 outfits that haven't been updated since the new Bodyslide muscle sliders where released and it's causing a large amount of cipping in game that I can't see in Bodyslide for one of the outfits. The clipping would also become a lot worse when my character is moving and I've tried updating both outfits sliders with no success, is there anyway to fix this.

For me it's the other way aound, sometimes the conveyor belt doesn't appear to move but the items on it still move.

I'm not using any weapon retexture mods and I had this issue before installing realisting guns and bullets. Could this be cause by the legendary modifaction and awkcr, because they're the only two mods I have that alter weapons before installing realistic guns and bullets. The weapons that suffer this issue are currently: The Supmachine GunAssaault RifleCombat Shotgunpossibly the minigunHavan't really tested the automatic recievers for the Combat Rifle, Pipe clip loaded weapons and 10mm Handgun have the same issue. If it help with the automatic Plasma and Laser weapons or the Gatling Laser, it's just the ballistic automatics.

Bethesda is probably using the pc base to test the patche incase they introduce any bugs in them and doesn't want to upset Microsoft with another broken patch, for example Skyrim had about 3 patches that broke the Dragons. I don't think anyone is going to forget the infamous 1.02 patch for Skyrim that caused the Dragons to fly backwards. Besides on PC Bethesda can introduce patches instantly, while on consoles they have to wait for the patches to be approved by Sony and Microsoft before they can be updated.

For some reason firing automatic ballistic tanks my framrate hard, if I fire them for about 5 seconds drops the framerate down to 12 and even short burts drops the fps by about 20. Though FO4 doesn't really have a stable fps to begin with while sprinting, espercially in the Boston area which will automaticly drop the fps to about 40. My pc specs are: Nvidia Geforce GTX 980TI 6GB MSI gaming editionIntel Core I7-4790 3.60hzWindows 1016GB Ramgame is installed on a 7200rpm exteranl hardrive. my load order is below if that helps

I'm having similar crashes whenever I go exploring the main Boston.

try reducing shadow distance from high to medium, apparently having shadow distance on high tanks the framerate.

@esorbma87 are you sure it isn't just the area around the Boston ruins that are crashing, because that's what keeps happening to me.

Isn't there a conflict between the Automatron and pipboy map ui mods that causes the crash, because they're not compatible with the new map marker added by the dlc. as for me, I'm having ctd when I try to go to explore the main Boston ruins.

Shouldn't official dlc esm's go before mod esm's?