-
Posts
563 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Everything posted by Wooks
-
Welcome my friend!
-
[Stock] The 30 Second Altitude Challenge- Revived for 1.0!
Wooks replied to Jodo42's topic in KSP1 Challenges & Mission ideas
Look at the upper left corner, there you'll find the ingame mission time or elapsed time, it clocks 30 seconds on the mark. If you get green numbers in the clock it means that the ingame clock is running at "real life" speed, one second ingame is equal to one second "IRL". Normally you get this running ships with low count part on a decent computer. Yellow or red numbers means that the time inside the game is running slower than "IRL", each second ingame elapses depending on the time it takes to calculate the graphics. This happens with higher count part or slower computers. -
[1.8.x] AutomatedScienceSampler - V1.3.5 - 18.10.2019
Wooks replied to SpaceTiger's topic in KSP1 Mod Releases
Excuse my ignorance, I downloaded the .zip, how do you install this? -
An auspicious beginning
-
Around-Kerbin Airliner Challenge
Wooks replied to Vectura's topic in KSP1 Challenges & Mission ideas
Maybe Mechjeb in a separate tier? Dunno. Hoping to update my entry today. -
Around-Kerbin Airliner Challenge
Wooks replied to Vectura's topic in KSP1 Challenges & Mission ideas
The important part of your statement: IF -
Around-Kerbin Airliner Challenge
Wooks replied to Vectura's topic in KSP1 Challenges & Mission ideas
Can we please keep this thread on topic guys? For all the new guys and girls joining the forums (and some old ones): It is frowned upon in the "Challenges" section to complain about how difficult is to complete a challenge because of hardware limitations. Why? because more often than not the challenges are designed to push the very limits of the game, bordering the unplayable in some cases. If you can't complete a challenge because your computer can't handle it, then don't do it, search for a challenge more fit for you... or even better, try your hand at creating your own challenge! What's not frowned upon is to ask for more details if the OP is not clear enough, for example: altitude limits, speed limits, how many parts can I use, mods allowed, how much time to complete, etc. Remember, you are joining a community that has been playing this game for a long time, we challenge ourselves just to see what we can achieve beyond the normal scope of the game. These challenges are just for fun, we are here just to have a good time trying to break the game or our computers, whatever comes first. Just have fun, try to be civil and don't forget to be kind. -
Kerbin Circumnavigation 1.0.2 - Aviator Challenge
Wooks replied to Fengist's topic in KSP1 Challenges & Mission ideas
Are East / West circumnavigations allowed? -
As I said before, an issue SQUAD needs to work on: time management, scope of updates, Q&A workload. The era of "not time for this" has come to an end, is time to put the man pants and start weeding those minor glitches and bugs while working on the rest of the bigger issues. I agree with you Lord Aurelius and DeltaB, despite what happened at v1.0 launch this game is awesome... heck it has been awesome from a freaking long time, I've been around since 0.23 and wow, just wow, what a game.
-
More or less the crux of the issue. I would love to see more people discussing this instead of the already trite "let's defend SQUAD from online bullies", I do believe SQUAD needs to learn a very important lesson with the v1.0 release about time management, Q&A, scope, hype building and community management.
-
I'm not assuming anything pal, I'm working with what has been said in this (very, very lengthy) thread. And lets be clear, the process to test v0.1 after release obviously didn't worked, is not news to anyone. I can only hope for SQUAD to learn the lesson and rectify their ways for future updates, basically "do what you did for all updates up to v0.90".
-
I wholeheartedly agree with a small team tackling experimentals, and it certainly worked fine when the releases where rather small and controlled with a lot of wiggle room timewise, but this release was different in scope and size compared to those versions. I believe the issue here is that SQUAD tought they could pull this v1.0 the same way and it just went over their heads, too many changes in such a compact time frame, a rather small team of testers focused on testing all the new mechanics and features, and certainly not enough testing of the finished product before releasing into the wild. Is a little bit pointless to keep repeating that this should have been v0.95 now that the cat is out of the bag but, hey! here we are. I agree with this too. It might seem like v1.0 was tested properly... from the standpoint of the handfull of testers that did it in a breakneck pace over a bunch of rushed weeks. Is clear now that v1.0 needed either more testers to work out bugs in such a hurry, or more testing time with the current batch of testers.
-
The game looks gorgeous, it loads faster and runs like a champ, the new gameplay mechanics and features are fun and interesting, so much to see and do! This has been a great release overall... ... but this should have been v0.95, not v1.0, the hypetrain just steamrolled all over you guys on SQUAD , I believe you placed the bar a little bit higher than you should have and that's what's triggering this weird response.
-
Been there, sometimes you think of a beautiful idea that looks so freaking good in your mind... but is just too damn big to tackle it by yourself: Making vids is a passion project, only a handful of people find themselves in the lucky and well deserved position of being able to make, at least, some revenue from them. If you have no other drive than your passion, then unleash what you have, find a middle ground and make a compromise: - Take your old footage and find what you can save, keep an open mind, don't be obsessive. - Find what's missing or in need of a remake, find a way to make it on a schedule, something like "one hour a day for the next 2 weeks" or "5 / 10 hours a week, be it one single session or several for the next month" - Don't feel bad if you can't finish it, do your best, release pieces of it, make a compilation. What I'm trying to say is: put things in motion. Have a hard deadline for the final form of the project, and in the meantime produce extras that will make you feel you are making progress. - Look for help. I've done some collaborative work with other KSP fans and, let me tell you, you feel less alone and more compelled to finish your work if you have someone as passionate as you driving a project forward, be it modeling ships, recording footage or editing it. PM me if you want to discuss this further if you are interested in some feedback. - Have freaking fun doing it. This is hard. Don't pressure yourself into finishing this project unless you FEEL THE NEED to finish it. ... that's all I got, I wish you the best of lucks in this, hope you can find a way to work your way through this.
-
Ah yes, tweakscale is a fun mod, check the latest SWDennis video to see his Death Star.
-
200 meters high, single launch, all experimental and test launchs finished, recording and gathering data tonight.
-
The Snack Tournament: Aerial Racetrack Challenge
Wooks replied to Wooks's topic in KSP1 Challenges & Mission ideas
That's why I have to update it, all tracks are in an old version of the game and things are not behaving properly. -
The Snack Tournament: Aerial Racetrack Challenge
Wooks replied to Wooks's topic in KSP1 Challenges & Mission ideas
I'll need to update this challenge, the tracks are outdated and I want to make room for more flexible rules, expect changes after this weekend. -
wat is this i don't even have some rep.
-
100% Stock, fully functional Submarine with transport ship.
Wooks replied to Wooks's topic in KSP1 The Spacecraft Exchange
Those are very cool concepts indeed, how you manage the part count? you weld the parts? -
The Chunkin' Challenge -- Haul Out your Trebuchets!
Wooks replied to Starwhip's topic in KSP1 Challenges & Mission ideas
Seems like OP took a vacation.