Jump to content

meganoth

Moderators
  • Content Count

    4,509
  • Joined

  • Last visited

  • Days Won

    13

meganoth last won the day on September 28

meganoth had the most liked content!

Community Reputation

715 Shiny

1 Follower

About meganoth

Backer
  • Rank
    Community Moderator

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I was making the point mostly about hardware (i.e. the minimum specs), but also about dev time. Corners have to be cut to finish in this millenia as well.
  2. 1) Story is kept secret for a lot of games in development. Especially in story-heavy games like full-blown RPGs, sure. But even in this game I see no reason for them to spell out everything even if the story is already written in detail. 2) For a long time now they have revealed features only once they have them fully implemented. We simply don't know whether a full script exists, but we know that the story can only be put in once NPCs are available.
  3. I would call it sloppy design. But look at what else is cutting corners in this game because a small dev team is making a huge game on insufficient hardware (at least for the level of optimization they can afford). Too few zombies, no detection of inside/outside or walls between sounds, all to save CPU cycles or development time. The game has compromises everywhere. With a team 5 times as much as TFP has you could implement atomicUS5000 suggestions and it would be a full stealth game inside the game and still get all the other features they want in the game. Or not, Bethesda had developers galore and still their offerings had lots of holes to critizise. It may be a cop-out to point to other sloppy stuff, but IMHO this small auto-aggro feature exists exactly because it allows the POI designers variation at the cost of very few lines of code.
  4. Steamcmd was updated twice? That sounds unusual. I just started steamcmd as well and it did update, but only once. Any<way, the systemd output shows he tries to do the update which seems to be followed by steamcmd restarting, which fails. My guess is that the update failed as well since you had to update by calling it manually. It might be because of the shutdownonfailed command and some routine mistaking this for an error (timeouts, return value different, who knows) it never gets past the update. You should do another reboot to see if it upgrades now. If I'm right it will work now because the steamcmd update has been done and won't interfere anymore. My stderr.txt after doing the upgrade was not empty by the way: CApplicationManagerPopulateThread took 0 milliseconds to initialize (will have waited on CAppInfoCacheReadFromDiskThread) CAppInfoCacheReadFromDiskThread took 139 milliseconds to initialize Now, running a script you have in your users home dir as root is practically giving everyone who might hack into your user account a direct way to get root privileges, you might as well just run everything as root. And maybe there are even safety checks somewhere to prevent steamcmd running as root. So, independant of your problem, I would advise to redesign the service to run the script as the user. Just google for "systemd run service as user" and you will find lots of info on how to do that . It basically is two lines in the service file giving userid and groupid of the user. Also make sure that no files in your home dir have owner root after you make this change, i.e. do "chown -R tatilumini /home/tatilumini". Especially if the update worked with the root script there might be lots of files owned by root now in there.
  5. What does /root/Steam/logs/stderr.txt say? Did you try out if steam works if started from root? Maybe there is some safety-code in steamcmd to not allow running as root
  6. I would try to give the ports different IP addresses. One IP on different NICs is unusual enough that hidden bugs might sit in the linux kernel, in steam, the router, EDIT: the NICs firmware, .... comfortably undetected.
  7. I'm not sure line of sight is calculated. I seem to remember a statement by Fataal that it costs too many CPU cycles. ??
  8. It does work with auto aggro zombies. Tested in the game. What you might be thinking of is when the zombies despawn and reappear as sleepers. But we are talking about running away and leaving them standing around but awake (using small stones is very effective there). They don't enter sleep state anymore, just clueless state.
  9. We agree on stable, optimized and bug free (while I know for sure that it never ever will reach "bug free" and "optimized" is also not some flag post that can be reached). EDIT: And yes, those are targets for the release version, how we reach that is TFPs problem. We definitely don't agree on what "playable" is supposed to mean. I can only speak for me and a few people around me, but I play pure vanilla a lot. And judging from the conversations here a lot of other people do too.
  10. You posted in the console section, but your bug report is about the PC version. So I moved your thread over to the PC section. Yes, I think there could be improvements to the save system to make it more robust. Probably TFP has to invest some time into this eventually as it isn't release-worthy in my opinion. Still, while the game is in EA, you should expect such issues. Just make regular backups of the save game.
  11. "game supposed to be". Yeah well, so your taste is the center of the universe, and the devs and lots of other players tastes are aberrant and misguided. Sure. Go ahead. Makes discussion easy. You are right because you define you are right.😆
  12. Wrong folder, you went down Data instead of Mods. The error message seems to indicate that there is a directory named "modinfo.xml".
  13. I think you are completely right. Chickens are birthed in hot oil, live in card board boxes and have a crust. They can't lay eggs. But you can order an egg salad with the chicken, though the eggs were never touched by that chicken in any way. Chickens also can't fly, otherwise we would call them vultures.
×
×
  • Create New...