-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RE 3, room 20C, many graphical bugs or crash #352
Comments
picture 1 : picture 2 : picture 3 : Is it same person in both column [xxx(xxx)] cause the problem ? maybe not , #338 no such problems if disable \mod_biorand\room |
@otamega72 the reason you don't get issues when you delete the room folder is because it removes the custom EMD (models/textures) for the NPCs. That is what is causing this, the custom NPCs we provide, probably because it is hitting some resource limit within the game. It happens when multiple active EMDs are placed within a room. For example in the first part of 20C, I have to force Carlos to be added to the room, as a 3rd NPC (alongside Mikhail and Nikolai) just because you might have all the components for the train. If you place all the components of the train when entering the room before the Nikolai cutscene has been activated, it will crash because Carlos isn't there. So now that all 3 NPCs are in the room (even if they are inactive / out of bounds), the texture of the sparks at the front of the train becomes corrupted. Again I think it is hitting some texture limit, or the textures are not compatible with each other (bit depth?). It is rather unfortunate. |
Version
3.0.1
Seed
R730-XAQF-ZTC885XZ3Z400NRPW490ZZZZZZZZZZZZZZZ
Scenario
RE 1 (Chris)
Player Character
Carlos
What happened?
Room 20C has many graphical issues due to the number of NPCs within the same room. I expect the custom NPCs (models and textures) are hitting some in-game limit related to graphical resources.
Another seed:

The text was updated successfully, but these errors were encountered: