DOAXVV mods by KrunkDunk

[DoMopi]

The GUI works for me, as in the menu shows up. I followed all the steps of uninstalling and reinstalling and patching, but the menu shows up & I can't click any option. I know you said this happens to old mods that use the gui, but this Himalayan mod was released right after you updated the interface and the hotkeys work (I did have to fix body weights, but the swimsuit ones are the same for both DMM and Steam) so could it be a Steam only issue somehow? Either way krunk, thanks for all your work, it's a brand new version so it's prone to be buggy, don't rush the patching too much : )

[roy1102]

Mashallah brother is fixed thank you. 

 

[krunkDunk]

2 hours ago, DoMopi said:

The GUI works for me, as in the menu shows up. I followed all the steps of uninstalling and reinstalling and patching, but the menu shows up & I can't click any option. I know you said this happens to old mods that use the gui, but this Himalayan mod was released right after you updated the interface and the hotkeys work (I did have to fix body weights, but the swimsuit ones are the same for both DMM and Steam) so could it be a Steam only issue somehow? Either way krunk, thanks for all your work, it's a brand new version so it's prone to be buggy, don't rush the patching too much : )

 

Which options are you talking about?
Options in the upper left ( main gui )?

Or options for the Himalayan mod?

 

If it's Himalayan's options, those aren't actually buttons - they don't have hitboxes and don't do anything when clicked.

It's understandable that it should be possible to click them though. Maybe I can think of a way to quickly add in hitboxes.

Edited May 3, 2023 by krunkDunk

[Lunatic dawn]

3 hours ago, DoMopi said:

The GUI works for me, as in the menu shows up. I followed all the steps of uninstalling and reinstalling and patching, but the menu shows up & I can't click any option. I know you said this happens to old mods that use the gui, but this Himalayan mod was released right after you updated the interface and the hotkeys work (I did have to fix body weights, but the swimsuit ones are the same for both DMM and Steam) so could it be a Steam only issue somehow? Either way krunk, thanks for all your work, it's a brand new version so it's prone to be buggy, don't rush the patching too much : )

 

If the mod icon don't appear when main menu shows up, the hash of "[TextureOverrideSubGuiHook]" section in "sub-gui-text.ini" may not match correct value.

 

[DoMopi]

All of the main gui icons show up, and the hashes match, even the gui cursor appears when I press F4, but none of the icons work when I click.

I think the "hitbox" part might have something to do with it though, as in, wherever I'm clicking, or where the game thinks I'm clicking, is not where the gui triggers are? Maybe it's not working in my scale/resolution, I play on 1920x1080 and tried to relaunch with my main monitor only, in case it's the HDMI second monitor's scaling being wrong (I don't know much about how this works or the terms, sorry), but no luck. The gui detects all the previous mods that use it too, the only problem is I can't interact with it.

If this doesn't happen to anyone else though, it's really not an issue! I can manage with what we already have, like the $active and $id presets

 

 

[krunkDunk]

@DoMopi Did you make any changes to the guicvm hotkeys.ini ?

Quote

[Key Click]
KEY = VK_RBUTTON
KEY = XBUTTON2
condition = $costume_mods
type = hold
run = CommandList-KeyHit
[CommandList-KeyHit]
$keyDown = 1
post $keyDown = 0

Try commenting out the first two 'KEY' lines, and set something like

KEY = X

then hover over a button and press 'x'

 

Edited May 3, 2023 by krunkDunk

[DoMopi]

38 minutes ago, krunkDunk said:

@DoMopi Did you make any changes to the guicvm hotkeys.ini ?

Try commenting out the first two 'KEY' lines, and set something like

KEY = X

then hover over a button and press 'x'

 

No changes were made prior, but the X worked, and it showed something interesting:

I installed the draw text patch by the way, but something isn't drawing it in the right scale/size, so the click area might be affected too? I think this version of the gui could require different versions for each resolution (which honestly sounds like way too much work), I'm guessing most people including you play at the highest resolution, so no one had found this problem

