Jump to content

Depressoexpresso04

Citizen
  • Posts

    7
  • Joined

  • Last visited

Profile Information

  • Preferred Pronoun
    He/Him/His/Himself

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Depressoexpresso04's Achievements

Citizen

Citizen (2/12)

0

Reputation

  1. I found the issue. It was a mod by Xtudo. Specifically the LOD fix on the Vigilant patches by Xtudo. The file only contains textures but for some reason it also disables all map LOD. I didn't realize it was there yesterday, but I saw it now, removed it, and my LOD is working properly again. So ultimately this was all my fault. But yeah thank you for being patient with me and helping me.
  2. I'm going to try that now, although with my level of knowledge I don't think I'm going to succeed. But yeah this does seem like ACMOS is screwing with the LODs. All right this is definitely an issue with ACMOS. It doesn't matter what LODs we generate, which files we use, or what value we set. ACMOS just doesn't let Vigilant worldspaces have the proper map. I tried to do it with Map object LOD set to 16, with only Vigilant's LOD files being active, and yet nothing showed up in the map. Btw though, how does one go about opening the .LOD files included in some mods. IIRC those are the ones that contains the LOD rules for said mod, aren't they?
  3. So essentially, I should copy the Node values from the BTOs supplied by Vigilant itself, to the LOD32 BTO generated by DyndoLOD. Am I correct or am I still missing something? I'm sorry if I appear too oblivious. This is my first time mesing with DyndoLOD doing anything past adjusting some values or just adding a couple rules. Also I made sure that nothing is overwriting the files provided in the link, and that the map object level is set to 32. Map's still empty.
  4. The map still looks the same, without any objects in it. I've deleted all the output for that world from my output folder, and made sure that the .bto you made is not being overwritten by anything else. Any ideas as to what is happening? Also I would like some clarification on the making my own LOD32 BTO file. More exactly, copy the Node blocks from which file to which? And would that actually help the objects show up in the map? I am using ACMOS, if I didn't make it clear previously.
  5. I tried to use it with the .bto file you supplied. I put the files into my Dyndolod Output folder, but the map was still empty. https://ibb.co/5wdZyTC Then I tried to generate Dyndolod again but only for the Vigilant worldspaces. All the files were only mere KBs in size, and this is how the map looks. https://ibb.co/G4SFx23H The only thing generated was that one structure in the top right. All the relevant logs ( I think they are ) are uploaded here. https://limewire.com/d/E8PEf#TZHDzcpbxQ
  6. I'm sorry this was completely not enough knowledge on my part. Once I actually added a proper mesh rule for it in Dyndolod, I got the results I wanted. And yeah, the model doesn't actually show up in the base mod, at least as a map object. Now I have one more question though. Why do Vigilant and it's worldspaces never generate proper LOD32 files? I tried to generate them, but I've only got LOD16 files. I'll dig up the logs and post them soon, but I just wanted an opinion from you.
  7. This might be a dumb question, but I can't get the Numidium model from Dac0da to show up in either actual LOD or the map. There was a mod which helped with that but that mod has been removed nexus by the author and they just redirect you to Dyndolod. Moreover Dyndolod doesn't run with that mod enabled, and even if I add the specific mesh supplied by that mod, Dyndolod says it can't find a matching model. What should I do? Other than this one issue my Dyndolod Output is perfect.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.