Highwayman300 Posted March 8, 2021 Share Posted March 8, 2021 (edited) Recently I downloaded and attempted to play with https://www.nexusmods.com/newvegas/mods/66666?tab=description (JAM) and https://www.nexusmods.com/newvegas/mods/71618 (Samurai Floating Damage), but I'm having trouble running Visual Objectives in the former and the later does not work at all. The visual objective marker refuses to move regardless of whatever MCM option I pick and simply stays in the top left corner of the screen, regardless of where the screen moves. Not suffering from CTDs or anything similar, and simply ticking off the option disables the marker on the top left corner from appearing.Samurai Floating Damage just outright refuses to work at all, except for once where the red critical message popped in for a second while using a scoped weapon ( https://imgur.com/BQ6FJVc ) .Since both of these mods use UIO and rely on the HUD to my knowledge, I think they suffer from the same problem/conflict. I tried deleting menu files to sort out a possible conflict, but not much happened. In a previous installation of NV, Solid Project's visual objectives (https://www.nexusmods.com/newvegas/mods/63239?tab=posts&BH=1) were also behaving in a similar manner and I couldn't figure out how to solve it. FNV Diagnostics did not show any conflicts, and I'm already running the basic requirements for both mods. (Both Solid Project and JAM work perfectly fine except for Visual Objectives) Could anyone share any insight on the matter? No matter what I do I can't figure out for the life of me how to solve this one. Edited March 8, 2021 by Highwayman300 Link to comment Share on other sites More sharing options...
Highwayman300 Posted March 9, 2021 Author Share Posted March 9, 2021 For posterity and possibly other people with the same issue, it was a conflicting JG-based, .dll xnvse plugin that was messing up other mods. Removing it made other xnvse plugins work perfectly fine. Link to comment Share on other sites More sharing options...
dubiousintent Posted March 10, 2021 Share Posted March 10, 2021 What XNVSE plugin, specifically, caused the conflict? If it came from the XNVSE team ... did you report it? -Dubious- Link to comment Share on other sites More sharing options...
Recommended Posts