Author Topic: [FF7PC-98/Steam] Multiple mods and Modding Framework-The Reunion [R06f] (Read 3070776 times)

DLPB_ · « **Reply #6450 on:** 2020-05-20 01:24:11 »

Minor issues like that even if bugs are likely going to go largely uncommented. There will be hundreds, so if I don't respond, you'll know why.

mph8er · « **Reply #6451 on:** 2020-05-20 03:53:30 »

Quote from: DLPB on 2020-05-18 10:52:05

need your save file,mph7er

Never saw a response to my save file, so will post a full bug report. I'm going to reinstall FF7 and R06F from scratch and start a new playthrough. If the save file is fixable or if you find something, let me know. Will post an update after I reach Cosmo Canyon again.

1. Progression issue in Cosmo Canyon. Red XIII missing from stairway after entrance cutscene. Bugenhagen and Red XIII not in the observatory. Other party members not in scripted positions. Talking to the guy blocking me leaving Cosmo Canyon causes a softlock.
2. Repeatable on save file. Planning to replay to verify if it's encountered on a new save. R06f was installed about 10 hours back. Did not encounter the issue on another playthrough via R06e, though I was using other mods on that playthrough via the custom folder.
3. App.log: https://drive.google.com/open?id=1F11v70XfhxpHM_mg4fUBoAn8TzvTP9Il
4. Reunion.log: https://drive.google.com/open?id=1kR1HLSpe6Ne-YVZRjqF0OTyqPIZ0s7SR
5. crash.dmp: Not crash-related
6. Save file (most recent save): https://drive.google.com/open?id=1BpPaj7SRbg8oWF5sHA5WirG9pCz3budA
7. Audio.log: https://drive.google.com/open?id=1p3eGKGytM1S_k4EweGLqaMufZfn11j77
8 & 9. - not a performance issue

ShinraITDepartment · « **Reply #6452 on:** 2020-05-20 05:36:31 »

Quote from: Elhoim on 2020-05-19 13:43:23

I thought I was alone in this, it's been pretty hard playing the game with this bug. For what it's worth, I also had it when playing with the 7th Heaven set-up, so it doesn't seem related to Reunion only. I added several graphical mods like Nino Style, better looking spells, Remako and a tweak to the UI.

Having this same issue.

DLPB_ · « **Reply #6453 on:** 2020-05-20 08:24:24 »

Please don't post bug reports twice. I'm aware of it.

DLPB_ · « **Reply #6454 on:** 2020-05-21 00:55:09 »

Resolved. Somehow a major variable allocation has been removed and so Cosmo Canyon is now completely broken. For now, until Cosmo Canyon is passed, turn off New Translation.

Sigh... I tested this area a lot so I have no idea how this has happened - unless Makou has some bug. I dunno. Any case, it's resolved with R06g. I need to get this updated anyway with ffxn - so I'll be working to that soon.

Alternatively: open flevel.lgp in BASE folder with Makou reactor and add

Bit 2 ON in Var[3][161]

below

Activate the triangle #88
Activate the triangle #84
Join party field (speed=18)

in cos_btm > group 15 > S1 - talk

Around line 122.

Agravaile · « **Reply #6455 on:** 2020-05-21 05:47:55 »

Sorry to ask, but if someone does edit that bug with Makou in flevel.lgp, would you be so kind to upload it please, i've no experience with it, so i'm afraid not being sure in what i'm doing if i try to fix it myself.

Please do this if you've already done this, and this won't take your time at all in doing so, i don't wanna waste anyone's time with it, so if you already have flevel.lgp fixed, i would appreciate a lot if someone uploads it. Thanks in advance!

All with DLPB's permission, of course.

skyhawk · « **Reply #6456 on:** 2020-05-21 06:48:53 »

Quote from: Agravaile on 2020-05-21 05:47:55

Sorry to ask, but if someone does edit that bug with Makou in flevel.lgp, would you be so kind to upload it please, i've no experience with it, so i'm afraid not being sure in what i'm doing if i try to fix it myself.

If my understanding is correct [take with a HUGE boulder of salt], flevel.lgp is actually built by the installer based on what options you select during installation. Using someone else's flevel.lgp may not work or might cause other bizarre issues.

