Fallout 4

File information

Last updated

Original upload

Created by

xi784

Uploaded by

xi784

Virus scan

Safe to use

6 comments

  1. foxhound525
    foxhound525
    • premium
    • 8 kudos
    Does this mod do anything if you aren't using creation club content?
  2. busybobo
    busybobo
    • premium
    • 0 kudos
    nvm,
  3. Raw117
    Raw117
    • supporter
    • 0 kudos
    Thank you, works well. 

    When I exited the vault I didn't receive any of the creation club items or quests. Is this normal?

    Thanks!
  4. TheModHead
    TheModHead
    • member
    • 0 kudos
    Massive tip to anyone using this, or just using DLCs on FO4 in general!
    Far Harbor breaks Diamond City and the Valentine Detective Agency!
    To fix this, get FO4Edit and run "FO4EditQuickAutoClean.exe", then select DLCCoast, and wait for it to get done. This removes the unneeded edits it makes, which break those two locations.
    You can then copy DLCCost.esm from Pancake FO4 into FO4VR, and it should run without issue.

    If you want to restore the unedited version to Pancake Fallout 4, you can find it in "Fallout 4\Data\FO4Edit Backups", just delete everything after esm, ensuring it's name is DLCCoast.esm
    I have yet to test it with the cleaned version, but I assume it won't cause any issues.
  5. Solrac421
    Solrac421
    • supporter
    • 0 kudos
    hi is this mod still usable? also is it compatible with luxor's hd texture pack as well as DLCVR - Fallout 4 VR and DLC standalone bug fixes?
  6. xi784
    xi784
    • premium
    • 1 kudos
    FAQ:
    What did this at all?
    It will give you a more up-to-date database at all.
    Some example to this. The data structure of F4 and F4VR is exactly the same, but F4VR is on the state of 2018 without any corrections which are already done to F4flat.
    So let´s say we´r using any mod, who defines something that an NPC should do, and the script is brocken in 2018 F4VR package, but fixed in 2019 in F4flat and on the other hand not touched by UFO4P (they touched over 2/3 of all scripts) - that mod could break the game because of the defect script.
    And thats all.

    Will all this resault in better performance?
    Maybe there are slightly improvments, but thats not my focus.

    What about the DLC_cc_VRsupport and the Pip Boy Skins?
    At the moment i need a dirty workaround. Pip Boy will be visivble in your inventory, it was needed because i cant get him visible in the Armor Workbench without this. I need to remove the flag "non-playable"

    What about VR-workshops.
    Short and Sweet - they will never work with F4VR in this way.
    I've spent a lot of time to see if any functions are called that don't exist in F4VR. The VR-workshops are the only mods I've found that call classes that don't exist in F4VR.
    Without updating the Fallout4VR.exe, these will not work without any workaround, which would mean that they would probably have to be completely rescripted.

    Automatron Workbench?
    Is not touched in this package, but invest some time on it.
    The Workbench on it self is not brocken and works pretty well - the main problem is, that F4VR disables by default any animation who registered to the Player, there is no 1st or 3rd person problem at all, the animation is stil not playing.
    The Workbench is scripted to wait for the animation to be done, it waits of a "recall" - hey i did it, replace the left arm - but this never happens.
    So what could we do? - Maybe there´r two way:
    First: complety remove the animation on it self from the Workbenchscripts an call back its done, update arm left.
    Second: unregister the player from the Workbench/Animation, so they the animation can played in the "open World" - you can take a look on the "Vaultdoorscript" and "Vaultdoorscript_V81" from the Fallout4VR - main.ba2.
    Normaly you press the button in F4flat, you get focused on the Vault door and watched how the get openend and the animation is finished.
    In F4VR - you push the button from everywhere, the vault door opens complety unaddressed from you and you could do anything between.

    Conclusion:
    I´m not Bethesda and i will not give any support of things they brocken by Fallout4VR themself.
    But please, feel free to post criticism, bugs or anything else. I'm sure I'll take a look, but for the most part this won't be a bug of this package.
    Also, I can't provide support for the CC packages and remember, if you want CC content, buy it.
    I could provide the fixed esm files, they would be useless without the associated files - but i don't want any copyright issues so you have to build these yourself. :)