Notifications
Clear all

[Sticky] Classic Survival Horror Framework – V2.0 | Dev Log

7 Posts
2 Users
1 Reactions
66 Views
Hosna
(@hosna)
DEVELOPER Admin
Joined: 6 months ago
Posts: 353
Topic starter   [#80]

v2 classicsmall2

This thread is dedicated to the development of Classic Survival Horror Framework V2.0, sharing progress, new systems, enemies, improvements, and features coming with this version.

All details, progress updates, and new changes coming with this version will be shared in this thread. We're excited about this new version and looking forward to sharing the progress with you.


This topic was modified 2 weeks ago 3 times by Hosna

   
Quote
Ben4886
(@ben4886)
Patreon Hunter Registered
Joined: 5 months ago
Posts: 98
 

I'm using V1.8. How will be best to integrate my project with V2?



   
ReplyQuote
Hosna
(@hosna)
DEVELOPER Admin
Joined: 6 months ago
Posts: 353
Topic starter  

@ben4886 Since V2 includes changes to the spawners, enemies, and some other core systems, I recommend downloading a fresh copy of the framework V2 and then manually migrating your custom Blueprints and any code you've written into the new version. This approach helps avoid conflicts and makes the integration process correctly.

Another approach is to review V2 and manually apply its changes to your existing project instead of directly copying files (which I don't recommend at all). This gives you more control over the integration and helps avoid potential conflicts.


This post was modified 2 weeks ago 6 times by Hosna

   
ReplyQuote
Ben4886
(@ben4886)
Patreon Hunter Registered
Joined: 5 months ago
Posts: 98
 

@hosna I've made changes to things like the Zombie Master and Zombie Normal, how will be best to migrate these over without overwriting the new blueprints and breaking the updated versions. It would be too time consuming to add everything manually again



   
ReplyQuote
Hosna
(@hosna)
DEVELOPER Admin
Joined: 6 months ago
Posts: 353
Topic starter  

@ben4886 Hey ben, I completely understand your concern, however, Because Unreal Engine doesn't provide a fully automatic or conflict-free way to merge heavily modified Blueprints, some manual migration is usually required after major updates.

This is a common challenge with most complex Unreal Engine frameworks and Marketplace templates. Once core Blueprints have been customized, there isn't a reliable way to automatically merge them with major updates.

The most reliable approach is to compare your custom versions with the new V2 Blueprints and manually migrate your changes where needed.

I know it can be time-consuming, but because V2 includes structural changes to some systems, this is the most reliable way to preserve your custom work while taking advantage of the new improvements.

By the time V2 is released, Future updates will mainly focus on improvements, fixes, optimizations, and smaller features.

For future updates after V2, we'll do our best to document all relevant Blueprint modifications on the DIY page with detailed text-based changelogs, making it much easier to apply and merge those updates into customized projects.


This post was modified 1 week ago 2 times by Hosna

   
ReplyQuote
Ben4886
(@ben4886)
Patreon Hunter Registered
Joined: 5 months ago
Posts: 98
 

@hosna Yeah, i was afraid of that 😆 

I'll just use 1.8 as the test to get things working then. V2 will be the full project



   
Hosna reacted
ReplyQuote
Hosna
(@hosna)
DEVELOPER Admin
Joined: 6 months ago
Posts: 353
Topic starter  

vsmal2

New V2 preview video is now available!

This video showcases some of the new content currently being added to Classic Survival Horror Framework V2, including new enemies, the flamethrower, and more.

V2 is on the way and we're currently targeting an August release.

Thanks for your support 😊 


This post was modified 4 days ago by Hosna

   
ReplyQuote
Share: