HebaruSan
-
Posts
4,995 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Bug Reports
Article Comments posted by HebaruSan
-
-
20 minutes ago, IncongruousGoat said:
All you can do is come up with a Chinese name, completely separate from the other one, and just use that.
That would work perfectly well for the game, though. 张伟 and 王芳 are not going to care that the characters they see don't mean "Gene" or "Linus."
-
Congratulations on a job well done. You leave behind some big shoes to fill.
-
8 minutes ago, JJE64 said:
The worst part, and I'm far too lazy to actually look for it, but I remember talk back when 1.0 was released where the devs came right out and said the best solution was to use a different engine, but declined to do so because it was too much work.
I'd be interested to see that quote, if you can find it. It's possible they were talking about the need to migrate to Unity 5.
8 minutes ago, JJE64 said:Here we are a year and 8 patches/releases later and hundreds of labor hours have been invested in still trying to hammer that square peg into a round hole.
I guarantee it's way more than just hundreds. Just one developer full time for a year is around 2000, and they've got several devs and probably worked overtime.
-
2 minutes ago, CaLVin-K said:
does it really? well then 128bit because its a bigger number! yea!
Well, not infinite, but hundreds of millions of times larger than the limit for 32-bit (4 GB).
-
1 hour ago, 5thHorseman said:
When I bought plane tickets for a vacation. I fly in 10 hours... :/
Have a good trip! We'll be right here when you get back.
-
26 minutes ago, KSP Bros said:
Another version would be that only a limited number of people could download every minute or hour, keeping traffic down.
Rather than a tantrum factory, that would be like how the US converted all production to military during WW2, except for tantrums.
-
Just now, Robotengineer said:
And people could have chosen to play .90 instead of the buggy 1.0 releases.
How could a new player who just bought the game after 1.0's release have gotten 0.90 instead of 1.0? How could a Steam user with auto-updates enabled have done the same if they didn't know the update was coming?
A full, publicized release puts the code out there in a way that it just isn't otherwise.
-
5 minutes ago, Robotengineer said:
It's a job some of us would like to do, but will not get the opportunity to do. Plus, how is what you just described any different from the series of patches after 1.0?
New players and Steam users who choose not to opt in will be playing 1.0.5 instead of the newer, less stable version during that two week period. There will be 1 update/download cycle for GoG and store users instead of 5. Problem reports on the forums will be couched in the less entitled "opt-in" mentality, since anyone reporting a problem explicitly chose to look for problems.
-
A farmer finds a magic lamp in his field. A few rubs later, the genie says, "Make a wish, but know that whatever I do for you, I will do the same thing doubled for your neighbor."
The farmer thinks for a moment.
"Pluck out one of my eyes."
-
7 minutes ago, Speadge said:
If I were SQUAD, all this flaming, whining & Co would be reason for me to cancel the pre-release.
This argument will probably not be very persuasive to someone whose stated goal is to cancel the pre-release.
-
17 minutes ago, Red Iron Crown said:
users who bought through Steam are being given preferential treatment in the form of early access.
It's also been stated by a member of staff that the version available in this way is not recommended for normal use. I'm not so sure that temporary access to an incomplete product is preferential treatment.
17 minutes ago, Red Iron Crown said:I expect that the percentage of Steam players who ignore the 1.1 beta releases and keep playing the "official release" to approach zero, whether they intend to provide bugtesting feedback or not.
I suspect a rather smaller proportion of players than that monitors the forum and dev notes. If this works like other betas on Steam, it'll be hidden behind a dropdown in a properties dialog, so a more casual player who just has occasional fun blowing stuff up on the launch pad will probably be on 1.0.5 till the official release, Steam or not.
17 minutes ago, Red Iron Crown said:There will also be people looking for support along the lines of "I see people posting about 1.1 and sharing screenshots/videos of it, but I can't find it on the store and the patcher doesn't work. How do I get this latest version?" Is the answer to this seriously going to be "You don't, you bought it from the wrong outlet"?
The plan is to have a separate sub-forum for the pre-release, right? It wouldn't be that hard to write a sticky post explaining what it's about. Though I don't envy the forum mods who may be faced with a flood of posts that need to be moved into that forum.
17 minutes ago, Red Iron Crown said:And where does this leave modders? Should they not release 1.1 versions until it's out of beta because not everyone has access?
No, they should not release 1.1 versions until it's out of beta because changes during beta might break such mods, because it's normal to expect a delay in mod updates, because it's very reasonable to tell people to wait two weeks (no one even needs to know if you finish early!), and because they'll need much of that time to catch up on development anyway. I may try out the pre-release, but if I do, it'll be pure stock only.
17 minutes ago, Red Iron Crown said:How are modders who bought KSP through non-Steam outlets supposed to get a head start on updating, which is one of the beta's goals?
SQUAD staff stated in this comment section that such persons should send private messages to make arrangements, so this concern seems to have been covered. Maybe that should be appended to the OP to catch the eye of non-Steam modders more readily.
17 minutes ago, Red Iron Crown said:And I don't even want to think of how CKAN will handle having two "current" versions of KSP being in the wild simultaneously, any approach there is going to cause additional support issues, too.
CKAN has the ability to track multiple versions of a mod, each tagged specifically to which KSP versions it requires. I can still switch over to my 0.90 install and add/remove compatible mods for it if I like as long as the download links haven't gone dark. So that should work out fine if some modders do decide to release early, unless I'm misunderstanding your concern.
17 minutes ago, Red Iron Crown said:So as I see it, the public beta is not going to significantly improve the bugfixing phase
We'll just have to wait and see; no one can honestly claim to know at this point. Presumably SQUAD will be paying careful attention to learn whether this approach makes sense for future releases.
17 minutes ago, Red Iron Crown said:Please consider the above as constructive criticism and reconsider this move.
It was quite constructive, so thank you for that and all the other efforts you've put in.
-
8 minutes ago, KerbonautInTraining said:
E: When I press next (or prev, first, last, etc) this comment section freezes. Refreshing will load the requested page. Anyone else experiencing this?
Yes. I've been opening the page number links in new tabs, which seems to bypass whatever the problem is.
5 minutes ago, Damien_The_Unbeliever said:Fast forward to R - 3 Weeks. Squad looks through all of the applications. And basically say "Yes" to anyone who selected Steam and "No" to everyone else. They then send email instructions to those they've said "Yes" to with nicely personalised instructions on how to obtain access through Steam (see, that's why they needed to ask). All the "No" people are informed (but, without having a reason to suspect, what are the chances that anyone will work out the pattern to who was accepted?)
You are a true evil genius. I think the one material difference, though, is that your scheme is more busy work for SQUAD. Their way, they tell Valve, "Pls turn on the opt-in beta option and here's download #1, more to follow," and the opt-in distribution takes care of itself once they post the single public message with the instructions (N.B., everyone posting "sign me up"
). Your way, they would have to have somebody reading all of these extra messages to find out who was naughty or nice, then sending all these emails (or managing their automation) and dealing with recipients' spam folders, mistyped addresses, etc. A small but still unnecessary hassle.
-
SQUAD is going out of their way to help mods be ready on release day (!!!!), and we're complaining?
On the topic of rereading the OP, there is this (emphasis added):
QuoteTypically a select group of particularly KSP-savvy modders would be given access to the new update to help us find bugs, but the extent of the changes this time around is such that we feel we should open it up to everyone.
It's pretty clear that SQUAD also sees this plan as an opportunity to make this unprecedentedly massive update more stable.
). Your way, they would have to have somebody reading all of these extra messages to find out who was naughty or nice, then sending all these emails (or managing their automation) and dealing with recipients' spam folders, mistyped addresses, etc. A small but still unnecessary hassle.
The Weighting of Fonts
in Developer Articles
Posted
Maybe the Chinese space program can supply appropriate substitutes.