Issues when using Ultimate ASI Loader alongside DXWrapper about dxwrapper HOT 8 CLOSED

1. Update the code for UALs newer features (possibly the most ideal)

What features of UALs are missing from dxwrapper?

2. Allow for ASI loaders to be used outside of dxwrapper when the LoadPlugins option is set to 0

There is nothing in dxwrapper that prevents other ASI loaders. In fact, you can even using dxwrapper to load other UAL tools. You can use the LoadCustomDllPath to load tools like the Ultimate ASI Loader.

Also, you can use the Ultimate ASI Loader to load dxwrapper. Just put dxwrapper.dll and dxwrapper.ini in the scripts folder.

from dxwrapper.

What features of UALs are missing from dxwrapper?

Specific stuff, such as allowing the fusion overloader for GTA IV.

There is nothing in dxwrapper that prevents other ASI loaders. In fact, you can even using dxwrapper to load other UAL tools. You can use the LoadCustomDllPath to load tools like the Ultimate ASI Loader.

I just had a problem in particular with using an external UAL with LoadPlugins = 0. Kept getting error 126 when launching the game for every ASI.

Also, you can use the Ultimate ASI Loader to load dxwrapper. Just put dxwrapper.dll and dxwrapper.ini in the scripts folder.

Really? I thought it was only with the .asi version. I'll have to try this out.

from dxwrapper.

You can rename dxwrapper.dll to dxwrapper.asi. Dxwrapper does not care what extension it is using.

from dxwrapper.

You can rename dxwrapper.dll to dxwrapper.asi. Dxwrapper does not care what extension it is using.

Oops, I just realized I accidentally formatted the reply incorrectly, and my reply was grouped in the quotes. Edited it to fix it.

from dxwrapper.

You can rename dxwrapper.dll to dxwrapper.asi. Dxwrapper does not care what extension it is using.

Update, According to some of the friends I talked to in the IV modding community, I think the reason why dxwrapper may have been working poorly is due a conflict with another mod that seemingly does not like other wrappers/injectables. It seems like I have fixed that problem, but just to be sure, I'll further test to make sure everything goes well.

Also, make sure to check out my edited post. I made some formatting mistakes and forgot to check markdown before posting so only one section of the message showed normally.

from dxwrapper.

Thanks.

As far as the missing features, can you give me more specific details? Is there a list somewhere? What exactly is "allowing the fusion overloader for GTA IV"?

I just had a problem in particular with using an external UAL with LoadPlugins = 0. Kept getting error 126 when launching the game for every ASI.

This sounds like a bug with the other UAL. Dxwraper literally just attempts to load the other dlls. It could be that dxwrapper hooks something that the other UAL's want to hook. That sounds like an issue with the other UAL's not handling this gracefully. Furthermore, since I just hotfix the hooks by writing to memory they should be able to hook on top of my hook, allowing for both hooks.

from dxwrapper.

Thanks.

As far as the missing features, can you give me more specific details? Is there a list somewhere? What exactly is "allowing the fusion overloader for GTA IV"?

To my understanding, when FusionFix 2.0 released for GTAIV, Ultimate ASI Loader had an update to work alongside FF to essentially establish a modloader for the project. I think there may have been more features, but this one currently is the biggest notable one introduced in recent updates.

After a bit of messing around, I found that the game seemed to act as normal after installing it on a less modded copy of the game. As described before, there's a specific mod (IV SDK .net I think?) that tends to have a problem with other wrappers/injectors when there are mutiple at once, and it caused for dxwrapper to just not at all work as intended. It's a known problem with that project, and the creator has absolutely no clue as to what may be happening.

This sounds like a bug with the other UAL. Dxwraper literally just attempts to load the other dlls. It could be that dxwrapper hooks something that the other UAL's want to hook. That sounds like an issue with the other UAL's not handling this gracefully. Furthermore, since I just hotfix the hooks by writing to memory they should be able to hook on top of my hook, allowing for both hooks.

That makes sense, but now that I know it wasn't dxwrapper, nor UAL, I think it's safe to close the issue.

from dxwrapper.

when FusionFix 2.0 released for GTAIV, Ultimate ASI Loader had an update to work alongside FF to essentially establish a modloader for the project.

Ok, I see. I am not really trying to add custom code for things like this. I will let Ultimate ASI Loader handle that.

I think it's safe to close the issue.

Ok, closing the issue.

from dxwrapper.