Jump to content

Recommended Posts

Posted

Hi and sorry for my eng. So I am trying to install 2 dynasty sets - dynasty and Blue dynasty, and they both have utx files with same names (f.e. ct1FDwarf.utx, because I am testint it on FDwarf) but textures are different. I want both of these sets so I changed Blue dynasty utx file names to ct1BFdwarf.utx and changed line in armorgrp from

Dwarf.FDwarf_m008_u 1 ct1FDwarf.FDwarf_m008_t201_u

to

Dwarf.FDwarf_m008_u 1 ct1BFDwarf.FDwarf_m008_t201_u

but if I try to equipt it L2 crashes. If I just replace the textures ct1FDwarf.utx -> ct1FDwarf.utx and leave armorgrp untouched everything works fine and dynasty turns blue. Can anyone help me and tell how to change armorgrp or rename files that both sets can work?

Guest Elfocrash
Posted

you have to make the textures by scratch in a new utx which you will name and create via unreal.you can't justrename the .utx and make it work eveny is you change the grp files.

Guest Elfocrash
Posted

One more q: If I add exported textures from blue dyn to normal and change this part:

Dwarf.FDwarf_m008_u 1 ct1FDwarf.FDwarf_m008_t201_u

or it didnt work either?

 

no cuz thsi exist only on the blue dyn utx not to the normal one

Posted

These 2 utx (blue and normal) are identical except for textures. All names are same, so I ask if I can extract these textures from blue one, import to normal dyn utx but rename from

FDwarf_m008_t201_u  to FDwarf_m008_t201_uBlue f.e. or FDwarfBlue_m008_t201_u or stm.

and path to this texture will be

Dwarf.FDwarf_m008_u            1  ct1FDwarf.FDwarf_m008_t201_uBlue

and for normal just

Dwarf.FDwarf_m008_u            1  ct1FDwarf.FDwarf_m008_t201_u

no? :/

Guest Elfocrash
Posted

These 2 utx (blue and normal) are identical except for textures. All names are same, so I ask if I can extract these textures from blue one, import to normal dyn utx but rename from

FDwarf_m008_t201_u  to FDwarf_m008_t201_uBlue f.e. or FDwarfBlue_m008_t201_u or stm.

and path to this texture will be

Dwarf.FDwarf_m008_u            1  ct1FDwarf.FDwarf_m008_t201_uBlue

and for normal just

Dwarf.FDwarf_m008_u            1  ct1FDwarf.FDwarf_m008_t201_u

no? :/

 

Look.The ct1FDwarf_m008t201_uBlue means that it reads the ct1FDwarf.utx the blue upper body.

You need a new .utx with another name

Guest
This topic is now closed to further replies.


  • Posts

    • fixed the flickering , if you noticed to an other specific page please let me know
    • And Discord: https://discord.gg/3aYqWNqb
    • Ofc: https://discord.gg/3aYqWNqb
    • You can find some H5 skins shared in old L2 modding Discords, but most of the higher‑quality ones are either paid or come bundled with full client edits. I usually mix in commissioned work and whatever I can patch myself. On a side note, I fund a lot of these commissions by selling off game items through instant sell cs2 skins, which has been a quick way for me to get some cash for projects.
    • There is no need for gRPC in this case, even tho originally it was gRPC based but since we don't need it to be bi-directional, we switched to simple http requests for the web calls and SSEs for the data streamed from the server. There are distributed locks in place to precent race conditions between actions that can happen between multiple web instances and the server.   Local models can also be slow depending on the model, and most external models can actually be faster than local ones if you use Flash 2.5 or something along those lines. I am running on 512GB of Unified Memory on my Mac Studio M3 Ultra so the speed of the local model for a small model is pretty good but I tested it with Gemini too and it works equally as fast and in some cases faster. The way it works is that I'm using pgvector (one of the benefits of moving to Postgres) to search the data and see what the player can see etc and there is some batching of the next few actions for 2-4 seconds for the user until the next LLM request fires. The batching also includes branching on logic so if they for example fall under some HP they will move to kiting instead of attacking or maybe they heal etc.   Everything is authed and permission-based. The server and the backend of the frontend have secure communication between them, either with a symmetric key (not recommended for production) or a certificate (the recommended way), so there is no worry. It's all tied to the account's access level, etc., so nobody can make an action that they normally wouldn't be allowed to do. Even the MCP is token-based, and there are prompt injection protections in place. The MCP is audited, and every mutation needs confirmation. The admin area is only accessible to the admin account anyway so normal users can't access it.  
  • Topics

×
×
  • Create New...

Important Information

This community uses essential cookies to function properly. Non-essential cookies and third-party services are used only with your consent. Read our Privacy Policy and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..