[FF7PC-98/Steam] Smoother 60FPS Battles (v0.95)

[obesebear]

Click here for a much better version of what this mod was meant to be

Up to date as of 10 January 2020
Soon to be implemented into FFNx

Please add 006E329B = 83 E1 03 8D 94 CA 44 01 00 00 to the very bottom of 60fps.txt.  This fixes Tifa's limit break slots.

Model animations... 99%

Limit Break animations... 99%  limcd7.a00 needs to be overhauled due to poor rotations

Camera animations... 95% (Thanks to NFITC1. Still a few camera movements at 30fps. )

Texture animations... 90% working but not interpolated

Battle Interface... 90% (Still needs animation scripts to be delayed)

Summons... the current fix for the textures messes up the summons. See below for details

The alternative to what I've just done is to alter a whooping 1,918 individual functions MANUALLY. I made a list (dynamically, of course) and thought I'd better save it for posterity. If anyone (or a group of anyones) is diehard enough to tackle this, here are the 3D handlers that I've identified:
Code: [Select]

425D29425FC442782A439C6B439EE043AF1B43CC4D43CD0C43CDE043D17E43D4DF43D65443D73E43D89243D98443DB3143DC8D43DEB043E02843E2B543E50C43E85E43E96243EA5943F2AE43F4A643F59C43F65E43F74D43FB7543FE0744009F4401BD4402D54403CB4404FE44065144084A440A6C440C22440CF5440DEC440ECD440FFE44116644137544166B44184D4419A7441D6344209C442179442B6744357D44366844375644385E443A2F443D2944409344425644453144469C44487B4448D64453DC44593F445BA0445DAF4461B044656B446926446F2B4474D5447C2A447CB84481524482F14484224488D2448B4B448BA644939C4494FA4497524498F1449CD7449DD3449F9844A15944A2F544A7D244B97544BCBD44C0C544D9A344DBC844E3D344E56B44E6E944E80D44EDC044FF634500BD450999450F4245138145162845199B451CA44522AD453450453FBF45500C4550D045521945542E45556B455BC0455E16455F8B4571484572F64575CF4577144578F0457C60458C9B458D864593A24594464595C745994C459A3F459B12459C95459DFD459F2345A09145A18F45A3B345A5EB45A6A645A99845ABAA45AF3945B0CF45B48745BA2C45BC8545BD4245BE5845C26345FF5C460303460A1D4615A14617A7461DCF46245F462B074632AE46338E463F4246406E464960464A6A464BAD464F0D4656554657AA46596D465A29465CB3465E514660634664A946652D466604466807466A7A466CD24672564673AA46758D467987467BA8467C8B467ED44680154682164688A24698EF469A7C469BE5469F3A469FB346A0A146A15646A7BF46A89046A98946AB0046B17546B40D46B57146B5F346BA0B46C9F246CB5D46CCC846CE3646D17746D32C46D45D46D64746D7BE46D8F446D9C846DDFA46DF6546E0BA46E2EA46E46146E57A46F22D4700314700F747025A4704384707CC470B8E470EEF4710234711A147148B471722471922471B90471C61471D994720CF4722FD47256C4726C547288A472B3D472C4B472D7A47301347310F4731AD4738DE473CC2474C71474D1C47518A47568747577747588D475989475BB7475CB1475E9C47605F4761864763C5476513476672478031478DB6478EDF479AB2479EAA47A15A47A52D47B00A47BC2C47BECB47C17747C3BF47C51647CAAC47CF8447D37B47D49D47D72647E72547E7F347E91947EE9E47F31047F50F47F7C747FA51480946480B3A480D91480DF94813BF4813FB4814374815BD4817C6481867481B5A481BE8481E7C4821E04822454822854823E44825E04834B4483866484A164854F44855A54858AA4859AA485E6A485F5B48615F4862B64864EB48667048685C48697C486A35486BDF486E18486FA0487277487842487A2C487BD2487C73489CF0489F4548A07448A95248AA6148AC5E48AD3C48AF4048B2C048B7C048BBFC48C75D48D7BC48DA7A48E2CD48E6BD49023449036D49067949075549081F490ABC490DE5490F2A4915E94917384918F1491B0E491E244923AB49258F4926E549281649299C492C4C492F2749313349346B49377549389F493A11493C9D493F49494091494773494D62494F264951A04952A84953D949551049680C4969FA496AC1496CC54970864971EF49731049741749757A4976D0497A37498A964990FE499227499388499540499823499A1A499C33499E6D499FEF49A0B949A1E949A32349A55B49A7AB49AC0A49ADEC49B12C49B16D49B20649C37C49C6E449E35649E55849E6F349E93A49EB0649ED0A49EEE749F10E49FB8749FBF749FF2E4A0F524A1F8A4A27CC4A2BE54A2D0E4A30C64A33624A36894A3A2E4A3E2B4A401B4A41714A425F4A43F54A46E74A499F4A4BE64A4D7C4A4EEA4A4F7B4A584D4A5D3C4A6CB84A792C4A7A034A7AC84A84314A89BB4A8B864A911A4A942F4A953F4A96274A99084A9C324AAAAF4AAC514AACE84AB1104ABA854ABCB04ABDF14ABF6A4AC1E74AC3544AC4F14AC8E14ACAEA4ACC4F4ACF674AD4B64AD5CD4AD6F94AD79A4ADA7C4ADD054ADEB34AE03C4AE3D24AE76E4AE9894AEA8C4AEC564AF0C84AF4244AF6F44AF8E84AF9C74AFC2F4B00504B060B4B06DC4B07EC4B092D4B0AE64B0D934B16A84B19854B1F124B24F74B25F24B275D4B29144B2B754B2D5C4B2E2D4B31304B34104B35524B377D4B39F24B3E724B3EF34B40454B41914B439D4B44704B45844B47B74B4CA14B53D94B56DA4B5BE34B5EE04B615A4B63A44B65A84B76144B79694B79E14B7A974B7BA74B809D4B81A24B89504B8A954B8F894B997F4B9B4F4BA03F4BA8C14BA9EA4BAE744BB0DF4BB3354BBA5C4BBB244BC2BD4BC3834BC3F64BC9AD4BCA544BCC254BCCC74BD41F4BD4C14BDE584BDF674BE08C4BE80C4BE9D54C0D634C11854C12DC4C14AB4C16AD4C1BA24C218F4C22F54C2D5F4C2E4B4C31984C362B4C37574C3A074C3BEF4C3DD74C406D4C40E54C43724C44C24C4A6B4C4E1D4C51E14C52904C53D64C55074C56FF4C5B5B4C5CDE4C60364C62DC4C650A4C694D4C69A84C6F424C740B4C79A74C7BA84C7D7A4C833D4C854A4C86CF4C8B104C8CC84C8F744C8FB54C91044C95354C965F4C972E4C98E74C9C024C9DA24CA64A4CAC854CB2264CB30D4CB71D4CB8974CBF804CC18A4CC3FC4CC5B04CC68F4CC7E84CC9D04CCB854CCC744CCDCD4CD2754CD3744CD54A4CDB554CDC544CDE294CE4874CE5F84CE7804CE9EA4CEB734CEE2A4CF15B4CF3C54CF6D24CFBE54D021E4D03EC4D05B64D08E64D0A5A4D0CB54D107B4D19104D1F074D202A4D219B4D23F64D25844D2BC74D2CEA4D2EB44D31FC4D33D14D3A374D3B364D3CA84D3FDD4D42914D48C64D49C24D4B5D4D4BEE4D4D644D50704D54B24D594C4D68FB4D69A64D70444D71744D72D04D75494D78B94D7AD04D7DAA4D7FDF4D81774D83764D93144D95024DA0864DA1824DA5164DA6DF4DAD5C4DB00F4DB15F4DB26E4DB4D24DB9D64DBA784DBBF24DBE484DC10C4DC2BF4DC7D74DCA514DCBC44DCD244DD0BD4DD4A64DD5484DD79E4DD8914DDA444DDE9F4DE1194DE2734DE51E4DE9BC4DEA5E4DECB44DEDAA4DEF5D4DF3B84DF6324DF78C4DFAFD4DFEE64DFF8B4E01E14E02E54E04984E08F34E0B6D4E0CE04E0FA74E12004E12C34E13D94E1E984E24B74E259A4E2DF34E33384E34364E3A444E3D514E401E4E44C64E45A94E48D44E4B3B4E4F064E50CA4E59624E61284E62A54E647D4E666E4E6AB74E6FEC4E71D24E73AF4E75DC4E78754E81F04E92924E93904E95AC4E9D1D4EA0F24EA2F44EA4D54EA6A04EAAF14EAC644EAEFF4EB7AE4EBA534EBC954EBD864EC0B24EC7FC4ECC664ECFAB4ED04F4ED3204ED5754ED7B04EDAA94EDFFE4EE2364EE4934EE9AD4EEA514EED224EEF774EF1B24EF4C14EF5374EF5B84EF7DB4EF87F4EFB504EFDA54EFFE04F02D94F04604F082B4F08CF4F0BA04F0DF54F10304F133F4F14794F19064F1A204F1B3A4F1F5B4F1FFF4F22D04F25254F27604F2A594F2C354F32FD4F36084F37DD4F3A6E4F3CFF4F3DD04F3FB04F419F4F44AB4F454F4F48204F4A754F4CB04F4FBF4F51044F540B4F54AF4F57804F59D54F5C104F5F094F61174F64504F66494F67CE4F697D4F6C2B4F6CCF4F6FA04F71F54F74304F773F4F78244F79BF4F7C2B4F7CCF4F7FA04F81F54F84304F87294F880E4F89A94F8C154F8CB94F8F8A4F91DF4F941A4F97134F9A4D4FAAAC4FB1D94FB2934FB3FC4FB9634FC52C4FCC1C4FCD1D4FCE714FD1284FE6CC4FE7C54FE9B04FEACE4FEF5A4FF1E24FF3114FF5F24FF82E4FF9124FFC9A50001F50011050031350046C50057F*500C458B500FCC50124E5013775016375025B350265E5033F55039E55047CA504D72504F7D505BC3505D5F505E2E505F0E5063505066C75069BA506D87506E9D50701D5071F75073C350749F5077925078D8507CA4508BED508EB450907E50921E5093BE5095F55096925096F3509B1050A9E050ACDA50AE6050B07D50B1A350B2F750B48350B5F050B6D650BA3650BE4850C0F050C22150C6EE50C7BF50C8ED50CAAB50CF6050D37250D5F550D72650DBFF50DCD050DDFE50DFC550E49350E8CF50E9A050EB7650EDAE50EFAB50F25D50F3BB50F46150FA5B50FEE250FFB351012A51040D51080D5108DE510A0B510C49510E085110E051137C5115AA511634511942511E2A51229751235E5124D55127B4512A9F512BB45137E9513BAD513CC7513D9A5141315142435143AE514506514B07515238516297516ACF516D3F516E135170BE5171E351731A5174DD5177D55178F9517C7A517DBB5180065181475188F3518AFF518C07518E2D51922451933651962A519754519A1B519E16519EE951A06351A3EA51A62151ABC851AD1751AE9151AFF751B3AA51B67D51B8F751BA1A51BED951C6E551CBD351CCFC51CE7651CF8951D0DE51DACA51DCE151E06851E3B351E83D51E98051EA7351ED9751F01151F14251F6EE51F81151F9C651FC3151FD5651FF77520406520746520BE3520D7C5210275213D1521967521AD2521C4C521DB252216B5225E752272152289B522C58522F575230EE52336D5234E15239A8523D85523F1C52419B52431D5247F0524C23524EB75252E25256355257565259CD525B1F525CCE525FFA5265645266C3526957526B4D526C20526EB8526FD05274E2527776527932527D945280B25282CE52840C52876E52882E5288FB528A27528C64528E2A5292E75295A252971552A00152A0E652A1B952A44052A77352ABE952AD2D52AE5052B09D52B33752B46852BA7052C02052C16B52C2A552C9BC52CC9052CF1552D01052D72752DC0C52E02652E16052E23152EBE852EEC252F01752F2C052F65C52F72552F83752FEFC5300D15303A75306DC53079A530AFC530C16530E1D530F035311EB53152653177B531C10531DD55320CA53218853237D5325A753268D532963532C56533005533199533370533A52533B9E53411D5344DE53456653463953484D534C3A534CCE534DA1534FB55351325351D45354635358E05359B1535B28535D775363015365955369A0536DD4537068537427537507537BC3537D6353831553858E538650538C6F538D77538F0E539174539590539883539A19539C6853A41853A69C53A76D53A83E53A98153AACD53AC2853B14D53B40753B8BA53BB4E53BD4453BE1753C0C153C20E53C2B053C53F53C9A553CA7653CBCF53CE5353CF6953D55353D64653DBB353DC6153E28253E5A153E6FC53E8B153EB4453F05E53F3B853F48953F84053FCE65400155400A854064E540863540C605411B35412CC5416D95419AF541C9A541DB954286E542BAE542C7F542E4A5432EE54362F543908543A2B543BBE543EC75440D95444735446DD544D43544F0354513F54542D545A90545C50545E8C54616354629854660E546846546E86546FD05472045473585476B0547B94547D56547F3C54809A5483E65486E2548829548980548C5E548F5A5490D1549228549542549A43549BD0549F2154A41654A54D54A84654B28B54B9E354BB0254BC4F54BE0554BF0954C19F54C28A54C3F054C73554CA8854CE7B54CF4C54D3BC54D53154D84054DA2354DAF654DE0A54E06554E2FE54E63754E88754EE3A54EF7D54F0F654F40954F76C54F8B554FBA054FFC955011D55029755073B55097F550DE355126155140F5515BF551A1C551CCC551F0C551FDD5523495524CE55280F552911552B04552C14552E2B5531D75532E05533BA5537DF553B88553DC1553EB655415C55439C55446D5547D955495E554C9F554DA1554FD055533F55544855552B5558BA555B0F555BE05562CC5568955569E3556B1B556E35556F4A5571C55574FE55765E55788B557AE8557BAA557E58557FC555848F5585BD558882558C0455903355918855925955958655991A5599ED559C82559EA255A2F855A3C655A4D455A88355AC1555ACFF55B1A355B47755B6C755BBBE55BEE155C06D55C17D55C53B55C77755C84155CAF755CE9E55CFFC55D0DD55D37855D6E055D7B755DB9855DF5F55E03755E49355E67155EA0A55ECA055F28455F42E55F64155F93255FB3C55FC3755FEF25600BE56020D5602FC5604E55607415609DB560C3256149A56163E561737561908561C87561FAF5624A5562C60563DC5563FBD56419156451556470F564844564A3B564B8F564CF6564E375650B35654845657895658825659BD565B9F5660075661A0566287566871566E615675385676E35678A5567E4456837156850F568ECD5691FE5693E35695CC569CAB569FDA56A9FA56AA3B56AB9856B17C56BA6256C30756C40E56C82856D25256D81756D97E56DB5256DD3256E65A56E81E56EA1D56EBC756EE4256EFFE56F14356F3F656F49656F6F056F9FD570120570244570417570531570688570996570AD6570C89570E24570FFD5714685716B257185C571A48571B06571CFB571F6657202A572912572A9F572CE0572DE75732915733A457364257380A5738C8573B8B573E87573F6D57421B5744BE57461C574901574CC7574E71575168575341575BEB57687A576A84576BD657708E5775FF57771457784F5779BD577C0E5782AF578378578B175794CD5797B15797EF579A97579BF3579D4B57A08257A7DE57AA5557ACAF57AE6E57B02D57B71257BECD57C1DD57CCE357D4CA57D69657D89B57DA9357E35E57E52B57E7D657E9D457EBD257EDD057EFA757F13B57F35657F44C57F77557F94257FB0557FCC857FE3657FFDF5804D458059D580D0C580F3E58119558173E581B7C581E5D582657582924582B4158474458488B584A5E584C4F584E14585412585B7358608A58729B5873FA5875FD58782F587A50587E7E588205588A5458900558932B589461589D38589FAE58A62958A9C258AC5958AF5D58B28558B5E958BABA58C02E58C10C58C7BC58CB0858CF8958D21058D3E158D60558D7AF58D95258D9F658DB7458DD8B58DE8258DFFA58E24F58E60D58F6E358F78E58FC1B590811590931590A54590B8E590D8A590FC459134F5917D55920635922715923F4592538592A36593A955940B2594C07594D825950925953FD59560159579159588C595A055967025968E3596B7E596DA55972065981015988465988DC598997598E29599004599C3D599EA359A07B59A49859A6F259A7D059AB5459AC9D59AD7F59AFBC59B4B059C50F59CAC159CF9F59E2CF59E3A359F2E859F55559F70759FBA05A033B5A05CE5A08395A0F695A10ED5A14B55A160A5A19FA5A1B555A1E935A20105A22005A23EE5A26D35A29235A2B085A2C455A2D8E5A303F5A322C5A3D8A5A3F8C5A40DD5A43595A45045A48F65A4D2F5A4E6D5A506E5A53F75A54C85A56515A58A35A638E5A64515A655A5A67C75A69E15A6B1E5A6D375A71B05A75E95A77275A79285A7CB15A7D825A7EEE5A80635A83015A855B5A86B85A89D65A8AC35A93A95A94775A95F55A97745A9B985A9C585A9D255A9EA55AA1365AA3415AA9FA5AAD5C5AAE1C5AAEE95AB0185AB2555AB5CD5AB8F55ABC715AC1425AC5475AC85E5ACA505ACBD05ACD775ACFDA5AD15A5AD4285AD4F35AD6C15ADC6E5ADE785AE0145AE30B5AE5DE5AE8C55AEAD65AED555AEEF55AF02D5AF26C5AF48E5AF6C55AF8AA5AFA7F5AFB3D5B01125B01FD5B07165B17755B1E955B26365B29AD5B2BA65B2D0A5B2F185B310F5B33545B35495B37095B38375B3B2F5B3CAA5B40175B415C5B44C85B483A5B4A765B50D25B58C95B5B1E5B5BEC5B5CE15B5F305B619E5B635B5B66335B671D5B69AF5B6DA35B6FAD5B73235B74FA5B75D25B786B5B7C6A5B7E005B81755B824D5B840B5B86BA5B891C5B8ABD5B8BC25B8C8A5B8F7D5B91415B92955B935D5B95F95B992E5B9A265BBA825BBD245BC21F5BC48C5BC8125BCAAA5BDA0F5BEA3C5BEB685BFB915BFCCC5BFD935C0BA55C0E4B5C1B815D36015D43315D442F5D45CA5D48175D4A585D50725D552D5D602A5D699C5D6B5B5D6CB65D6F0E5D705F5D72265D73D85D75425D75E65D77785D792E5D7B24

