0 of 0

File information

Last updated

Original upload

Created by

OBSE Team

Uploaded by

llde

Virus scan

Safe to use

2204 comments

  1. llde
    llde
    • premium
    • 83 kudos
    Locked
    Sticky
    xOBSE 22.11 release still report as 22.10 inside the game. It's an oversight on my part as I forgot to update the version string. So if your game or mod manager report xOBSE 22.10 don't worry, it's normal and harmless

    EDIT: IT came to my attention that the last release is for some reason flagged by antivirus more then the previous one.
    I'm sorry but I can't do much to avoid this. I can assure the mod is clean, the source is public to analyze ,and the published version isn't even built locally (It's built directly by github runners). The component most flagged is the obse_loader.exe file, according to the Virus Total Report. Most antivirus on virus total don't flag these files as malicious at all.
    Most antivirus have a way to report false positives, it may be worth to try.
  2. slaymike
    slaymike
    • member
    • 0 kudos
    OBSE doesn't seem to launch from the steam "play" button anymore. Still works perfectly fine from the loader. I did a full reinstall of oblivion yesterday is it possible i set it up wrong? Extract and let the install wizard do its thing?
    1. SariusSepulcralis
      SariusSepulcralis
      • member
      • 0 kudos
      I encountered the same problem after updating to Windows 11 24H2 today. You can just start the game by using OBSELoader.exe instead of launching it through Steam, and it will work.
    2. SariusSepulcralis
      SariusSepulcralis
      • member
      • 0 kudos
      .
    3. CatsfromElsweyr
      CatsfromElsweyr
      • supporter
      • 2 kudos
      Is there something in particular you need to do to get OBSE to run on Steam now? Whenever I run it (even as admin), I get the warning to run through Steam instead of obse_loader.
    4. Giantjay
      Giantjay
      • member
      • 1 kudos
      not for me 
  3. Giantjay
    Giantjay
    • member
    • 1 kudos
    Application load error 5:0000065434 is what I'm getting
  4. twotonedearly
    twotonedearly
    • member
    • 0 kudos
    thought I'd pick Oblivion back up after seeing the remaster. Though whenever I launch Oblivion with the script extender on, it will start to load then stop and close out. I dunno what else to do about this error. 
  5. darklord4878
    darklord4878
    • premium
    • 25 kudos
    Like with the others, after updating Windows, I can no longer load xOBSE through the Steam launcher. I have to use the obse_loader.

    1. dethtrain
      dethtrain
      • member
      • 0 kudos
      Same here. It's been over a year and it seems I had the vortex installation. Since it wasn't working I ended up deleting the vortex download and manually installed the latest version of OBSE because it wasn't being detected. Running the game directly through obse_loader.exe (via the vortex UI) works now and is detected.
  6. Thistledowns
    Thistledowns
    • member
    • 0 kudos
    obse broken after windows 11 update 
    MO2 works perfectly for both OBSE and steam overlay as it has done so for as long as I can remember including on windows 10.
    You may have to set up the overlay in its settings for it to work though.
    In MO2:
    Tools -> Executables _> Turn on force load libraries.
    Click "configure libraries".
    Add a row
    On the left put oblivion.exe, on the right put the gameoverlayrenderer.dll from the steam folder.
    Turn the row on by clicking the "V" on the left, click done and it works.
  7. Jmsx999
    Jmsx999
    • premium
    • 0 kudos
    how do i fix oblivion script extender not being detected

    1. i have steam community enabled
    2. i have it BOTH installed in vortex and manually installed the right 5 files you need 
    3. i tried it through obse loader and play through steam
    4. i tried the current version off the website
    5. tried a older version of obse

    still says obse not detected 


    someone told me the new windows update broke obse might not be anything i can do and have to go back to skyrim
  8. CybrogFox
    CybrogFox
    • member
    • 1 kudos
    Hello, hope your having a good day, I cannot be sure this is related to your mod, but it seams that three of my mods are not working now and correlate to this mod as my game was running very well with all mods before this update? for instance the oblivion character overhaul requires blockhead and OBSE to work and it is currently not working and making my character say I need blockhead on her forehead, so I uninstalled an reinstalled blockhead, and still no change, but I was also getting a pop up saying that the curse of hircine was no longer working because of an OBSE problem, so I uninstalled an reinstalled OBSE and still no change to either problem I ended up uninstalling and reinstalling OBSE, Blockhead, Oblivion character overhaul and curse of hircine and still no change? I then also reinstalled an older version of OBSE and still the same problem with both mods? like I say, I have no idea if this is related to your mod and I do love your mod however I think its the most recent mod to be updated? if you have any suggestions id really appreciate it!!! thank you for all your hard work. 
    1. kiwifruitxx
      kiwifruitxx
      • premium
      • 16 kudos
      Having the same issue with the new version.  So I reverted back to version 22.11 dated Nov 2024.  Everything seems to work fine again for me.  Thanks
  9. AndalayBay
    AndalayBay
    • premium
    • 128 kudos
    There seems to be a bug introduced by xOBSE. Not sure which version. I have some old debugging code that used to work just fine, but when I enabled it again, I had to change the Scribe calls. When using Conscribe, I would register a default log and all successive scribe commands would write to that log. With xOBSE, that is no longer working. Instead it couldn't find the default log and would write to script logs instead. I discovered that if the scribe calls where in a user function, it would write to the default log as intended, so I had to define a user function just to call the scribe command.

    Latest version of xOBSE, which reports as 22.10 as noted by IIde. Windows 10.
    1. llde
      llde
      • premium
      • 83 kudos
      Could you find the exact version  of xOBSE were this beheviour start?
    2. AndalayBay
      AndalayBay
      • premium
      • 128 kudos
      I recently went back to one of my old game instances and it's the same issue there. That's using xOBSE 22.8.0. I'll check my other instances and see if I have something running an older version. I might be able to set up a new game instance, if not.
    3. AndalayBay
      AndalayBay
      • premium
      • 128 kudos
      I set up a new game instance and I can confirm that it works fine with OBSE 21.4. Now that I have the code in place, I can test with a couple of xOBSE versions. The oldest I have is 22.5.
    4. llde
      llde
      • premium
      • 83 kudos
      All version can be downloaded from github if you are interested to do a bisection
    5. AndalayBay
      AndalayBay
      • premium
      • 128 kudos
      Now I'm not sure about my test results. It's a new game so my mods haven't started yet (they require certain actions or completion of other quests), so I put the scribe commands in the main starting script where I register the log. That's working in all versions, including xOBSE 22.11.

      I can tell that I've had an issue with this for a while. One of my mods that I put into debug mode to test this had scribe commands where I was trying to write explicitly to the default log, which won't work. That's one of the mods that requires more actions and quest completions to trigger the scribe commands in other scripts.

      I wish I could talk to shadeMe about this, but he hasn't answered my messages. Could you try sending him a message?
    6. llde
      llde
      • premium
      • 83 kudos
      I can try, but I need detail on what the mod is doing
    7. AndalayBay
      AndalayBay
      • premium
      • 128 kudos
      Now I'm starting to wonder if it's a Conscribe bug or it got confused. I had some trouble unregistering a log and I've now got that sorted. So now when I turn debugging on, it will register the log properly and therefore all successive scribe statements will write to the log as they should.

      I need to debug one of my mods. I'll remove all the user functions and see if it works now.
    8. llde
      llde
      • premium
      • 83 kudos
      keep me informed
    9. AndalayBay
      AndalayBay
      • premium
      • 128 kudos
      Will do.
    10. AndalayBay
      AndalayBay
      • premium
      • 128 kudos
      I think I can declare this as a non-issue. I finally got to the point where my debug statements in regular scripts are triggering and they are writing to the default log as they should. My guess is that Conscribe got confused somehow. Doing a clean save fixed the problem.

      I'm also running 22.12.1 and the error messages I saw previously have been fixed. Everything is working fine for me.
  10. Miraak18
    Miraak18
    • member
    • 0 kudos
    Help when I either start a new game or load an old save, a message "xOBSE not installed at all. Please double check installation" would display, then my character dies and the game crashes...
  11. Vorians
    Vorians
    • premium
    • 430 kudos
    I just installed v22.12 but had to immediately revert back to v22.11 as scripting no longer recognises references to "Player" so all the Player.GetItemCount and Player.GetInCell and Player.AddItem etc. script lines were flagged as invalid.
    Also, a script line to play a BIK file was flagged invalid as the named file was deemed invalid, even though the file is in the Video folder, plays fine in-game from this script, and v22.11 is happy with the file name reference.
    1. AndalayBay
      AndalayBay
      • premium
      • 128 kudos
      I think this is related. I also upgraded and got these errors in the CSE console even if I only loaded Oblivion.esm:
      [CS]    Unable to find Function Info TESForm (0000001C) in TESConditionItem Parameter Init for INFO Form '' (0018BC9F): Quest 'Generic' (00010602), Topic 'HELLO' (000000D2), Text: "You have the eyes of a trained marksman.".
      [CS]    Unable to find Function Info TESForm (0000000D) in TESConditionItem Parameter Init for INFO Form '' (0018BCBA): Quest 'Generic' (00010602), Topic 'HELLO' (000000D2), Text: "You're a fit one. Been running a lot?".
      [CS]    Unable to find Function Info TESForm (0000001B) in TESConditionItem Parameter Init for INFO Form '' (000C459C): Quest 'Generic' (00010602), Topic 'HELLO' (000000D2), Text: "I heard you know how to move in light armor.".
      [CS]    Unable to find Function Info TESForm (0000001D) in TESConditionItem Parameter Init for INFO Form '' (000C459D): Quest 'Generic' (00010602), Topic 'HELLO' (000000D2), Text: "You look like a shrewd businessman.".
      [CS]    Unable to find Function Info TESForm (00000008) in TESConditionItem Parameter Init for INFO Form '' (0002249A): Quest 'MG05Fingers' (000224E1), Topic 'GREETING' (000000C8), Text: "You're a bold little thing, aren't you? I'm afraid you're of no use to me. Goodbye.".
      ... many more, but exceeds new post limit
      Not only was the player reference gone, but NPC references are gone as well. For example, in MG05Fingers, the NPC that says that line is now UNKNOWN. It should be Earana.
    2. llde
      llde
      • premium
      • 83 kudos
      Vorians, this is in game or in CS?
    3. llde
      llde
      • premium
      • 83 kudos
      @AndalayBay
      Sorry for the regreession, fixed.

      @Vorians
      While I fixed a regression with some issue with  some commands, I'm unable to reproduce the the Player unrecognized issue. 
      In case can you drop on discord to test if the regression fix to solve the issue?
    4. Vorians
      Vorians
      • premium
      • 430 kudos
      Sorry, I don't like to use Discord so would need a download link provided here.

      When using CSE, in the script editor when saving (recompiling), every reference to "Player" is flagged as invalid, preventing recompiling the script.
      Same applies to every reference to the stat "Fatigue", and to a video file which does exist in the Video folder.

      Example:
      If player.getInCell LeyawiinThreeSistersInn
      Player.Additem BearPelt01 1
      PlayBink "OblivionIntro.bik" 1
      playerref.forceActorValue Fatigue 100
      EndIf


      This script snippet would compile in any earlier version of OBSE, but every line will throw up an error if compiled in v22.12

      From a quick check of some other scripts, there's other failures with v22.12, such as every float variable called at the top of the script being unknown when referenced in a script block lower down.

      And if using printc, the string is deemed to be a missing item, e.g.
      printc "player found"which produces an error "Item 'player found' not found for parameter format string"

      Similarly
      PlayGroup Forward 1produces an error "Item 'Forward' not found for parameter Animation Group
    5. llde
      llde
      • premium
      • 83 kudos
      Do the DLL from this action work? https://github.com/llde/xOBSE/actions/runs/14158080658 
      Hoping you have at least a github account

      If I try your snippet with 22.12 it do have the errors on forward and the video string and the conditional expression (and these are fixed by the DLL from the action)  but I get no error about Player/PlayerRef
    6. Vorians
      Vorians
      • premium
      • 430 kudos
      I don't have a github account. There doesn't appear to be any file download link on the page you just linked to?
    7. llde
      llde
      • premium
      • 83 kudos
      downlaoding github actions need a github account.
    8. llde
      llde
      • premium
      • 83 kudos
      downloading github actions need a github account unfortunately.
    9. llde
      llde
      • premium
      • 83 kudos
      Vorians, can you check if you can download the artifact from here? https://ci.appveyor.com/project/llde/xobse/builds/51792969/job/ju52p3aristv973p/artifacts

      Note that the filenames are  wrong in this build and need to be properly changed to override (or use the -altdll option in the loader). You need to download the obse_editor.dll to test
    10. Vorians
      Vorians
      • premium
      • 430 kudos
      Thank you, yes I was able to download the DLL from there. After reinstalling v22.12, renaming the test DLL and overwriting v22.12's DLL, all the scripts which were producing errors can once again be compiled without complaint.