One of the issues is it's only doing half of what it should be doing. Currently, this is only loading UI's in the old SUITE engine, where it should be loading UI's using both the SUITE and GAMEFACE engines. the "/loadskin" command, and using the "load UI skin" window do the same thing. Use "/loadskin Default 1" to load the EverQuest default skin.īut my ui runs just fine, since it's a cosmetic feature mainly and not a change in functionality to any element (as in targeting rings, spell icons, and window borders, etc).
#EVERQUEST 2 UI RESOURCES LOADING SLOW WINDOWS#
Your XML files are not compatible with current EverQuest files, certain windows may not perform correctly. This also generates the following warning (in red colored type): This newui_mod folder contains mainly tga files with a couple of xml files and ini files that are used in place of the corresponding files in the default UI. For me this custom folder (which I call "newui_mod') resides in the uifiles folder. ↑ “ I may be totally confused, but the options window, general, 'load UI skin' is how I substitute any custom UI files into the default UI, etc. There is currently no way to use a custom UI in the new engine because it refuses to recognize any folders other than the "default" one. When one uses either (or both) the /loadskin and the /ui reloadhtml commands in order to load a custom UI of any of the windows ported over thus far to the new engine, it doesn't load them. The only files I have modified at this point are the QuantityWnd.html, StoryWnd.html and SelectorWindow.html which are contained in the "windows" subfolder. Inside both the Default, and EmilariUI folder, I have the three subfolders: assets, img, and windows.
#EVERQUEST 2 UI RESOURCES LOADING SLOW UPDATE#
Now, in an attempt to update my UI for the new Gameface engine, we have the 'Uiresources' folder (and subfolders) in addition to the 'Uifiles' folder, so I've also got:
This is the ideal behaviour for the new engine as well as NO custom UI has ever customized every single file that makes up the entire UI. If I'm using the 'EmilariUI' skin, it pulls all my custom windows, then pulls all the default windows for anything I haven't customized. So, with the old SUITE engine, the way Custom UI's work is that you create a new folder in your uifiles folder, add any XML files you have customized to it, and then whatever is missing is pulled from the EverQuest -> Uifiles -> Default directory.Ī player then uses the /loadskin command (or the "Load a Skin" window - opened via a button in the Options Window) to load the custom UI.
0 kommentar(er)