DLPB_ · « **Reply #6457 on:** 2020-05-21 07:59:49 »

ah shit yeah you'll need a special build of Makou too. forget it. await R06g

Agravaile · « **Reply #6458 on:** 2020-05-21 08:12:12 »

Quote from: skyhawk on 2020-05-21 06:48:53

If my understanding is correct [take with a HUGE boulder of salt], flevel.lgp is actually built by the installer based on what options you select during installation. Using someone else's flevel.lgp may not work or might cause other bizarre issues.

Right, it was then i remembered there were certain setting the installer has to build during installation, thanks for your help though.

Quote from: DLPB on 2020-05-21 07:59:49

ah strawberries yeah you'll need a special build of Makou too. forget it. await R06g

I see, thanks anyway, for now and in general.

Zatos · « **Reply #6459 on:** 2020-05-21 08:17:41 »

Quote from: Agravaile on 2020-05-21 05:47:55

Sorry to ask, but if someone does edit that bug with Makou in flevel.lgp, would you be so kind to upload it please, i've no experience with it, so i'm afraid not being sure in what i'm doing if i try to fix it myself.

Please do this if you've already done this, and this won't take your time at all in doing so, i don't wanna waste anyone's time with it, so if you already have flevel.lgp fixed, i would appreciate a lot if someone uploads it. Thanks in advance!

All with DLPB's permission, of course.

EDIT: I'm not sure if this will work as DLPB mentioned needing a special version of Makou Reactor.

Here's some easier instructions for those that haven't used the program.

You can download it here: https://forums.qhimm.com/index.php?topic=9658.0

***Make a backup of your flevel.lgp file just in case anything goes wrong***
After launching the program, go to File -> Open -> select the flevel.lgp in the BASE\New_Translation folder
On the left hand column/section, select the file 'cos_btm'
In the second section to the right of this, find ID 15, the group is named 'WATCH' and select it
In the third section, select 'S1 - Talk'
In the fourth section, you'll need to expand the lines (click the arrow on the left hand side around line 89, should be the last arrow) as the lines you need to find are collapsed and not visible
Find these lines (which should be around 122 as DLPB mentioned):
- Activate the triangle #88
- Activate the triangle #84
- Join party field (speed=18)
Right click on the last line 'Join party field (speed=18)' and select 'add'
Choose 'Mathematics' from the first drop down
On the second dropdown, choose 'Bitwise operation'
Below the text box, it will say 'Variable' - in the first number field to the right of that, set it to '3'
In the second number field to the right of that, set it to '161'
Below that, there will be a line that says 'Position' - set the number field to the right of that to '2'
Click 'OK'
These lines should now show as:
- Activate the triangle #88
- Activate the triangle #84
- Join party field (speed=18)
- Bit 2 ON in Var[3][161]
If the lines don't appear in this order, right click the newly added line and choose 'up' or 'down' to make sure the lines appear in this order
Choose 'File' in the upper right and select 'Save' (or alternatively use the Save icon in the upper right)
Close the program and play!

To be honest, I've never used this program. But I'm pretty sure I did it correctly according to DLPB's instructions. If not, feel free to chip in DLPB if any of this is incorrect. I still need to test it myself, which I'll be doing after this.

DLPB_ · « **Reply #6460 on:** 2020-05-21 10:34:16 »

I wouldnt touch it at this time.

Zatos · « **Reply #6461 on:** 2020-05-21 12:24:38 »

I just finished getting past Cosmo Canyon using the fix and I had zero issues.

DLPB_ · « **Reply #6462 on:** 2020-05-21 13:52:27 »

Yeah but you'll now likely have issues where your flevel is now broken because supported opcodes will be knackered

Hence why I said not to do it.

Zatos · « **Reply #6463 on:** 2020-05-21 15:35:10 »

Gotcha. I'll wait for the next release.

DLPB_ · « **Reply #6464 on:** 2020-05-21 19:05:06 »

fractalsinnsture · « **Reply #6465 on:** 2020-05-21 22:46:29 »

I apologize for the stupid question, but I'm not seeing any of the button commands. For example, I just got to Junon and the parade commands are all blank spaces. I'm running R06f and the Steam version of FF7. Thanks!

