Git Product home page Git Product logo

Comments (4)

LagoLunatic avatar LagoLunatic commented on July 23, 2024 1

This is a bug with how DSVEdit loads room states. It only seems to work 100% correctly in the vanilla case (room states don't appear as normal sector rooms, only as unique alternative states for normal sector rooms or other alt states). In your case a room's alt state is another room in the same sector, so it gets into an infinite loop of trying to load that whole sector into memory every time it encounters the alternate room state. I'll have to rethink how DSVEdit loads and caches rooms in memory to fix this.

from dsvedit.

4lorn5 avatar 4lorn5 commented on July 23, 2024

Thank you for your explanation.

For an alternate State, I also thought about moving away its opposing Castle counterpart and placing the new Castle State in its place (ie, for a Castle A State, moving away its Castle B counterpart and replacing it with the new Room), but it won't work. It does seem to accept already existing Castle counterparts as alternate States, however, so I might give my project a little push - even if it this requires considerable more juggling than I thought.

While I did not address the previous bug I've posted, I've realized it's somewhat related. It seems a room's layer size was somehow being affected if I created a Room meant to replicate it, and used the exact same information on the original's Room Layers. The error stopped happening once I chose to Select Tileset from within each Layer's options, and also didn't use any repeating information from its Room Props. Regardless, I think either is now solved or at least explained so as to find alternatives on my end.

Thank you once again.

from dsvedit.

LagoLunatic avatar LagoLunatic commented on July 23, 2024

It seems a room's layer size was somehow being affected if I created a Room meant to replicate it, and used the exact same information on the original's Room Layers.

I don't understand how that could happen as the layer's dimensions were being set to invalid values in your other issue. Even if two states share a layer and editing one edits the other, the safeguard to prevent invalid dimensions should still exist.

from dsvedit.

4lorn5 avatar 4lorn5 commented on July 23, 2024

Well, I have no copies of the previous project version I was working on. If I manage to replicate that particular error, I'll be sure to post it here.

from dsvedit.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.