AR34X

So it crashes even before the addon / texture is loaded by clicking on the dropdown menu?
You can try looking in "mainfx_errors.txt" located in (...\Binaries). I don't know/think if a faulty addon will show up there but I know bugged normal and specular textures do at least... had some issues with a couple of those a while back. You can also have a look in "VX-addon.log" (...\Logs) and see if you can identify any sort of error / fault there.
Hope it helps.

Here it is. I've tested it and it works on my end at least. was a bit more work than I initially thought because PSP refused to do batch-export... 😐
 

You're welcome! Weird that you can't have 1x & 4x versions in the same folder... that shouldn't be an issue as long as everything named properly. I have a couple of 1x/4x-mixed folders... You can only use one at the time (complete set of either 1x/2x/4x), though. "Universal Skin System"/"Customizable Skins" offers more flexibility when its come to mixing resolutions. FYI if you're using Hook5 you should also rename the _pass-files accordingly so that they reference the relevant skins. Like this for 4x "mod_Male_White_Body_pass.txt", "Male_White_Body_pass.txt" for 1x etc.

Greetings!
In "_level_definition.txt" there's a bunch of different parameters that you can edit such as "ambient_intensity" and under [sunlight] there's an intensity as well. Then there's the different light sources like omnilights and spotlights (type = spotlight & type = omnilight). Some people, myself included, prefer to use the "[include]" function and under there specify a separate .txt-file* with all omni-/spotlights. Then there's also stuff like cubemap/skybox that also influences lighting (well, kinda everthing does in the level def... 😉).
*I would bet "_ceiling_spots.txt" is just such a file.
In the case of your bed spotlight: first thing you can do is a search for spotlight and see if all/the one you want have "enable = true". If your lucky the person who made the definition even named it to something like [BedSpot] or [Spotlight_Bed]...
I recommend  a text editor like Notepad++, although you can make do with regular Notepad, it's just easier and more convenient with something like Notepad++ if your going to do a lot of editing, especially when the files grow longer/bigger.
ps. in the folders "!DAY" & "!NIGHT" you'll most likely have alternative level definitions which you can choose from/load using the H5-user interface (H5$-feature).
By the looks of it I'd say you're using the night definition so you could simply try loading level def. in the !NIGHT-folder/replacing _level_definition.txt with the one from there. ALWAYS MAKE BACKUPS of the file you're about to replace so that you can revert changes if something goes wrong.
It's weird that things/settings change if you haven't changed anything...
Hope it helps.

Yeah, I name all my models starting with [ ! ], [ _ ] and other symbols that makes them all turn up earlier in the list so those base models aren't mixed in with the ones I actually use...

This is a slightly edited copy+paste for H5-basic installation instructions that I saved while MG was still around... I believe I used this when installing. Hope this helps.

"                                    Hook5 simple setup / install guide 02.12.2019
After two days of struggle I finally made Hook5 (basic version) to work with TK17 VX. And since there's no comprehensive guide covering its installation I've made this simple one. 
Hope that helps!
    Setup:
1.     Download the recent basic version of Hook5 from modsgarden.cc, put it into "TheKlub17\Binaries" folder
2.     Download all additional Hook5 files from the project's Patreon, put it into "TheKlub17\Binaries" folder. 
    Only difference is "Lua binaries and examples.zip" package, it should go to the TheKlub17 main folder.
    There's also "Lua binaries and examples_31.05.2019.zip", that I've just installed after "Lua binaries and examples.zip". 
    
    >>>> DO NOT overwrite original lua51.dll file if you use TK17 V10 Beta 2 (VX) <<<<
    
3.     Download Hook5 StarterContent.
4.     Alter the 2 paths to envmaps in "TheKlub17\Binaries\main11.fx" file, for default game install directory they should look like: 
    "C:\TheKlub17\Mod\ActiveMod_hook5data\envmaps\EveningField.dds". This will prevent Customization Room and many other environments in the game from going dark.
5.     Launch your game in DirectX mode (you can pick OpenGL or DirectX in the game's launcher) from "TheKlub17\Binaries\TK17_Launcher.exe" file.
Troubleshooting:
1.     If your models have green eyes, change their Eye Specular to "No Eye Specular" in Customization Room. Some toys and rooms will have green elements and AFAIK 
    there's no fix for that - you should use Hook5 toys (if there are any) and rooms (there are some available right from the start). 
    If you want a more permanent solution to the green eyes bug in VX, check a comment section below this post!
2.     If your game crashes during a room selection, delete "R_h5p_Photostudio_Ps" folder from "TheKlub17/ActiveMod" folder.
    It's a part of Hook5 StarterContent but it somehow caused crashes on my PC.
3.     If you have any problems relating DirectX, check the comment section below this post.
By user wapitawg @ MG "
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Note: You can also use "R_h5p_Photostudio_Ps" from "hook5_basic_version 25.06.2017" if you want (.../ActiveMod) and that won't cause any crashes.
Your "Binaries Folder" should have these files and folder present:
- FILE: main11.fx
- FILE: d3d8.dll
- FILE: GFSDK_SSAO.win32.dll
- FILE: PhysX3Common_x86.dll
- FILE: PhysX3Cooking_x86.dll
- FILE: PhysX3_x86.dll
- FILE: NvHairWorksDx11.win32.dll
- FILE: d3dcompiler_47.dll
- FOLDER: hook_data11
"hook_data11"-content (Working H5-Basic 3.07.2019):