- Jul 27, 2017
- 42
- 50
I liked the first one quite a bit, but man, this one's just awful. Even the character models are less attractive
Generally I wait for the bugfix and mod to be updated to the newest release before attempting it. It's always been stable for me after that. If you are trying to apply the current bugfix/mod to the 36.1 game right now, it won't work out too well I am sure.Is this a massively buggy mess for anyone else? All I get is error after error after error after error....
I have not noticed a significant drop in visual quality from any compressed versions of games.Does the compressed version change the quality of the graphics a lot? Just wondering which I should download.
It's a bit complicated until you get used to the layout.6th attempt to even get a single production line functioning... I set the dam design - done... I set the research and got the minimum points - done. I went to production and it has NO SERUM DESIGNS available... even with 3 freaking designs locked down. WASTE of time. 6the attempt at this mess of a game. I can't seem to get the thing to work, so I'm freaking done. I wish all of you well, but the FAQ and walkthrough don't seem to work at all.
And make absolutely certain your serum design doesn't have -money traits.Anyone having trouble staying solvent with their first serum only needs to remember these four steps
Research basic med trait and then create a serum with that trait and research that too
Total supplies must be kept higher than production output
Fabrication of serums after researching them requires configuration in production
Marketing requires serums marked for sale
I'm curious about that too. What is it about the LR2 updates that make them all (all that I've seen, at least) incompatible with previous incarnations? Most other games seem to occasionally have that happen, and it's understandable in a lot of instances, but it seems like it's ALWAYS the case for LR2, even when the contents of the changelog don't seem to indicate any changes to the game, stat blocks, etc. that would make that happen.is it really that hard for a developper to make a new version backwards comatible with
older saves?
not ment as a comment , just a questin because i dont know anything about devolopping games
(just play them)
It's not a problem at all for a linear virtual novel. But this kind of game is not linear but includes state machines with internal variables (which Ren'py does not handle well when it comes to rollback or save -- which is basically the same for Ren'py). If a new game version has states or variables which the older has not, this has to be handled by the developer, i.e. old saves have to be migrated with special coding. This can be much effort in a complex game and will be a source of bugs as well.I'm curious about that too. What is it about the LR2 updates that make them all (all that I've seen, at least) incompatible with previous incarnations? Most other games seem to occasionally have that happen, and it's understandable in a lot of instances, but it seems like it's ALWAYS the case for LR2, even when the contents of the changelog don't seem to indicate any changes to the game, stat blocks, etc. that would make that happen.
The Summertime Saga comparison is interesting. What's weird is that it's ALWAYS the case for LR2. I don't have it all laid out on a flowchart or anything, but it seems to me that every iteration breaks previous saves. Like no LR2 update is ever just content, it's always also at least a code rewrite. It's not a calamity or anything, but it does track to me like a lot of really rather minor tinkering constantly going on rather than actual changes to content/structure. That is, it tracks to me like a lot of backtracking as the code progresses. Maybe in the long run that's a better coding strategy. Hard to say. I'm not going to go through his code and do a whole analysis to figure it out or anything, but it's at least interesting from a big picture/process POV.Summertime Saga is another example of a non-linear game with state machines, which had a save compatibility problem until some time ago (and kind of still has). They put a lot of effort into solving that. Basically, after loading a save, all the triggers which are used by the game engine to transfer the state machines (i.e. the characters) from one state to another have to be re-played in the correct sequence. This works most of the time but not always.