But now that I know I can use hotkeys to use the gui, I've bound it to 0, similar to CC. I know the purpose of the gui is to not have to use any hotkeys, but one key is much better than 3 or 4, so it works with at least the older mods.

Edited May 3, 2023 by DoMopi

[krunkDunk]

@DoMopi

Well, I don't know why the default Keys for [Key Click] didn't work...

 

Maybe take a look at this debug display I cobbled together... You can try the default keys again and see if it shows the $keyDown and $keyHit / $hitCount variables changing etc...

You can just extract it into the Mods folder or _guicvm if you like

debugDisplay.zip

 

As for the Himalayan sub-gui-text.ini, you could screenshot or copy and paste the [CommandList-DrawText-1] section and the [Resource-SubGUI-TextParams] section. Maybe I can see if it's a problem there.

 

[iVileLight]

I'm having a lot of trouble here over at my end. Can anyone help?

[kassarc16]

I think you're using a mod with a graphical menu without having the required items installed for the menu.

[krunkDunk]

@iVileLight

That's CostumeCustomizer, I don't know what's going on exactly... maybe some CC mod folders are missing .ini files. But I can't tell with just warnings especially when they are cut off.

Edited May 8, 2023 by krunkDunk

[DoMopi]

On 5/3/2023 at 6:33 AM, krunkDunk said:

@DoMopi

Well, I don't know why the default Keys for [Key Click] didn't work...

 

Maybe take a look at this debug display I cobbled together... You can try the default keys again and see if it shows the $keyDown and $keyHit / $hitCount variables changing etc...

You can just extract it into the Mods folder or _guicvm if you like

debugDisplay.zip 1.04 kB · 3 downloads

 

As for the Himalayan sub-gui-text.ini, you could screenshot or copy and paste the [CommandList-DrawText-1] section and the [Resource-SubGUI-TextParams] section. Maybe I can see if it's a problem there.

 

Sorry for my absence. Only the hover debug flag triggers it seems...

 

as for himalayan, here's the text:

Spoiler

[CommandList-DrawText-1]
x = window_width
y = window_height    
Resource\guicvm.drawtext\Text = ref ResourceTextFile
Resource\guicvm.drawtext\Params = ref Resource-SubGUI-TextParams
run = CustomShader\guicvm.drawtext\FormatText
run = CommandList\guicvm.drawtext\SetGSPS
run = CustomShader\guicvm.drawtext\RenderText
run = CommandList\guicvm.drawtext\UnSetGSPS
[Resource-SubGUI-TextParams]
type = StructuredBuffer
array = 1
data = R32_FLOAT    -0.98 -0.6 -0.60 -0.98     1.0 1.0 1.0 1.0     0.0 0.0 0.0 0.3      0.0 0.0          0 0          0         2.5
;                       rectangle bounds           rgba text            rgba BG        border h/v      h/v anchor,  text-align, font scale

 

[krunkDunk]

@DoMopi

Lunatic updated the Himalayan mod, but you were still using the old version.

The problem in the old version is this... because I changed something in guicvm 1.4.1

Quote

x = window_width
y = window_height

In order to get the text scaling consistently, x & y need to be hardcoded.

For the modder, it's not important what values you use... just any 16x9 resolution & adjust "font scale" after fixing the x & y values.

Drawing the text via ShaderFixes\help.hlsl has a scaling operation that uses both x & y ini params (window width & height) and "font scale" from TextParams section.

Normally, using window_width & window_height would make the text appear smaller the larger your resolution and vice versa. (Check it out with F1 help notification)

 

As for the mouse clicking... I have no idea why the VK_RBUTTON wouldn't work for you.

Does your mouse use a usb connector or PS2? - I don't have a PS2 connector mouse to test...

