File information

Last updated

Original upload

Created by

CreeperLava

Uploaded by

CreeperLava

Virus scan

Some files not scanned

2866 comments

  1. CreeperLava
    CreeperLava
    • supporter
    • 2,534 posts
    • 71 kudos
    Locked
    Sticky
    I'm tired of answering questions that are already in the FAQ. Or helping people that didn't follow the instructions. RTFM before posting anything !
    If your post is removed, you know why.


    New milestone reached ! Thank you for your continued support !


    If you have a legitimate issue not answered in the FAQ :
    - Make sure it's not answered in the FAQ (see description)
    - Make sure it's not answered in the tutorial
    If both the above don't cover your issue, please open a bug report in the Nexus bug section :
    - Send screenshots and the installer's debug log, if applicable. See how to upload a log and make a diagnostic.
    - If the issue is texture-related, send a save game where it can easily be seen.
    - Give a precise description of the issue you are having by answering the following questions :



    Join us on Discord to discuss your issue. We're more active there than on Nexus. Link !

    0.- Base game source (DVD / Origin / Steam)
    1.- Base game in vanilla state (unmodded) (y/n)
    2.- BW DLCs installed (y/n and, if so, how many?)
    3.- Other mod(s) installed (y/n and, if so, which one(s)?)
    If yes, were these other mods installed before or after A.L.O.T ?
    4- SweetFX, ENB, ReShade installed (y/n and, if so, which one?)


    Spoiler:  
    Show
  2. magnetite
    magnetite
    • member
    • 5 posts
    • 0 kudos
    Hi,

    I've noticed that when I installed a lot for ME3 that it didn't add the following line to the GamerSettings.ini file.

    [D3DDrv.D3DRenderDevice]
    MaxTextureSize=4096

    By default the Coalesced.bin file value is 2048, but I believe without the modded value, the full resolution of the 4096x4096 textures won't be applied.
    1. CreeperLava
      CreeperLava
      • supporter
      • 2,534 posts
      • 71 kudos
      That setting doesn't do anything. Rest assured, we'd have noticed by now :).
  3. SundialPaisley
    SundialPaisley
    • member
    • 5 posts
    • 0 kudos
    I have a quick question that I haven't seen on the FAQ yet, and that is the process of uninstalling a said mod that was part of the installation process. In particular, I'm referring to the "optional character tweaks" section, I want to remove the default female Shepard tweak but I haven't had any luck. I loved the mod, and the mod author did a fantastic job, yet I wanted revert back to the vanilla model.

    I've tried disabling the mod but the custom textures were still present in the game. I know that the fault here is my own, since the tweak was clearly stated optional, however I am just curious if there is a way of disabling the mod to revert to the vanilla default face.

    Thank you.
    1. Mgamerz
      Mgamerz
      • premium
      • 762 posts
      • 26 kudos
      Textures are a one way installation. Short of reinstall the vanilla textures (which we don't provide or support), you will have to restore your game using the a lot backup/restore feature or nuke the install and start again.
    2. SundialPaisley
      SundialPaisley
      • member
      • 5 posts
      • 0 kudos
      Gotcha, thank you for the reply.
  4. DaedalusXV
    DaedalusXV
    • member
    • 9 posts
    • 0 kudos
    Hello, I cannot find an answer in the FAQ about my problem.

    I followed every step and installed a lot for ME3. Most of the textures are working, but i have some of them that turn black when i'm close to them, just like i have a problem with Ashley's hair fading when the camera is near her face. There is no problem when the camera is afar.

    Would you be nice enough to help me, please? Thank you in advance.
    1. CreeperLava
      CreeperLava
      • supporter
      • 2,534 posts
      • 71 kudos
      Please upload a diagnostic and post the link here. https://imgur.com/sflQV1U
    2. DaedalusXV
      DaedalusXV
      • member
      • 9 posts
      • 0 kudos
      Thank you for your answer.
      https://mega.nz/#!oZgX0RxB!Ilc7a53swXV7SJbgloItm9nB9aTWYJ7ArykuwrumwGM
    3. CreeperLava
      CreeperLava
      • supporter
      • 2,534 posts
      • 71 kudos
      "Diagnostic reports some files appear to have been replaced after textures were installed:"
      There you go. Don't install content mods or DLCs after A.L.O.T. I'm afraid you're going to have to reinstall everything.
    4. DaedalusXV
      DaedalusXV
      • member
      • 9 posts
      • 0 kudos
      I didn't install anything after ALOT. I installed only what was in the a lot installer, (a lot, the update and the optionnal texture mods), then i started the game. Thanks anyway i'll try to reinstall everything.
    5. CreeperLava
      CreeperLava
      • supporter
      • 2,534 posts
      • 71 kudos
      Might be Origin's auto update then. Disable it, it tends to overwrite modded files because it doesn't recognize them, thus creating problems like the ones you saw.
    6. DaedalusXV
      DaedalusXV
      • member
      • 9 posts
      • 0 kudos
      I'll try that thank you
    7. SidewinderISR
      SidewinderISR
      • member
      • 1 posts
      • 0 kudos
      Hey, I have the exact same problem. However, not only did I not install anything after a lot, origin's update have also been turned off before I even installed the game. Is there any way to fix this, besides reinstalling (which still may not work)? thanks!
    8. CreeperLava
      CreeperLava
      • supporter
      • 2,534 posts
      • 71 kudos
      Upload diagnostic and log through the installer, send the links here. See pinned post above.
    9. Mgamerz
      Mgamerz
      • premium
      • 762 posts
      • 26 kudos
      Inability to read EXP001 localization files means it is pirated. We do not support pirated installations. Additionally this is really obvious because the folder is named Mr. DJ.
  5. luccasfs
    luccasfs
    • member
    • 40 posts
    • 0 kudos
    Great mod! But my M7 Lancer is all black, no textures at all, everything else works fine, I've Game + all DLC on origin.
    1. CreeperLava
      CreeperLava
      • supporter
      • 2,534 posts
      • 71 kudos
      This has been fixed in one of the recent updates to MEM. You'll need to reinstall A.L.O.T using the latest version of the installer. Just launch it, let it autoupdate and click install ME3.
    2. luccasfs
      luccasfs
      • member
      • 40 posts
      • 0 kudos
      It worked! Thank you very much, I'm new to modding Mass Effect so I didn't knew that the software update would change anything on the installation
  6. ebg2465
    ebg2465
    • premium
    • 281 posts
    • 4 kudos
    CreeperLava If I use MEM to install a lot for ME3 can I still use ME3Explorer for Conditional Edits and to Autotoc?
    1. CreeperLava
      CreeperLava
      • supporter
      • 2,534 posts
      • 71 kudos
      No. You don't need to autotoc, MEM does it already. Not sure what conditional edits are ?
    2. Mgamerz
      Mgamerz
      • premium
      • 762 posts
      • 26 kudos
      Conditionals should be fine, autotoc is fine too from me3explorer (do not do it before installing a lot as it will attempt to unpack your DLC). Just avoid using any of their texturing tools as they are not compatible.
    3. ebg2465
      ebg2465
      • premium
      • 281 posts
      • 4 kudos
      Thanks!
  7. igrlans
    igrlans
    • member
    • 11 posts
    • 1 kudos
    Hello! In changelogs i see Version 2018.6.4
    But i cant donload it, i find only Version 2018.6.3. Any tips?
    1. CreeperLava
      CreeperLava
      • supporter
      • 2,534 posts
      • 71 kudos
      It's in beta for now. You can participate to the testing by enabling beta mode in the installer.
    2. igrlans
      igrlans
      • member
      • 11 posts
      • 1 kudos
      Ty for the answer!
  8. MagnusThorek
    MagnusThorek
    • member
    • 344 posts
    • 2 kudos
    I finished (another) playthrough and it went all smooth except for the shadows rendering like plain and crispy polygons once in a while, mostly on the floors, like if there was a big source of light behind the character (and thus the bugged shadows were following me while walking around). This usually occurred when the game executable reacher or crossed the 2GB of memory.
     
    Usually, it was just a matter to restart the game and everything returned to normal but now, while exploring the Citadel DLC a bit further, I'm having issues with these shadows again inside the Armax Arsenal Arena to a point of being almost unplayable, as it becomes very difficult to see enemies at distance.
     
    After digging others' issue reports, someone on EA's forums said to delete/rename the GamerSettings.ini. I did and it solved, however, it was like I was playing without any texture improvements whatsoever. Even the effects provided by the SweetFX preset I've been using became less intense.
     
    By analyzing both files, the old that apparently is modified by A.L.O.T. during installation and the new one re-created by the game, I noticed that the lines below were removed:


    TEXTUREGROUP_World=(MinLODSize=256,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_WorldSpecular=(MinLODSize=256,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_WorldNormalMap=(MinLODSize=256,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_AmbientLightMap=(MinLODSize=32,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_ShadowMap=(MinLODSize=1024,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_RenderTarget=(MinLODSize=2048,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_Environment_64=(MinLODSize=128,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_Environment_128=(MinLODSize=256,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_Environment_256=(MinLODSize=512,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_Environment_512=(MinLODSize=1024,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_Environment_1024=(MinLODSize=2048,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_VFX_64=(MinLODSize=32,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_VFX_128=(MinLODSize=32,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_VFX_256=(MinLODSize=32,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_VFX_512=(MinLODSize=32,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_VFX_1024=(MinLODSize=32,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_APL_128=(MinLODSize=256,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_APL_256=(MinLODSize=512,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_APL_512=(MinLODSize=1024,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_APL_1024=(MinLODSize=2048,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_UI=(MinLODSize=64,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_Promotional=(MinLODSize=256,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_Character_1024=(MinLODSize=2048,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_Character_Diff=(MinLODSize=512,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_Character_Norm=(MinLODSize=512,MaxLODSize=4096,LODBias=0)
    TEXTUREGROUP_Character_Spec=(MinLODSize=512,MaxLODSize=4096,LODBias=0)
    MaxShadowResolution=2048
    MinShadowResolution=64
    ShadowFilterQualityBias=2
    ShadowFilterRadius=5
    bEnableBranchingPCFShadows=True
    DepthOfField=True
    Bloom=True
    QualityBloom=True
    ParticleLODBias=0
    SkeletalMeshLODBias=0
    DetailMode=2

    I've added them back, manually, the shadows bugged again. Then I tried to remove a couple of them, individually, restarting the game after every attempt, but without success.
     
    What could it be?
    1. Godstrail
      Godstrail
      • member
      • 1 posts
      • 0 kudos
      I have the same problem but not wityh the shadows, only with NPC faces, except for core-people, like Hackett, Vega, Kaiden and the likes.

      This is what it looks like: https://imgur.com/a/QN4CtKu
      THanks man! I'll do that. I've had some issues with my hard drove lately after I installed it so it may have f***ed with my game.

    2. CreeperLava
      CreeperLava
      • supporter
      • 2,534 posts
      • 71 kudos
      "After digging others' issue reports, someone on EA's forums said to delete/rename the GamerSettings.ini."

      Yeah, don't do that. That is essentially disabling the high resolution textures. Without the changes from this file, textures are capped at vanilla resolution.

      Now, as to both of your problems, it's most likely caused by installing a mod or DLC after A.L.O.T. I'd suggest reinstalling your game and mods, this time following the instructions on the A.L.O.T page.
  9. Demiaxes
    Demiaxes
    • member
    • 35 posts
    • 0 kudos
    I was unable to find an answer for this, so I'll ask here:
    Does this edit default fem-shep's complexion? Specifically, does it make her eyebrows thinner? I just started a game using the default female appearance and noticed her brows are considerably thinner and there's like, a small line on her right side of where the brow used to be filled to. Its been a while since I installed all the mods for this game, but I'm almost positive that I haven't used any mods to change the default complexion. I didnt use any texmod textures either.
    (you can see it here https://i.imgur.com/O469hR8.jpg)
    1. CreeperLava
      CreeperLava
      • supporter
      • 2,534 posts
      • 71 kudos
      It does edit it, yes, with a vanilla friendly texture (should be CDAMJC's).
  10. th3kracken
    th3kracken
    • supporter
    • 11 posts
    • 0 kudos
    I'm having an issue where the game crashes, but only when I'm on the Normandy. The only other mods I have are John's MEHEM, the extended Anderson convo mod, and the "Hair Mods as DLC" mod, all of which I added before I installed a lot. When I run the game with just those mods, there are no issues. When I install a lot, the game won't let me load onto the Normandy. I've tried all of the fixes on the FAQ (windowed, adding command line, disable motion blur, etc.) but the it is still crashing. Also, it ONLY happens on the Normandy. I'm able to load into the Citadel or on Palavan just fine, but not the Normandy. I love this mod, but after installing and disabling and repairing the game and reinstalling about 4 times, I'm ready to give up. I'm sorry if I'm missing some obvious answer or if you've answered this a million times.

    Also, to answer the questions at the end of the pinned comment,
    -I bought the game on Origin,
    -Citadel, Leviathan, From Ashes, Omega, and extended cut DLCs installed (along with some of the alternate appearances/added weapons dlcs from Origin),
    -Other mods I have are John's MEHEM, Anderson Convo, and Hair Mod DLC (all installed before a lot)
    -no other shading/texture mods (except for the recommended additional texture mods shown in the a lot installer)
    1. CreeperLava
      CreeperLava
      • supporter
      • 2,534 posts
      • 71 kudos
      Does the game only crash if you load a savegame to the Normandy or alsoif you access it from the citadel ?
    2. th3kracken
      th3kracken
      • supporter
      • 11 posts
      • 0 kudos
      Both, so whenever I enter the Normandy or load onto the Normandy (I had a previous save on the Normandy (pre a lot) so that's why I could see if it worked).
    3. CreeperLava
      CreeperLava
      • supporter
      • 2,534 posts
      • 71 kudos
      Can you come to the Discord and post a diagnsotic there ?
  11. charlottek
    charlottek
    • member
    • 18 posts
    • 0 kudos
    Sorry to bother you again! Just having a small issue that I can't figure out: Similar to user s1357924680 below, the M7 Lancer is showing up completely black for me. But I have a legitimate copy of the game on Origin and the full diagnostic came up completely normal (link: https://vps.me3tweaks.com/alot/logviewer?logid=bac3d78b37c939454b799f49d98b9ff4&type=diag). This only happened after I reinstalled ME3. I've reinstalled both A.L.O.T. and the game multiple times and it's the same issue. It's strange because it was showing up just fine earlier today (before I decided to reinstall) and I did not change anything prior to or after installation, and all content mods were installed before A.L.O.T. Is there anything I can do?
    1. CreeperLava
      CreeperLava
      • supporter
      • 2,534 posts
      • 71 kudos
      Hmm, that's odd. I see nothing wrong with the textures, it's weird. 2 things :
      - Can you upload a screenshot showing the problem ?
      - After that, can you try to install the following textures with MEM (see description for a guide) : https://mega.nz/#!ww0nhJqR!rQJnZggsjvlm9Yq_6JLAjw6GTlZM3q4qW1pFlGCTMWc
      They're the vanilla textures of the M7. I'm curious to see if that fixes it.
    2. charlottek
      charlottek
      • member
      • 18 posts
      • 0 kudos
      Screenshots: https://imgur.com/a/nAIYA7X

      Huh, installing the vanilla textures did nothing, the gun's still entirely black.

      EDIT: Okay, so I tried multiple reinstalls, checking the gun after installation, content mod installation, coalesced edits, then finally texture installation. The texture was fine up until I installed A.L.O.T + the addons so I think the cause might lie in there somewhere. I'll redownload A.L.O.T and install it on a vanilla ME3 and see what happens.
    3. CreeperLava
      CreeperLava
      • supporter
      • 2,534 posts
      • 71 kudos
      Might be a content mod that edits the gun's mesh somehow. Perhaps EGM ? What other content mods are you using ?

      I'm definitely curious as to the result of your vanilla ME3 installation, as that will eliminate a lot of possibilities.
    4. charlottek
      charlottek
      • member
      • 18 posts
      • 0 kudos
      Alright so it's definitely A.L.O.T, not caused by a content mod (if you still need that list though, let me know). Vanilla install, didn't touch any files whatsoever. All I installed this time around was the main file and the update, I even downloaded those off the nexus tonight so everything is brand new. And unfortunately the gun still turns black after installation of the mod. Sorry, I thought this would be a simple fix, I don't mean to make you break your back trying to figure out the problem.
    5. Mgamerz
      Mgamerz
      • premium
      • 762 posts
      • 26 kudos
      Please come to the discord.

      Edit: We can reproduce this issue and are investigating the cause.
REPORT BUG
Top