-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"oculus is not a valid mod jar" possible Connector incompatibility? #524
Comments
Not oculus OR connector. see: mod 'I See Lava' (iseelava) 1.1.7 requires any version of fabric, which is missing! |
As I said in the main post, those mods are not missing. What I suspect is that because oculus fails to load, it prevents the loading of mods after it, which causes other mods to break due to dependency. Downgrading oculus fixes the crash, further proving that it's not a missing dependency issue. |
Oculus loads for me on connector. Do you have all connector dependencies? |
[03Jan2024 16:12:07.837] [main/ERROR] [net.minecraftforge.fml.loading.moddiscovery.ModDiscoverer/SCAN]: Locator {mods folder locator at C:\Users\Admin\AppData\Roaming.minecraft\mods} found an invalid mod file net.minecraftforge.fml.loading.moddiscovery.ModFileInfo@6579c3d9 |
are you installing oculus without embeddium? |
Yes, I have all the dependencies. If I didn't, the game would crash
regardless of Oculus version installed.
Oculus 1.6.13 loads fine, as my original post said. The newer version, for
which I made this issue, is now archived, it seems. I don't see it on CF
any longer, anyway. Are you sure you installed the newer version when
everything loaded fine?
…On Tue, Jan 2, 2024, 11:09 PM Xplodin ***@***.***> wrote:
Oculus loads for me on connector. Do you have all connector dependencies?
Like forgified fabric api and connector extras?
—
Reply to this email directly, view it on GitHub
<#524 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE7XE5T3JPHLYGWCFLBHOMDYMTRYPAVCNFSM6AAAAABBIM3UKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZUHA2TIOBQHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Yes, my crash is from the same versions as in description "embeddium-0.2.16+mc1.20.1.jar", oculus 1.6.13a, forge 1.20.1-47.1.81 from neoforge site. Now I'm using oculus-mc1.20.1-1.6.13.jar without "a" suffix and have no such crushes. |
Also getting this issue with 1.6.13a. Can also confirm that 1.6.13 works just fine. |
Seems they messed up the jar for oculus on latest release. 1.6.13 works pretty well. |
Also having this issue. In my case, the latest version of oculus causes Forge to load NO mods, which is really interesting. Basically just launches a vanilla game with forge installed and tells me the oculus jar is "Not a valid jar" or something, and lets me go back into the game. Works fine with the version I used before, all mods load fine. |
See #525 |
Help me figure out which version of oculus requires embeddium I had a problem with version 1.6.15a, I tried to roll back 1.6.15, but he says he only needs a higher version. How do you even understand this ahahah Mod ID: 'oculus', Requested by: 'embeddium', Expected range: '(1.6.15,)', Actual version: '1.6.15' |
Minecraft Version
1.20.1
Oculus Version
1.6.13a
Sodium Version
embeddium 0.2.16
Operating System
Windows 11
What is your GPU?
i forget, but it's unrelated
Java Version
also not sure, probably 17?
Reproduction Steps
Crash Report file and latest.log
Additional context
The original crash mentioned that I was missing some mods related to Connector, and also said that Oculus was an invalid mod jar. I double checked that I had the missing dependencies, and then tried downgrading Oculus. The crash did not occur after downgrade.
The text was updated successfully, but these errors were encountered: