Modding Help Need Help With This Error...

Discussion in 'Starbound Modding' started by agmoyer, Jan 8, 2017.

  1. agmoyer

    agmoyer Cosmic Narwhal

    So I did fresh install of Starbound and checked to make sure it was working then after I tried to put one of my mods in the mod folder and now it crashed... Normally I can just check the log myself and find what the problem is because it nromally would tell me it failed to load a file from my mods folder or there was a duplicate name. Not this time, instead I get this error "sehTrampoline".

    I have no clue what to do about this. Anyone know what this is?


    Code:
    [23:49:15.772] [Info] Root: Preparing Root...
    [23:49:15.842] [Info] Root: Done preparing Root.
    [23:49:15.842] [Info] Client Version 1.2.1 (windows i386) Source ID: f15286d545debbcdb4e5e73680a1805ad29308da Protocol: 729
    [23:49:15.842] [Info] Root: Scanning for asset sources in directory '..\assets\'
    [23:49:16.857] [Info] Root: Scanning for asset sources in directory '..\mods\'
    [23:49:16.858] [Warn] Root: Unrecognized file in asset directory 'mods_go_here', skipping
    [23:49:16.864] [Info] Root: Detected asset source named 'base' at '..\assets\packed.pak'
    [23:49:16.865] [Info] Root: Detected unnamed asset source at '..\mods\warframe_crossover'
    [23:49:16.865] [Info] Root: Detected unnamed asset source at '..\assets\user'
    [23:49:16.865] [Info] Loading assets from: '..\assets\packed.pak'
    [23:49:18.032] [Info] Loading assets from: '..\mods\warframe_crossover'
    [23:49:18.048] [Info] Loading assets from: '..\assets\user'
    [23:49:20.715] [Info] Assets digest is 37d4cf49f5c184faaa837abfb86237d032666748d6c0a2c522bfb19cb9442746
    [23:49:20.740] [Info] Root: Loaded Assets in 4.88975 seconds
    [23:49:20.797] [Info] Application: Initializing SDL Video
    [23:49:20.867] [Info] Application: Initializing SDL Joystick
    [23:49:21.392] [Info] Application: Initializing SDL Sound
    [23:49:21.756] [Info] Initialized Steam services
    [23:49:21.778] [Info] Application: Creating SDL Window
    [23:49:23.260] [Info] Application: Enabling VSync with late swap tearing
    [23:49:23.371] [Info] Application: Opened default audio device with 44.1khz / 16 bit stereo audio, 2048 sample size buffer
    [23:49:23.603] [Info] OpenGL version: '3.3.11672 Compatibility Profile Context' vendor: 'ATI Technologies Inc.' renderer: 'ATI Mobility Radeon HD 4200 Series' shader: '3.30'
    [23:49:23.871] [Info] Application: initialization...
    [23:49:23.973] [Info] Root: Loaded Configuration in 0.0520652 seconds
    [23:49:23.994] [Info] Application: renderer initialization...
    [23:49:24.204] [Info] detected supported OpenGL texture size 8192, using atlasNumCells 128
    [23:49:24.341] [Info] detected supported OpenGL texture size 8192, using atlasNumCells 64
    [23:49:24.423] [Info] Root: Loaded ImageMetadataDatabase in 6.35555e-06 seconds
    [23:49:25.300] [Info] Application: main update loop...
    [23:49:25.315] [Info] No subscribed user generated content
    [23:49:25.675] [Info] Root: Loaded NameGenerator in 0.332836 seconds
    [23:49:41.267] [Info] Root: Loaded PlantDatabase in 15.5925 seconds
    [23:50:08.005] [Info] Root: Loaded ProjectileDatabase in 26.7146 seconds
    [23:50:26.756] [Info] Root: Loaded ObjectDatabase in 61.4135 seconds
    [23:50:27.751] [Info] Root: Loaded MonsterDatabase in 19.7276 seconds
    [23:50:27.791] [Info] Root: Writing runtime configuration to '..\storage\starbound.config'
    [23:50:27.927] [Info] Root: Loaded StagehandDatabase in 0.170563 seconds
    [23:50:28.089] [Info] Root: Loaded VehicleDatabase in 0.161173 seconds
    [23:50:28.352] [Info] Root: Loaded PlayerFactory in 0.263451 seconds
    [23:50:28.591] [Info] Root: Loaded NpcDatabase in 1.80962 seconds
    [23:50:28.850] [Info] Root: Loaded VersioningDatabase in 0.226133 seconds
    [23:50:28.850] [Info] Root: Loaded EntityFactory in 0.497381 seconds
    [23:50:38.164] [Info] Root: Loaded ParticleDatabase in 9.31487 seconds
    [23:50:52.823] [Error] Fatal Error: Access violation detected at 01690CF3 (Read of address 00000008)
    [0] 10674ba Star::captureStack
    [1] 10676f2 Star::fatalError
    [2] 1062e92 Star::SignalHandlerImpl::sehTrampoline
    [3] 15b2e9b <lambda_e284610c0e9ebf57602b633cd66f66dc>::<lambda_invoker_cdecl>
    [4] 6c7441b8
    [5] 6c7c3cf9 SDL_LogCritical
    [6] 6c81af7e SDL_LogCritical
    [7] 771c9bc3 RtlDestroyQueryDebugBuffer
    [8] 771c9b92 RtlDestroyQueryDebugBuffer
    [23:50:53.808] [Info] Root: Loaded MaterialDatabase in 24.9589 seconds
    [23:50:53.827] [Info] Root: Loaded TerrainDatabase in 0.018261 seconds
    [23:50:55.713] [Info] Root: Loaded BiomeDatabase in 1.88607 seconds
    [23:50:55.781] [Info] Root: Loaded LiquidsDatabase in 0.0600116 seconds
    [23:50:56.111] [Info] Root: Loaded StatusEffectDatabase in 0.330458 seconds
    [23:50:58.373] [Info] Root: Loaded DamageDatabase in 2.26116 seconds
    
     
  2. Inf_Wolf14

    Inf_Wolf14 Parsec Taste Tester

    Sadly, access violation errors are nigh, impossible for most modders to read.
    Only by looking at the source code for the game could we determine the source of the error from the log

    At very least, in this case, you are only loading one mod: "warframe_crossover".
    What does the .metadata for your mod look like? (Invalid metadata throws access violations to my recollection...)

    Otherwise, all we know is something in the mod doesn't work, and the only real way to find it is to scour the assets till you find it. :/
     
  3. agmoyer

    agmoyer Cosmic Narwhal

    As it turns out last time I updated the mod I didn't have a metadata file since I didn't need one then. So now the question is how do I get one? And where do I go from there?
     
  4. Inf_Wolf14

    Inf_Wolf14 Parsec Taste Tester

    You can just make a metadata file yourself.

    If you have file extensions enabled on Windows, rename a random file as
    Code:
    .metadata.
    
    -or-
    Code:
    _metadata
    
    And it should work.

    Empty the file and from there, just copying the fields from another mods metadata and changing the information works well.
     
  5. agmoyer

    agmoyer Cosmic Narwhal

    Thank you now it works, all I need to do now is fix my crafting table then update the mode and go from there.

    Just double checking this is how I did it if it is right or wrong...


    Code:
      "author" : "AGMoyer",
      "description" : "Warframe Crossover.",
      "friendlyName" : "Warframe Crossover",
      "link" : "http://community.playstarbound.com/resources/warframe-crossover.2738/",
      "name" : "Warframe_Crossover",
      "version" : "1.4"


    I named it "metadata" and used Notepad++ to add the code I found online (If I even needed to I don't know ) then saved the file as "lua" but typed ".metadata" at the end. Now in properties for it says "METADATA File (.metadata)" for Type of File. I am guess this was the right way The part I typed inside could've been pointless for all I know but I guess it is okay in the end?
     
  6. Inf_Wolf14

    Inf_Wolf14 Parsec Taste Tester

    Yup, honestly whatever works for you to get the file type.
    If the type is METADATA, then you did good.

    Just make sure your metadata has the opening and closing brackets in the file.

    Code:
    {
      "author" : "AGMoyer",
      "description" : "Warframe Crossover.",
      "friendlyName" : "Warframe Crossover",
      "link" : "http://community.playstarbound.com/resources/warframe-crossover.2738/",
      "name" : "Warframe_Crossover",
      "version" : "1.4"
    }
    




    (For the sake of clarity, adding the appropriate metadata file fixed the access violation error, yes?)
     
    agmoyer likes this.

Share This Page