search

opentomb / OpenTomb

An open-source Tomb Raider 1-5 engine remake
http://opentomb.github.io/
GNU Lesser General Public License v3.0
1.39k stars 145 forks source link

Is project dead? No updates in 2 Years? #608

Open tprivaterep opened 2 years ago

tprivaterep commented 2 years ago

Is project dead? No updates in 2 Years?

stohrendorf commented 1 year ago

@TeslaRus has to answer this.

TeslaRus commented 1 year ago

Hi, have no ideas / motivations for updates.

Helenah2020 commented 1 year ago

Hi, have no ideas / motivations for updates.

I don't understand why nobody else has taken over after the amount of whining towards Eidos and Core Design to release the source code people did, it's funny how people can act out with desperation but then show no seriousness to reflect the desperation. Seriously, for more than a decade now, people have hounded Eidos and core Design to open source their classic engines, and now this? I've been looking through the source code of OpenTomb myself, and even planning to read the RosettaStone documents. I was reporting bugs as if people would respond to them but I also noticed that nobody has been releasing updates for this engine. I understand developing something of this scale is difficult but I just don't understand why people take on such a huge thing only for it to just get abandoned and nobody contribute to it again. While Tomb Raider 1 is mostly playable, Tomb Raider 2-5 seems very buggy.

Helenah2020 commented 1 year ago

Hi, have no ideas / motivations for updates.

I tried to contact you directly but I couldn't, please give me some advice on the best way to contribute using GNU/Linux systems as this is all I use and all I will use, I have no intentions on using anything else. For one it would be nice if I could open the game files in a viewer program, all I'm finding is a Windows program called Tomb Viewer which does not help the situation. I am wanting to attempt to fix issues in Tomb Raider 1 and 2 such as untextured areas at Lara's home in Tomb Raider 2, Tomb Raider 2 bats which do not fly but are always on the ground, there are certain bits of terrain in Tomb Raider 1 that you can fall through. I believe that when Eidos/Core Design made these maps, they used code to work around terrain glitches and stuff, I'm wanting to view these files to analyse and see if my theory is correct.

Popov72 commented 1 year ago

If all you want is to view level files, you can use OpenLara or Tomb Raider Nostalgia - http://www.evpopov.com/. Disclaimer: I'm the author of the latter!

TeslaRus commented 1 year ago

Hi, have no ideas / motivations for updates.

I tried to contact you directly but I couldn't, please give me some advice on the best way to contribute using GNU/Linux systems as this is all I use and all I will use, I have no intentions on using anything else. For one it would be nice if I could open the game files in a viewer program, all I'm finding is a Windows program called Tomb Viewer which does not help the situation. I am wanting to attempt to fix issues in Tomb Raider 1 and 2 such as untextured areas at Lara's home in Tomb Raider 2, Tomb Raider 2 bats which do not fly but are always on the ground, there are certain bits of terrain in Tomb Raider 1 that you can fall through. I believe that when Eidos/Core Design made these maps, they used code to work around terrain glitches and stuff, I'm wanting to view these files to analyse and see if my theory is correct.

Hi! The same named email should work tesla.rus@.gmail.com But I rarely check it. Too much programming at work and over-engineering. In a free time I prefer make things by my hands (i.e. electric circuits, tools), repair some tools, schemas. In current state of OT engine I do not like how animations works, targeting (fire ray trace), looks / targets mutators, enemies moving.

Helenah2020 commented 1 year ago

Hi, have no ideas / motivations for updates.

I tried to contact you directly but I couldn't, please give me some advice on the best way to contribute using GNU/Linux systems as this is all I use and all I will use, I have no intentions on using anything else. For one it would be nice if I could open the game files in a viewer program, all I'm finding is a Windows program called Tomb Viewer which does not help the situation. I am wanting to attempt to fix issues in Tomb Raider 1 and 2 such as untextured areas at Lara's home in Tomb Raider 2, Tomb Raider 2 bats which do not fly but are always on the ground, there are certain bits of terrain in Tomb Raider 1 that you can fall through. I believe that when Eidos/Core Design made these maps, they used code to work around terrain glitches and stuff, I'm wanting to view these files to analyse and see if my theory is correct.

Hi! The same named email should work tesla.rus@.gmail.com But I rarely check it. Too much programming at work and over-engineering. In a free time I prefer make things by my hands (i.e. electric circuits, tools), repair some tools, schemas. In current state of OT engine I do not like how animations works, targeting (fire ray trace), looks / targets mutators, enemies moving.

Thank you for the email address, my progress so far is that I have byte-for-byte interpreted the contents of PHD files using my own code to better learn how things work.

Helenah2020 commented 1 year ago

If all you want is to view level files, you can use OpenLara or Tomb Raider Nostalgia - http://www.evpopov.com/. Disclaimer: I'm the author of the latter!

Weird that I didn't come across your project, sounds like a viewer I was wanting rather than a gaming engine. As for OpenLara, check out this issue: https://github.com/XProger/OpenLara/issues/470

vvs- commented 1 year ago

I don't understand why nobody else has taken over after the amount of whining towards Eidos and Core Design to release the source code people did,

Did you look carefully enough? There are at least eight other active TR engine projects. At least one of them is 100% compatible with original TR1 and yet has many enhancements and bug fixes. And as mentioned above there are several TR viewers and editors available.

P.S. As far as original source code is concerned it was already leaked years ago. Seems that this actually had negative impact on reverse engineering efforts.