Who is Dr. Peter Haas? I am having CTD:s

[wim95]

For whatever reason, .pex files store the login name, the computer name, and path to the original source file for Fallout 4 on the computer they are compiled on.

 

;/ Decompiled by Champollion V1.0.6

PEX format v3.9 GameID: 2

Source : C:\Users\Dr. Peter Haas\AppData\Local\Temp\PapyrusTemp\companionactorscript.psc

Modified : 2017-04-05 11:17:03

Compiled : 2017-04-05 11:17:04

User : Dr. Peter Haas

Computer : MARVIN

 

Ask the UFO4P team who logged in as "Dr. Peter Haas"

[SharraShimada]

Ah yes, my mistake. then its hardcoded into the logging system for some stupid reasons. (head>desk)

[mikvat]

I can assure everyone that I am absolutely not Dr Peter Haas. It seems that quite often there are mysterious paths in mods. Check your own papyrus logs and you will probably see some weird names. I have no idea why it´s like that and it would seem that our dear doctor belongs to the unofficial fallout 4 patch.

[SharraShimada]

I can assure everyone that I am absolutely not Dr Peter Haas.

He´s a synth!

[Webpowers]

C:\Users\Dr. Peter Haas\AppData\Local\Temp\

 

Sorry to tell you, but thats not an issue with FO4. "Dr. Peter Haas" is the current user, your windows is logged in.

Either you are Dr. Peter Haas, or you may bought the computer, with windows installed, that way (what should not happen... maybe stolen, and then sold to you?)

 

Your problem is another. Some script-mod, that affects companion affinity goes haywire. Thats the point you should start your investigation.

I just had to chime in. I have been wondering forever the background the script errors from the mysterious Dr. Peter Haas. I total agree and bet he is a coder for Bethesda and wrote or worked on the companion scripts amongst. Great find! Thank you for sharing!!

[Webpowers]

I can assure everyone that I am absolutely not Dr Peter Haas. It seems that quite often there are mysterious paths in mods. Check your own papyrus logs and you will probably see some weird names. I have no idea why it´s like that and it would seem that our dear doctor belongs to the unofficial fallout 4 patch.

Now everything makes sense. Synths took over Bethesda's coders and that's why it's so freakin' buggy. Man, this has been one of the best posts I've come across in a long time. :-)

[reconphil]

 

 

I think Dr. Peter Haas is someone who works for Bethesda. I think the original full file path gets compiled into the pex for some reason.

Nope its the user-directory of windows. He´s logged in as "dr peter haas", for whatever reason.

The log shows it, because the log-output is located there.

 

No.

 

I have Peter Haas in my papyrus log as well, and my windows user has definitely a different name.

I also have log entries with references to "C:\Users\Samson\AppData..." in the same file. Again, my user isn't called Samson.

 

Another path is "g:\_F4\Art\Raw\Scripts\IDCardReaderScript.psc". I don't even have a g:\ drive.

 

 

I also have the same issue. "C:\Users\Dr. Peter Haas\AppData\Local\Temp\PapyrusTemp\companionactorscript.psc" Line 556. I didn't log in as Haas, I didn't buy my computer from a thief (I built it) and no one else has logged on to it. I agree with the Bethesda theory. I'd like to know, however; why this is the last entry before a freeze.

 

[Brennan]

Yup same here, I'm not Dr. Peter Haas, I never have been, and I'm pretty sure I'm not a clone. I had a cat named Marvin though....

 

I'm suspecting my issues are from fiddling with my mods mid game since these issues just popped up. I'm going to try running my last quicksave through Resaver and see if that helps. Oddly the issues seem to be connected with that dratted BOS quest at Cambridge. I ignored Paladin Dance and I read that can cause issues also.

 

The last line I have is this:

(6E001E0E)].companionactorscript.OnTimer() - "C:\Users\Dr. Peter Haas\AppData\Local\Temp\PapyrusTemp\companionactorscript.psc" Line 426

Edited May 6, 2018 by Brennan

[ImpMontezuma]

I'm having the same error

[billxsand]

WHO IS HE ???