Or do you have some mouse software for macros that may be modifying mouse input?

 

With the debug display, you can test out different [Key Click] keys in _guicvm\hotkeys.ini

Try setting only one Key in [Key Click] section

or try something from https://learn.microsoft.com/en-us/windows/win32/inputdev/virtual-key-codes

 

Edited May 16, 2023 by krunkDunk

[iVileLight]

On 5/2/2023 at 8:24 PM, krunkDunk said:

 

Which options are you talking about?
Options in the upper left ( main gui )?

Or options for the Himalayan mod?

 

If it's Himalayan's options, those aren't actually buttons - they don't have hitboxes and don't do anything when clicked.

It's understandable that it should be possible to click them though. Maybe I can think of a way to quickly add in hitboxes.

 

[krunkDunk]

it's self explanatory...

[andyleo456]

[mod] Photo Frame Mod seems to be invalid

at least in my dmm it is currently unavailable

[krunkDunk]

On 7/25/2023 at 11:54 AM, andyleo456 said:

[mod] Photo Frame Mod seems to be invalid

at least in my dmm it is currently unavailable

 

Are you using this version?
https://www.loverslab.com/files/file/22760-photo-frame-mod/

 

There are some quirks to prevent displaying at bad times / unintended overwriting of textures that share the same hash.
It's off by default after mods are reloaded or when the game starts.

It will be disabled when a menu ( location, pose, swimsuit ) is opened.

To turn it on, use the hotkey "Ctrl F" or use GUICVM.

[andyleo456]

9 hours ago, krunkDunk said:

 

Are you using this version?
https://www.loverslab.com/files/file/22760-photo-frame-mod/

 

There are some quirks to prevent displaying at bad times / unintended overwriting of textures that share the same hash.
It's off by default after mods are reloaded or when the game starts.

It will be disabled when a menu ( location, pose, swimsuit ) is opened.

To turn it on, use the hotkey "Ctrl F" or use GUICVM.

Yes, I am using this version and the latest GUICVM

Ctrl F cannot be used in the photography interface

[krunkDunk]

@andyleo456

 

Uh, maybe there is a misunderstanding on how / when it can be enabled.

It replaces the original photo overlay - so that it will be included in the game's photo ( rather than simply drawing a UI overlay which is not included in game photos )

The replacement mod won't be enabled while a menu is opened because of hash conflicts that may make using the game UI difficult.

 

1. Use one of the game's original photo overlays

2. Close game menus before the mod can be enabled

• photo filters / overlay menu
• locations menu
• poses menu
• swimsuits menu
• maybe other menus I haven't tested

 

 

If this is how you've been trying to operate the mod, I have no idea what could be wrong. I've tested it with each of the standard resolutions, and without any shaderoverrides from a d3dx.ini.

 

Are you using a custom resolution? Maybe some other mod is causing a conflict? Do any other mods work?

[andyleo456]

@krunkDunk

I understand how to use it, thank you for your help

 

[lpTT]

Can you help me solve this problem

[lpTT]

6 minutes ago, lpTT said:

Can you help me solve this problem

[krunkDunk]

[SSR] (_KAS) Unlock_Heart [krunkdunk] 1.0

2023-09-14, Unlock Heart, Common body, KAS body, SSR, topless, barebreasts

https://www.loverslab.com/files/file/29165-ssr-_kas-unlock_heart-krunkdunk/

 

[krunkDunk]

An oldie, SSR - Aikujaku / Benikujaku / Peacock Kimonos for Nyotengu and Tamaki

 

 

 

[krunkDunk]

The original un-modded meshes someone requested.

Marie's and Honoka's can be found in their character episodes where their swimsuits fall off.

Kasumi's was from the malfunction version of her Destiny Child outfit. I don't have the outfit, but did a frame analysis years ago during a PvP event. It has probably been updated and the body may have changed...

 

OriginalBodyMeshes(BarbieDoll).zip