Cupcake · « **Reply #6466 on:** 2020-05-22 01:59:29 »

I've stayed out of this for a while; but man those are some hot takes Dan. Here's my question, why the fern do you not understand that LGPL is not the same thing as GPL. The stackexchange question you keep posting as evidence that you are NOT in the wrong is explicitly about LGPL, not GPL. I know you won't answer me because you're not at all interested in actually talking about strawberries, and even if you were, you're such a damn narcissist that you wouldn't be able to comprehend yourself being in the wrong; but in the off chance you do, the fern dude?

EQ2Alyza: This topic is done and over with publicly. If you want to further discuss, take it to PMs.

mph8er · « **Reply #6467 on:** 2020-05-22 02:06:02 »

This one's easily avoided, but was reproduceable across two separate playthroughs. Didn't find it in the list. This was on R06f with no other mods.

1. Soft lock in Golden Saucer. If you skip the final tram FMV during your first visit, the music will not play. If you immediately go back in the tram upon arrival, the game softlocks.
2. Repeatable on save file 1. Enter Corel, take tram to Golden Saucer and use the FMV skip feature on the cutscenes.
3. App.log: https://drive.google.com/file/d/1K6yZo_ne0p-j1ncwjfb_JgL4otG5eSB6/view?usp=sharing
4. Reunion.log: https://drive.google.com/file/d/1qVDkRQ_Yhro1dp_bnjUv5kFfMBWnOMOX/view?usp=sharing
5. crash.dmp: Not crash-related
6. Save file (most recent save): https://drive.google.com/file/d/19Jbn5e2bdA-Zl4OzH9ImugUbVdNcjf-E/view?usp=sharing
7. Audio.log: https://drive.google.com/file/d/1RXy3f_UPF2JFq_B75COaU0VNvRoYBCwe/view?usp=sharing
8 & 9. - not a performance issue

DLPB_ · « **Reply #6468 on:** 2020-05-22 02:33:31 »

Skipping FMVs is warned about in help file.

mph8er · « **Reply #6469 on:** 2020-05-22 03:22:27 »

Quote from: DLPB on 2020-05-22 02:33:31

Skipping FMVs is warned about in help file.

I know. Still worth it to document it though. A, it will help those who want to skip as many of them as possible. B, if a way is ever discovered to actually fix them, your bug document is well organized and and would serve the purpose well as a one-stop shop for the instances it occurs in.

DLPB_ · « **Reply #6470 on:** 2020-05-22 10:17:58 »

I'll see if anything can be done about it - if not, I'll disable skipping for problem FMV.

YPM · « **Reply #6471 on:** 2020-05-22 21:25:11 »

Hey, DLPB. I've been struggling to find a full answer on the small model size within fields issue. I've looked in the bug reports, help files and the forums but I can't find much on it, so I'm gonna ask here. Forgive me if you've heard this 1000 times but is correcting the Kaldarasha field model sizes to look larger on the table for you or no?

I've been playing around with HRCResizer and Makou to varying levels of ~~failure~~ success, but since this is my first playthrough and first crack at FF7 modding, I'm not convinced I know what I'm doing.

Anyway, I'm really enjoying the mod and the game. I've got a bunch of other mods installed under Custom, so the mod framework seems solid, too. I hope you keep everything going. Thanks.

DLPB_ · « **Reply #6472 on:** 2020-05-23 02:13:42 »

Possibly but not a priority at this time.

YPM · « **Reply #6473 on:** 2020-05-23 14:54:13 »

Completely understandable. I'm tempted to start working through the flevel.lgp in Makou to do each field myself (I'm bored

) but I believe the next time you update Reunion, my changes would be lost and it would all be for nothing. It's a tad immersion-breaking when I flip back to stock graphics and see the size difference but I can deal with that.

Thanks, again!

DLPB_ · « **Reply #6474 on:** 2020-05-23 23:16:00 »

https://drive.google.com/file/d/1Ir2iHMUDPSlNZe3Hc8Vkq41Kfooz2Muu/view?usp=sharing

need testers. Use this file and play at least 1 hour of battles and send me app.log - if crash, let me know as well and send as soon as crash. No crash = 1 hour of data. It attempts to fix the crash with a custom TRY CATCH. A sloppy work around.