As far as I can tell that's inclusive. Ignore then 8-digit one. I don't know what that is or where it came from. Not only this, but there are likely multiple edits per method. On the flip side there are probably some that don't need any modification at all. That likely comprises less than 5% of them.
There are also 2D effect handlers, but not near as many. Less than 125.

If you don't know what this means then don't worry about it. Just accept the fact that interpolation of 2D/3D effects is FAR AND BEYOND anyone's dedication to this game. Feel free to prove me wrong though.
If you're curious about how to alter these PM me and I might try to explain. Be warned it's extremely technical and requires knowledge of x86 assembler and how the battle render engine works.

There are occasionally problems in the battles where bullet shells or textures don't show up.  I have no idea why or what causes it because reloading a save and fighting the exact same battle will sometimes load the textures properly.

Proof of Concept Videos (must be watched at 720p or higher)
www.youtube.com/embed/CFixQcIpMEs
www.youtube.com/embed/5m57Uz6gkrs

 

[sl1982]

I will ask Borde about it, next time i see him online if you guys like. He maybe to busy to do anything but he might tell you where or if it can be done

Don't worry about it. I took care of it.

edit: Here is a video if anyone is interested of the battles running in 60fps. Fraps does drop the frames down a bit when recording but you get the idea. Interpolated animations were created with a modified version of kimera i made.

 

[sl1982]

Just a little experiment with interpolating the sprites. Opinions please.

 

[nfitc1]

Since a moderator necro'd this I'll follow suit.

It literally occurred to me this morning. You don't specifically need a camera editor, just something that will extend the camera's duration for things. That would take no more than a single pass through the camdat files and increasing/decreasing all the "steps/frame pauses" for all relevant codes. That I could probably cook up pretty quick. Enter the current fps, desired fps, the camdat file to process and you'll get the camera flowing the way it should! I'm going to give this a go real quick. Should be pretty easy. It's just picking out the codes and modifying the correct bytes. I'm pretty sure I found them all already. Let me take a crack at this.

 

[Aali]

.s files can be edited to include more frames but they wont play. The duration of those animations seems to be hardcoded.

 

[sl1982]

Perhaps when they actually play can be edited? Say for example they play on frame 20 right now and we get them to play at frame 60 instead? It wouldnt totally solve the problem but it would help.

 

[Aali]

Thats also hardcoded. It can be fixed of course but it entails reprogramming every single spell effect in the game.

Your best bet with spell effects is probably to pretend the game is paused for 3 frames, advance one frame, rinse and repeat.

And yes, I am working on that as we speak.

 

[nfitc1]

I've been meaning to get back to this. Stupid addictive duodecim.......

