Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
For now, it sounds like the best thing (besides a screenie so we can verify if it's the fps you're seeing) for you to do is play straight vanilla ff7.exe with the Reunion mod disabled, but including all the other graphical work (like satsuki's field remasters)
Each time I try to launch FF7 and it fails, it creates an extra instance each of 'direct' and 'music' in extra folders.This is a known bug. You can safely delete the extras when your load times start getting bogged down.
Trying to launch the game in the 640x480 mode causes my monitor to say "input not supported" and then i have to do a full hard reset of my pc. if anyone can help me solve the issue it would be greatly appreciated T_TIf your monitor doesn't support 640x480, you have bigger problems than a game that doesn't want to run. Of course, since this is the first post you've ever made here, it might be nice to have the usual diagnostic info... game converter output, opengl config settings, mod profile... y'know, stuff that's actually helpful?
My only concern is the R06 modding framework, I feel it may split the community with some modders supporting reunion and others 7th heaven, as right now 7th heaven I feel is an excellent tool, one can just add mods to it, remove it, all without manual fiddling, its click and play almost. The only real issue is the main catalog has been allowed to get out of date.I don't really think there'll be a split... sure, maybe some grumbling and grousing, but in software the better solution typically wins (n.b. I am specifically disclaiming the systemd abomination here). I'm looking forward to seeing what DLPB has in mind as a mod management system since turBoss seems to have lost interest in 7H. 7H has its warts, but as long as mod authors split their work into sensible pieces (one of the very few things I think Remako did right), it's still a pretty user-friendly solution to what would otherwise be a very user-unfriendly task.
Also you use precompiled exe's which is probably the main reason 7th heaven has been problematic with reunion, hext loading would likely make it work so much better. It allows much more modularity in selective use of features and co existence with other mods. But I accept this isnt a 7th heaven thread. So will stop there, but maybe to hope one day you reconsider your stance on allowing the two to be used together with your support.
I think a lost opportunity for them tho was on the PS4 version to not use any of the mods from this site in that build.Doing so would require lawyers, royalties, and all that other fun stuff.
This is proving difficult.KISS principle... Keep It Stupid Simple
I dont think I will be able to do all my wanted improvements to the menu overhaul but there is good news.
Or rather, in this case, release what's reasonable and easy to do (and it sounds like you've already got a huge amount done), then go back and do the nutso parts later in an update to the original mod, or as a second stand-alone. I'm not sure what EQ2Alyza has in mind for v3.0, but I *think* an easier update mechanism is part of it. From what he's posted publicly, I think whatever DLPB has in mind for his mod management method makes updates something the author can push (or at least advertise) themselves, rather than sending them through a catalog "gatekeeper."
For reference, this is what I see in the FINAL FANTASY VII\shaders\ directory, and this is what I see when I open up FF7_GameConverter_7H.exe. Is that what it's supposed to look like? If so, is 7thHeaven 1.56RC6 looking in the right place, for the right files? If so, can someone explain to me how that works, because I'm obviously missing some knowledge that would make this all make sense.I haven't played with the shaders myself (yet, anyways...), but my folders (both game and archive) are identical. Apart from the forward/backslash issue EQ2 already pointed out in the .xml, there's also this little piece in ff7_opengl.cfg that might have somehow been borked by a previous mod/install, which the converter isn't automatically repairing:
# post-processing shader, used to apply fullscreen effects
post_source = shaders/SmartBloomAdvanced.post
enable_postprocessing = noAs I said, I have shaders turned off right now (hence enable = no), but perhaps the source line got munged?
why use the 1.54 version?Because the 1.56RCx series suffers from a multitude of various and sundry bugs