The "solution" I came up with isn't perfect,but the only thing I can think of to so with this is to add wait periods to make the camera last as long as the animation. This has drawbacks though. Consider something simple like Matra Magic. The camera is supposed to follow the missiles from the caster to the target by performing XX transitions between looking at the caster and looking at the target. If that transition takes more than 64 frames, then the transition increment can only go to 255, then it'll have to wait the rest of the frames at the destination before the next transition takes place.

Say a transition is supposed to take 100 frames. If your increasing the fps from 15 to 60 then the new desired transition time would be 400 frames from point A to point B. But it can only really be increased to 255 transitional frames and made to wait the remaining 145. That will make the transition much faster, but it will be focusing on what it should focus on when it should focus on it.

That said, in order to do this, it requires splitting each camera script by type, editing them, then reconstructing the cam files From scratch. That's not as simple as it might sound because there are actually scripts that aren't used and there are lots of duplicate pointers.

There is no better solution unfortunately. In some cases we could calculate where the camera should be after 255 transitions between point A and point B, but there are some scripts with transitions between relative locations like "caster_center" and "target_center" that wouldn't work like that. Not unless we knew more about how it all works.

 

[nfitc1]

Well, if you can't increase the script's wait, make the game wait longer. If the F5 handler was changed from

Code: [Select]

005C2A95 PosCamF5:005C2A95                 movsx   edx, [ebp+arg_0]005C2A99                 imul    edx, 0Eh005C2A9C                 xor     eax, eax005C2A9E                 mov     ax, word_BE10F8[edx]005C2AA5                 mov     ecx, [ebp+var_18]005C2AA8                 mov     edx, [ecx+4]005C2AAB                 movsx   ax, byte ptr [edx+eax]005C2AB0                 movsx   ecx, [ebp+arg_0]005C2AB4                 imul    ecx, 0Eh005C2AB7                 mov     word_BE10FA[ecx], ax005C2ABE                 movsx   edx, [ebp+arg_0]005C2AC2                 imul    edx, 0Eh005C2AC5                 mov     ax, word_BE10F8[edx]005C2ACC                 add     ax, 1005C2AD0                 movsx   ecx, [ebp+arg_0]005C2AD4                 imul    ecx, 0Eh005C2AD7                 mov     word_BE10F8[ecx], ax005C2ADE                 jmp     loc_5C3C57

to something like:

Code: [Select]

005C2A95 PosCamF5:005C2A95                 movsx   edx, [ebp+arg_0]005C2A99                 imul    edx, 0Eh005C2A9C                 xor     eax, eax005C2A9E                 mov     ax, word_BE10F8[edx]005C2AA5                 mov     ecx, [ebp+var_18]005C2AA8                 mov     edx, [ecx+4]005C2AAB                 movsx   ax, byte ptr [edx+eax]005C2AB0                 imul    ax, 4005C2AB3                 movsx   ecx, [ebp+arg_0]005C2AB7                 imul    ecx, 0Eh005C2ABA                 mov     word_BE10FA[ecx], ax005C2AC1                 mov     ax, word_BE10F8[ecx]005C2AC8                 add     ax, 1005C2ACC                 movsx   ecx, [ebp+arg_0]005C2AD0                 imul    ecx, 0Eh005C2AD3                 mov     word_BE10F8[ecx], ax005C2ADA                 jmp     loc_5C3C57005C2ADF                 nop005C2AE0                 nop005C2AE1                 nop005C2AE2                 nop

Then we'd be a lot closer. That's just forcing the wait counter to be four times as large as the script wants. This would also have to be done for the Focus Cam F5 handler and any other op that wants a increment of some sort. The problem is this solution isn't as wonderfully modular as altering the scripts themselves.

 

[nfitc1]

NTFIC1 i eagerly await your modified ff7.exe

*sigh* I have GOT to stop suggesting things.

For my own personal record I'll submit the following:

Cam Progress:
Position:
D8 - 0x5C3E6F; 100
E2 - 0x5C27DA; 100
E3 - 0x5C3E6F; 100
E4 - 0x5C3E6F; 100
E5 - 0x5C3E6F; 100 (I hope I'm not breaking these)
E7 - 0x5C352D; 100
E9 - 0x5C33B9; 100
EB - 0x5C31F8; 100
F5 - 0x5C2A95; 100 (this was a long one. Most others shouldn't be so bad)

-That didn't take as long as I thought. Still, there are a good number of changes that were made. Mostly it involves optimizing code and adding a harmless* imul ezx, 4 command in there.

Focus:
D8 - 0x5C52F8; 100
E2 - 0x5C4BAF; 100
E3 - 0x5C52F8; 100
E4 - 0x5C52F8; 100
E5 - 0x5C52F8; 100
E8 - 0x5C4963; 100
EA - 0x5C4800; 100
EC - 0x5C4651; 100
F5 - 0x5C4253; 100

I'm pretty sure those are all the cam ops that use delays or step increments. I don't know where the animation scripts are handled yet, but I'll look for them after I'm done with the camera parts and test them. I have a nice little dif file that shows what I changed from -> to if anyone is interested in trying it out.

* I say "harmless" because I think the register is completely cleared before the value is loaded. More modern processors will probably handle it correctly. Oddly enough, the game loads a byte value into a word-sized register chunk then stores that word-sized register chunk into another value that is modified later. Basically what I added was removing a redundant re-indexing (those are freaking everywhere) and shift some commands down and add a [dword-register] *= 4 command in there. The problem would be if the loading a byte into a word-sized chunk would result in clearing the register or not. If it does then there's no problem. If the upper part of the register still holds a value then the *4 could result in an overflow if the upper word is greater than 3FFFh. It doesn't look like that can happen in any of these cases, but it's now more vulnerable to error and possible BSOD-ing.

Take D8/E3/E4/E5's handler:
Code: [Select]

xor    eax, eaxmov    al, [edx+ecx]mov    ecx, 0xC05FF4imul   eax, 4mov    [ecx], eax

This is actually completely safe by virtue of fuzzy logic. eax was cleared before manipulation so the upper part is empty.

Now take E2's:
Code: [Select]

xor    ecx, ecxmov    cx, 0xBE10F8[eax]mov    edx, [ebp+var_8]mov    eax, [edx+4]movsx  cx, byte ptr [eax+ecx]mov    edx, [ebp+var_4]imul   ecx, 4mov    [edx+4], cx

The problem is in line five when it moves a byte-sized value to the word-sized register. Does the entire word get reset? Very likely. In fact, the entire ecx SHOULD only contain that value at the end of that statement. Since it's only moving a byte, it can't be larger than 255 and multiplying by four would yield no more than 1020 to be stored in that spot (which is the current camera script position).

 

[nfitc1]

 

[nfitc1]

You should probably change your name then.
 
 

Anyways it is the opening and closing battle camera pans. They run at the proper speed but get cut short.

I noticed that when I was showing off that tech demo. There might still be a duration counter that I'm missing. The battle timer begins so far into the initial camera motion. If there is a trigger for that it'll have to be moved down in each script. Try changing the battle mode to 'wait' and see if that makes a difference. I've long thought that the command for making the battle timer wait rests in the animation, but it might be in the cam scripts.
In reference to a prior post of mine, it could be DA, DB, DC, or F1 of the position cam or DB or DC of the focus cam codes. I should extract all the init cam scripts and see if I can find some commonality that they all share. They're all in the exe if someone wants to beat me to it.

Update:
It looks like E6 is also used to create increments in both the position and focus scripts. That won't affect all the scripts, but it would affect some.

 

[Aali]

I wrote these tools to help me read and edit .s files, maybe you can put them to good use. Simply adding more frames to the animations just caused it to cut out early when I tried it but maybe you can figure that out.

sptdump.c: .s file -> text format
Code: [Select]

#include <stdio.h>#include "spt.h"int main(int argc, char *argv[]){ FILE *f; struct spt_header header; int i; int j;  if(argc < 2) {  printf("usage: sptdump <file>\n");  exit(1); }  f = fopen(argv[1], "rb");  fread(&header, sizeof(header), 1, f);  printf("File type: %p\n", header.file_type); printf("Version: %p\n", header.version); printf("Number of SPT entries: %i\n", header.num_spt_entries);  printf("\n");  for(i = 0; i < header.num_spt_entries; i++) {  struct spt_entry entry;    fread(&entry, sizeof(entry), 1, f);    printf(" SPT Entry %i: %p, %i\n", i, entry.field_0, entry.num_spt_struc_183);    for(j = 0; j < entry.num_spt_struc_183; j++)  {   struct spt_struc_183 struc_183;      fread(&struc_183, sizeof(struc_183), 1, f);      printf("  %i: %p %5i %5i %5i %5i %5i %5i 0x%04x %3u %3u %3u %3u\n", j, struc_183.flags, struc_183.x, struc_183.y, struc_183.field_8, struc_183.field_A, struc_183.texture_page, (struc_183.field_E & 0x3F) << 4, struc_183.field_E >> 6, struc_183.w1, struc_183.w2, struc_183.h1, struc_183.h2);  } }  return 0;}

sptbuilder.c: text format -> .s file
Code: [Select]

#include <stdio.h>#include <string.h>#include "spt.h"const char file_type[] = "File type: ";const char version[] = "Version: ";const char num_spt_entries[] = "Number of SPT entries: ";int main(int argc, char *argv[]){ FILE *f; FILE *of; struct spt_header header; int i; int j; char line[4096];  if(argc < 3) {  printf("usage: sptbuilder <infile> <outfile>\n");  exit(1); }  f = fopen(argv[1], "r");  of = fopen(argv[2], "wb");  if(!f) {  perror("input file");  exit(1); }  if(!of) {  perror("output file");  exit(1); }   while(1) {  fgets(line, sizeof(line), f);    printf("%s", line);    if(!strncmp(line, file_type, sizeof(file_type) - 1)) sscanf(strstr(&line[sizeof(file_type)], "x") + 1, "%hhx", &header.file_type);  else if(!strncmp(line, version, sizeof(version) - 1)) sscanf(strstr(&line[sizeof(version)], "x") + 1, "%hhx", &header.version);  else if(!strncmp(line, num_spt_entries, sizeof(num_spt_entries) - 1)) sscanf(&line[sizeof(num_spt_entries) - 1], "%i", &header.num_spt_entries);  else break; }  printf("Done parsing headers\n");  header.field_2 = 0;  fwrite(&header, sizeof(header), 1, of);  for(i = 0; i < header.num_spt_entries; i++) {  struct spt_entry entry;    printf("Parsing SPT entry %i\n", i);    fgets(line, sizeof(line), f);    printf("%s", line);    strtok(line, ":,");    sscanf(strstr(strtok(0, ":,"), "x") + 1, "%hx", &entry.field_0);  sscanf(strtok(0, ":,"), "%hi", &entry.num_spt_struc_183);    fwrite(&entry, sizeof(entry), 1, of);    for(j = 0; j < entry.num_spt_struc_183; j++)  {   struct spt_struc_183 struc_183;   int tmp1;   int tmp2;      printf("%i\n", j);      fgets(line, sizeof(line), f);      printf("%s\n", strtok(line, ":"));      //printf("%s\n", strtok(0, ":"));      sscanf(strstr(strtok(0, ":"), "x") + 1, "%x %5hi %5hi %5hi %5hi %5hi %5i %p %3hhi %3hhi %3hhi %3hhi", &struc_183.flags, &struc_183.x, &struc_183.y, &struc_183.field_8, &struc_183.field_A, &struc_183.texture_page, &tmp1, &tmp2, &struc_183.w1, &struc_183.w2, &struc_183.h1, &struc_183.h2);      struc_183.field_E = tmp2 << 6;   struc_183.field_E |= tmp1 >> 4;      fwrite(&struc_183, sizeof(struc_183), 1, of);  } }  fclose(of);  return 0;}

spt.h: data structures used in both programs
Code: [Select]

#ifndef _SPT_H_#define _SPT_H_struct spt_header{ unsigned char file_type; unsigned char version; unsigned short field_2; unsigned int num_spt_entries;} __attribute__((__packed__));struct spt_entry{ unsigned short field_0; unsigned short num_spt_struc_183;} __attribute__((__packed__));struct spt_struc_183{ unsigned int flags; short x; short y; short field_8; short field_A; unsigned short texture_page; short field_E; unsigned char w1; unsigned char w2; unsigned char h1; unsigned char h2;} __attribute__((__packed__));#endif

 

[Kranmer]

Of course that's all Greek to me.

Well it appears to be C, it should be easy to compile to EXE with a compiler like Mingw,
try installing mingw and msys (both free programs) to the default directory of C:\Mingw
then run mingw from your startmenu and you should get a command box, then copy and paste all the text in those code boxes into TXT files and use the filenames provided sptdump.c,sptbuilder.c,spt.h
then put these 3 files into your
C:\MinGW\msys\1.0\home\USERNAME
folder.
Then in the command line type
GCC -c sptdump.c -o sptdump.o
then press enter then type
GCC sptdump.o -o sptdump.exe

then you will have sptdump.exe then do this for sptbuilder

GCC -c sptbuilder.c -o sptbuilder.o
press enter then
GCC sptbuilder.o -o sptbuilder.exe

then you will have sptbuilder.exe and sptdump.exe files. And that should do it. hope this helps.
NOTE: in the line C:\MinGW\msys\1.0\home\USERNAME where it says USERNAME it should your windows username, so for me its Kram since i log into windows with that username.

 

[nfitc1]

Unfortuanately, I must confess I'm complety at a loss here Obesebear. It would seem reasonable for limit break animations to be stored togheter with the other battle animations, but as long as I know, noone around here has found a trace about them. My information could be outdated, though, I've been away for quiet a while.

I don't think animation length can be automatically adjusted by the game engine. All other animations have a fixed framerate. But then again, who knows.

I thought limit break animations were contained with the magic animations. Pushing some magic anims beyond a certain number seemed to support that theory. Their effects range from 00h - 4Eh. I don't know where these are stored, but it doesn't seem like they're stored in the animation of the actors themselves. They're likely in the magic.lgp somewhere and made to specifically reference bones of the actor.

 

[Kranmer]

I did create a DLL a while ago to allow switching of FPS between values via hotkeys, I haven't had chance to fully test it (i did give it to pitbrat to test but i haven't been on IRC for a while so i haven't had chance to ask him how good/bad it worked).
So if you want to test it, it should allow you to switch between a lot of different FPS values (similar to the speedhack but different because this DLL only sets the FPS for what you choose, so if you choose to run battles at 60fps it will only run battles at 60fps and the field and stuff will stay the same where as the speedhack speeds up the whole game regardless)
So this will make it easier so you won't have to hex edit your EXE (i can make 1 just for battles if need be).
You can get it here
http://www.mediafire.com/?ee02tw422kfml2m
this is also a all in 1 DLL so it also includes other stuff like my AnyCd, load saved games, Always Run, Interface Switcher (only for use with menu overhaul) and move while talking.
here is a list of what the hotkeys are (so to set battles to 60FPS just press and hold the B button on your keyboard then press number 6 on your keyboard (using the top numbers NOT the side keypad))
Code: [Select]

WORLD MAP FPS CONTROLW+1 = 15FPSW+2 = 22FPSW+3 = 30FPSW+4 = 40FPSW+5 = 45FPSW+6 = 60FPSW+7 = 80FPSW+8 = 100FPSW+9 = 200FPSW+0 = 400FPSFIELD FPS CONTROLF+1 = 15FPSF+2 = 22FPSF+3 = 30FPSF+4 = 40FPSF+5 = 45FPSF+6 = 60FPSF+7 = 80FPSF+8 = 100FPSF+9 = 200FPSF+0 = 400FPSBATTLE FPS CONTROLB+1 = 15FPSB+2 = 22FPSB+3 = 30FPSB+4 = 40FPSB+5 = 45FPSB+6 = 60FPSB+7 = 80FPSB+8 = 100FPSB+9 = 200FPSB+0 = 400FPSM+1 = Move While Talking V1 (glitched cloud but works at events)M+2 = Move While Talking V2 (Doesn't work correctly at some events)M+3 = Access Menu While TalkingM+4 = Highwind land on dark parts of the map or in forest's (Don't use on other vehicles only on highwind)M+0 = Undo Move While Talking, Access Menu While Talking and Highwind landingCTRL+F3 = Always Run OffCTRL+F4 = Always Run OnCTRL+F5 = FFX Normal InterfaceCTRL+F6 = FFIX Normal InterfaceCTRL+F7 = FFX 9999 InterfaceCTRL+F8 = FFIX 9999 InterfaceCTRL+L = Load anywhere (press twice in field or once if in the in-game menu) NOTE: DO NOT USE THIS WHILE ON THE WORLD MAP (you can load saves on the world map just don't press CTRL+L on the world map)FF7AnyCDv2 Built in

NOTES:
1. Set the FPS before you go into the desired part, so set the battle FPS before going into battle, Set the world map FPS before going to the world map, Set the field FPS while on the world map or in battle.
2. To run at over 60FPS you may need to disable Vsync in Aali's Driver and in your graphics card driver's control panel.

 

[ficedula]

As far as the field, I don't think we have anything that lists which animation is used by whom.   Though we could manually make a spreadsheet with each animation listed, then use Makou Reactor to go through each scene to find out which .hrcs are using which animations.

If you download Ifalna, there's a file in there (ifalna.filter) that lists for each HRC file, what field animations it thinks are associated with it.

It was generated based on parsing the field files, and this was done over 10 years ago when the format wasn't understood so well, so no guarantees it's totally accurate; but, it shouldn't be too far off.

 

[DLPB_]

I sent my findings to Dziugo, who in his god like knowledge of assembly showed me where it is going wrong.  So now Cait's reels work properly at 60fps, the way they did with PSX. 

I can't get anywhere with Tifa's slots, but assuming he has the time, I am sure Dziugo will!

To correct Cait's slots for use at 60fps:

0x6e2138: mov byte ptr [00DC3B6C],04
0x91eacc: set to 20

In ff7.exe this is simplified as:
002E153E: Set to 04
0051D4CC: Set to 20

I will look at Battle Arena slots myself.  Don't want to pester people too much

 

[Borde]

I'm impressed by the amount of progress this project has seen since the last time I checked. Great job guys.

As for my end, I finally have good news. After spending countless hours checking and rewriting my encoding/decoding functions,I found out what went wrong... at a completly different place. Turns out I was ignoring the root rotation. It was suposedly ignored by the game, but looks pretty damn clear it's not. That was also the reason why Cid's fleeing animation was wrong.

 

[Borde]

I think I solved all the problems regarding animations interpolation, so at least that's one less problem. The new version of Kiimera allows you to interpolate automatically all the animations in the game so there is no need to process one by one any more, either.

We still need to get effects interpolated. Anyone has information about them?

EDIT: Aali has been researching about effects and found out pretty much everything is hardcoded into the EXE. That means that getting interpolated effects implies finding all the functions used by effects and modifying them to work at the new framerate. I'm sorry to say I think the future of this mod looks very grim...