Jump to content

Search the Community

Showing results for '동해출장마사지ㅇㅁㅂ【Talk:Za32】'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Welcome Aboard
  • Kerbal Space Program 2
    • KSP2 Dev Updates
    • KSP2 Discussion
    • KSP2 Suggestions and Development Discussion
    • Challenges & Mission Ideas
    • The KSP2 Spacecraft Exchange
    • Mission Reports
    • KSP2 Prelaunch Archive
  • Kerbal Space Program 2 Gameplay & Technical Support
    • KSP2 Gameplay Questions and Tutorials
    • KSP2 Technical Support (PC, unmodded installs)
    • KSP2 Technical Support (PC, modded installs)
  • Kerbal Space Program 2 Mods
    • KSP2 Mod Discussions
    • KSP2 Mod Releases
    • KSP2 Mod Development
  • Kerbal Space Program 1
    • KSP1 The Daily Kerbal
    • KSP1 Discussion
    • KSP1 Suggestions & Development Discussion
    • KSP1 Challenges & Mission ideas
    • KSP1 The Spacecraft Exchange
    • KSP1 Mission Reports
    • KSP1 Gameplay and Technical Support
    • KSP1 Mods
    • KSP1 Expansions
  • Community
    • Science & Spaceflight
    • Kerbal Network
    • The Lounge
    • KSP Fan Works
  • International
    • International
  • KerbalEDU
    • KerbalEDU
    • KerbalEDU Website

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Skype


Twitter


About me


Location


Interests

  1. Well, truth be told I may be taking a little shortcut. We're getting close to whatever the end is, and frankly it's just more efficient if the main people who need to talk next can do it in the same room. Especially when getting visual effects right can mean an hour of flying people around in jetpacks, dealing with helmet bugs, and trying to orient bridge sets sunny-side up for better lighting etc., for just a couple of panels. If there's any concern about continuity etc., well I did hang a lampshade with the thread title. I was considering having Evil Bob throw even more snark than his "abusing crew transfers" comment by pointing out that the "turbolifts" are just part-clipped lander cans, and why couldn't he just transfer into a docked landing craft? Well if he could do that, why did the boarding parties have to burn through bulkheads etc. to get aboard? I'm certainly not going to explain it! This is why the author's crew compartment is as well-stocked with lampshades as KSP craft are with flags and EVA propellant. Who's to say? A couple of thoughts from a similarly mirrored situation: (1) It is far easier for civilized [kerbs] to behave like barbarians than it is for barbarians to behave like civilized [kerbs], BUT, (2) ruthlessly evil or not, it is possible to be a "[kerb] of integrity" in more than one universe.
  2. The $20M is for just the launch, not the payloads. Several years ago, a SpaceX engineer giving a talk at a conference said their marginal internal cost was ~$25M a launch (I posted the vid here at the time, but it was pulled down—possibly because he talked about those numbers). This was long before they were flying 20 times+, and before they recovered fairings much if at all. So $20M seems pretty reasonable as a current ballpark.
  3. This is something I and others said multiple times throughout EA. I think a lot of anger at the communication/CMs was misplaced disappointment with the development speed. If the game was fun and developing quickly they could’ve talked as much or as little as they wanted. You don’t really need to have a big dev interview once a month if there’s a content update once a month to show what the devs have been up to. A KERB update post is easily replaced by weekly patches with detailed patch notes. Then they can talk a lot, nearly not at all, be sassy like the Wendy’s Twitter, be very proper or whatever other style they want and it wouldn’t really matter. The frustration always stemmed from this being the slowest progressing EA game I think any of us have ever played. With the devs not active (for the most part) interacting with the community that frustration was expressed to the CMs, and eventually it became (unfairly) frustration at the CMs.
  4. Did you really put the "Terrain Implementation" along the Pros of this game ? Damn, it looks so aged, so outdated, so clunky, so weird, inhomogeneous, unaesthetic, etc. Especially with the harsh lightning which got quite improved by the last Blackrack efforts, but I find the terrain to be so 2015, technically speaking, and very not beautiful as an art decision (which is more personal opinion). The only way to get it "OK-Ish" is to compare it to Stock KSP1. But doing so, well, I won't elaborate further, it is nonsense to me as it's just the literal bare minimum. Terrain is very precisely what I was expected the most, because it would mean a LOT for this game, even gameplay wise, with proper collision, scenery, landscape to discover, etc etc, I've already repeated that so many time and now there no point to get to it again. Really, terrain and scenery is the key for a proper KSP2... Everything else fade out compared to what it can bring to the table. Look at the trailer again if you want to talk about it, I don't find much people sharing my opinion so I would gladly elaborate again, finally, if there is some people who want to debate that subject.
  5. So I have a question. The financial call for TT happens on the 16th. People here talk as if it is a public call people can listen in on. Is that the case? If so, how do we listen in, and at what time? My assumption is that we can't, but that the call is made public shortly after it happens. If someone can confirm this, I would greatly appreciate it!
  6. They've actively, literally, contradicted this by saying work was continued between the restructuring. Plus it's literally the same upper management minus Paul Furio who got fired early on, so it's either them practicing corporate diplomacy (with themselves?) or development really wasn't interrupted. Hope one day we get a proper post mortem and a case for devs and publishers to look at and learn from. It becomes a self fulfilling prophecy. They work super slowly > they can't show progress because there's none > there's nothing solid to talk about (and they don't want to talk about plans either because they know they'll be held up to their words, the horror). > they need to space posts more > those posts are still empty because (start cycle again here). Basic bug-reporting feedback right there that you should be telling the authors of reports. In github you get your issues properly tagged if they can't be reproduced, or are believed to be hardware related, or whatever. Reports being archived without saying a single word is a big no no, no matter what single excuse you could write for doing it. Even a "not important" provides at least some closure and safety that the thing was at least read. Not only is the faith in QA testing for this project under the ground, but the bug tracker that had to be fought for "happens" to be ignored and users are made to wait ~1 month to see if top voted issues are even being looked at. Because even those barely have developer interaction, only to be met with "can't reproduce lol". The whole bug reporting-to-feedback process (let alone a "hot" fix that's cold by 2 months at the minimum) is laughably bad and should be set as an example to every dev running a bug tracker on how exactly to not do things. Great way of putting it into words. We're 1+ years into the project and these very basic doubts still linger. Even if they work at the pace of a DMV, they should have a vision they want to pursue and a reason for wanting to repeat all the same mistakes KSP1 made. For all the hate KSP1 received in these forums once 2 dropped, from some people, they're really doing a very basic rerun with a fresh coat of paint and a bigger price tag. Doesn't matter, there's still a missing part to close the loop. It's the same issue the old "mail us the bug" reporting system had. You have no idea what they're doing, if they're doing anything at all, with your report. On which everybody complained about readability and what we got in return was "replace font 2 hard" and some color changes on the navball which is still a mess. Great feedback loop, at least that issue had some closure and we know we need mods to fix that. So you get another black hole place where you don't even know where your feedback goes. The K.E.R.B. is so vital and wanted because it's what's missing to close the loop: feedback on feedback. It's the only time we get to hear about what devs are actually working on, without marketeer language, without hypebeasting, and so on.
  7. Nice, I didn't see any other obvious install issues. I don't really know much about the B9 error, but your log is way cleaner. Hopefully someone else can help pin down the specific error. Personally, I'm side-eyeing IFS just because I hear so many people talk about incompatibilities with it, but I don't have an experience with it myself.
  8. First post on here in a while. Wish it was under better circumstances. To be clear: as of the writing of this post, KSP 2 HAS NOT BEEN OFFICIALLY CANCELLED. Mostly, this is a response to a phenomena I've noticed a lot on this forum: people making statements to the effect of "They promised us they would finish the game, isn't this some kind of breach (possibly even legal)?" Some people are talking about lawsuits, others about refunds. The fact is, early access games are always a risk, both for the publisher as well as the customer, even when they are being developed by a major studio. KSP 2 in particular, is a relatively niche-interest game whose development was seeminly laden with difficult technical problems and other REAL CODING CHALLENGES which have the tendency to make development slower and more expensive than other reliable, mass-market games. Take Two may well decide that KSP 2 will either be unprofitable, or that the money will be better spent somewhere else. They may be right. Unfortunately, there is no known way to design an economic system that both 1) causes companies to waste money on consumers like us and 2) leads to the development of MRI machines, sufficient food to feed the population, etc. A lot of the initial anger back when the game was released was in this context. The anger boiled down to two main points: The game was way less developed than it ought to have been based on previews and pre-development communications. This could have many causes, among them: There were more engineering challenges than expected, or they were more difficult than anticipated Development was being mismanaged There was dishonesty involved Development was restarted due to some unknown reason, possibly some combination of the other bullets All of which indicate that the game's development was significantly more risky (less guaranteed) than what one might otherwise assume, which was/is upsetting to many fans of the game. Especially in light of (1), the asking price of $50 was extremely steep. Not only was the game not worth $50 at that moment, but the development of the game was full of risks and red flags that reduced the likelyhood of successful development even further below that which one would expect from an early access game, which should reduce the price. Since the release, which many viewed as already involving several broken promises, more 'promises' or 'goals' have gone unfulfilled, such as: Frequent communication Updates "on the timescales of weeks, not months" "Major content updates coming within months of each other" And other such conditions which would alleviate risk and speak to a solid development environment. Take-Two's "cost reduction plan" is not a monumental, rare, or unpredictable occurence. It is exactly the sort of thing we should expect companies to do: look to reallocate funds away from things that either lose money or don't make enough money, and towards things that do. We should have had, and should continue to have, the expectation that KSP 2 will be subject to such pressures, AND THAT EXPECTATION SHOULD BE BAKED INTO THE PRICE OF THE GAME. It's no surprise, then, that many of the same people who were fine with the price of the game and many other perceived sleights feel like they are owed some sort of recourse if the game fails. You are not owed anything- your "recourse" was had a year ago when you purchased the game for less than it would eventually cost if it made it to release- you got a bargain, which doubled as your consolation were the game to fail. If you are unsatisfied with your recourse, then perhaps we are in agreement that the game should have been, for instance, $30. All this being said, I hope for the sake of the community, the devs, who I do believe worked hard to make this game succeed and care about the game, and the broader world which stands to benefit from the existence of games like KSP 2, that the worst has not come to pass, and that the game will continue to be developed, and one day release successfully. I mainly wrote this post because it concerns what I believe to be a common flaw in the way people think/talk about "cOrPoRaTiOnS" which irritates me greatly, and I'm not a perfect person.
  9. Which sounds nothing like what they did back to Star Theory. Remember, if it was that, we already know what it looks like. The fact they got offered re-hiring was communicated instantly, and so was that another studio was to continue the game's development. They also got a message warning of this with a lot of time, they were not gagged and were able to talk right then and there. It's a totally different news that we got now, they did not communicate anything similar. "We're firing people and closing projects." Read above. People really like to not look back it seems.
  10. All good, it's your right. But... How long are you going to expect them to deign to explain something to you? A month? One year? a decade? a century? And if you expect someone to talk, it's because you don't understand the corporate fabric. Anyone who breaks the line is not going to be hired even in the competition. Marked for life.
  11. i love this thread so much, it's a rare bastion of unfiltered love and compassion in an otherwise hostile subforum A huge thank you to Intercept Games and all its members. I hope you find work that's good for you, and, even though I bet you're not really allowed to talk about it, I hope whatever it is that happened isn't the downfall of the project you poured your hearts into. I appreciate you all!
  12. The situation could have been similar, though probably less hurtful on head count - that was while the game was in prealpha stages, so there was not much talk anyway, so nobody noticed anything out of normal schedule.
  13. So, if you are all interested in a lot of the back end systems in KSP (scaled space vs local space, PQS, floating origin, floating velocity reference frame, quaternion3d and vector3d doubles,. etc...) I would like to point you to Harv and Mu's Unite talk that took place 10 years ago on Sep 20th of 2013. KSP 1 was not, easy. It took years. KSP 2, would have also taken years, and Juno New Origins has taken years, so has every other major space flight game with any level of simulation. Turns out that not on is "space hard" but making space... is also hard.
  14. I am not sure about that. The game still has so many bugs that it is pretty much unplayable. At least for me. There was a lot of talk about how "Science" was a good update. I tried it and after all the bugs I stopped playing again. It did improve the game. But the game was still bad. I know others have a different oppionions. But for me the game in the current state is still not playable and the Science update did not fix any of the main issues I did have with it.
  15. Nate just released a upcoming update on Steam on 04/25: Hello! It’s been a while! I know that many of you have been wondering about the status of KSP2, so I thought I’d give you an update on how things are going. We have an incremental update on the way! The v0.2.2.0 update will address a number of common user experience issues, some of which have been causing frustration for quite a while. In many cases, a thing that was reported as a single bug (Delta-V calculations being incorrect, or trajectory lines being broken) were actually half a dozen or more closely related bugs. We identified a series of issues that we believed were negatively impacting moment-to-moment gameplay and the first-time user experience, and we dug deep into those bug clusters to make meaningful improvements. Some of those issues include: Parachutes don’t deploy reliably (doubly true when fairings are in the mix) Fairings don’t protect their contents from heating Trajectory lines in the map view sometimes disappear (often related to erroneous designation of craft as “landed” when in flight) Landed vehicles fall through terrain during time warp Maneuver nodes refuse to allow the player to plan beyond the calculated Delta-V allowance, which in many cases is an incorrect value We’ve submitted changes to address a number of these issues – in the case of the last one, we’ll just be letting you plan beyond your current dV allowance while we continue to improve our Delta-V accuracy over the longer term (there’s a very challenging set of problems to solve in the pursuit of accurate Delta-V projections for every possible vehicle that a player can make, so this is something we’ll likely be refining for quite a while). For this update, we’ve also prioritized a new kind of issue: in some cases, the first-time user experience is undermined by a failure of the UI to clearly communicate how to progress between phases of gameplay – put simply, we sometimes put new players in a position where they don’t know what they’re supposed to do next. We’ve received a huge quantity of very helpful user feedback in this area since the For Science! Update. For example, since most of us are seasoned KSP veterans, it never occurred to us that we hadn’t fully communicated that “revert to VAB” is a very different thing from “return to VAB.” We received a rash of bug reports from people who were confused about having lost progress after completing their missions and reverting to VAB. Yikes! Similarly, the lack of a clear call to action when a vehicle can be recovered frequently left new players staring at a landed vehicle and not knowing there were more steps to follow. We’ve made some UI changes to address issues like this, and we think the flow has improved as a result. Another usability issue that even catches me out on occasion -- trying to do illegal actions (for example, parachute deployment) while in time warp states other than 1x. In fact, we believe quite a few bug reports we’ve gotten about actions being broken have actually been the result of people attempting to do things under time warp that weren’t allowed. This is an area of ongoing work for us – not only do we need to do a better job of communicating to the player when they’re warping, but we also need to make clear what actions are and are not allowed under both physics and on-rails time warp. We’ve made some small UI changes to increase the player’s awareness of their time warp state, and we’re looking forward to seeing if those changes feel good to you. I know we talk a lot about the value of Early Access, but this is a great example of how your reporting helps us target our efforts. We still haven’t nailed down the exact date for this update, but we’ll notify you here once we’re on final approach. Most of our team continues to be pointed squarely at the Colonies update. We’re making a lot of progress this month on colony founding, the colony assembly experience, and colony gameplay mechanics. There are lots of interesting problems to solve here – some are super obvious (colony parts exist at a wide range of scales, and the Base Assembly Editor – the colony version of a VAB - needs to feel equally good when you’re connecting a small truss or a giant hab module). Other issues – for example, how vehicles interact with colonies on both the systems and physics levels – come with a lot of edge cases that need to be satisfied. We remain very excited about the ways colony gameplay will move KSP2 into completely new territory, and we’re definitely eager to see what our legendarily creative players do with these new systems. In parallel with our colony work, we’re continuing to find significant opportunities to improve performance and stability. We just made a change to PQS decals that got us huge memory usage improvements – mostly VRAM (this one is still being tested, so it won’t go into the v0.2.2.0 update – but I was just so excited about the improvement that I had to share): And of course, while all this work is going on, Ghassen Lahmar (aka Blackrack) continues to make big strides with clouds. Here’s a peek at some of the improvements he’s working on today (yep, that’s multiple layers)! And because the VFX team can’t ever stop making things better, they’ve begun an overhaul of exhaust plumes to bring them more in line with reality (which thankfully is also quite beautiful): Thanks as always for sticking with us as we work through each challenge – we couldn’t be more grateful to have your support as we move toward the Colonies era!
  16. True. But it doesn't hurt to talk hypothetically and brainstorm solutions. Fact is we know the studio is shut down. We know a number of KSP2 devs have been laid off. And we haven't ruled out that it might be ALL of them. We don't know if the roadmap is on the table. And if it's not I think a class action lawsuit is something worth discussing if for any other reason than to help strengthen consumer protection. It's rare that a AAA company cancels a game in EA. And if you believe it's wrong for a company to essentially break its word just because a few lines on a corporate website says that's ok then we need to fight that policy in court. If the game is cancelled or the roadmap is no longer on the table, we shouldn't waste this opportunity to strengthen consumer protections.
  17. You must have missed the part where I literally said: I'm not trying to be difficult, but you seem to not read all of what I post. I was pretty clear that I'm not a lawyer, that I didn't talk to one, and that whoever takes this up needs to. Please make sure you read what I write instead of making assumptions to drum up drama.
  18. After doing some research this morning, a class action lawsuit against Take Two is viable. While both the EULA and the Terms of Service both indicate that you must use a mediator or 3rd party arbitrator to sort out differences before going to court, there is legal precedence in multiple states that allow for this clause in the Terms to be thrown out, with action moving through the legal system without mediation. The big issue here becomes what state to file a lawsuit in. You have 3 choices: The state the company is headquartered in (New York); The state the game was developed in (Washington); The state you purchased and play the game in (for me, Nevada, as an example) Because we are talking about a potential class-action lawsuit here, the state in which an individual purchased and/or plays the game is nearly irrelevant. And considering that a lot of gaming (in a general sense) happens over the internet, no one state where a person plays a game has jurisdiction. So that option is out. Filing in the state the game was developed is a viable option, provided you can prove that the majority of the work was done in that state. Again, the internet and remote work - especially during and because of the COVID-19 pandemic - make this difficult to ascertain without getting cooperation from the company/developer you want to sue. So this option is probably not the best one. This leaves filing in the state that the parent company is headquartered in. This is the best option for class-action lawsuits as you are trying to gather as many people as possible together who have a common interest and/or complaint about the product they received. New York General Business Law section 350 allows for the protection of consumers against false, misleading, or misrepresentative advertising in products that are sold to the general public. While it doesn't specifically call out digital media, it is considered to be included in this section. Furthermore, New York Civil Practice Law and Rules sections 901-909 deal with class-action lawsuits, providing the framework for how and when consumers can get together and file a class-action. I would like to point out that all of my research stems from a host of Google searches, as well as getting clarification on things from ChatGPT. Yes, I talked to the bot this morning because that is the easiest way to get definitions and information these days. How accurate that is remains to be seen, so take everything I stated above with several grains of salt. But if you really want to go this route - and I'm going to be frank and say that I doubt this would lead to anything substantial in the long run - what I've stated above is probably the best information you'll get from a non-lawyer. So talk to a legal professional before going anywhere else on this.
  19. KSP Interstellar Extended (KSPIE) is a plugin for Kerbal Space Program, designed to encourage bootstrapping toward ever more advanced levels of technology as well as utilizing In-Situ resources to expand the reach of Kerbal civilization. KSP Interstellar Extended aims to continue in @Fractal_UK original KSP Interstellar vision in providing a realistic road to the stars. Players will first gain access to contemporary technologies that have not been widely applied to real space programs such as nuclear reactors, electrical generators and thermal rockets. By continuing down the CTT tech tree and performing more research, these parts can be upgraded and later surpassed by novel new technologies such as fusion and even antimatter power. We attempt to portray both the tremendous power of these technologies as well as their drawbacks, including the tremendous difficulty of obtaining resources like antimatter and the difficulties associated with storing it safely. The goal is to reward players who develop advanced infrastructure on other planets with new, novel and powerful technologies capable of helping Kerbals explore planets in new and exciting ways. The principal goal of KSP Interstellar is to expand Kerbal Space Program with interesting technologies and to provide a logical and compelling technological progression beginning with technologies that could have been available in the 1970s/1980s, then technologies that could be available within the next few years, progressing to technologies that may not be available for many decades, all the way out to speculative technologies that are physically reasonably but may or may not ever be realizable in practice. This is the KSPI-E release thread where we announce any releases of KSPI Extended If you want to chat about KSP Interstellar you can do it at our new Guilded Server (old: KSP Interstellar Discord Server ) For technical questions or Mod support, please ask them in the KPIE Support thread For talk about new development and features request you have to be in the KSPI-E develpment thread Latest Version 1.29.5 for Kerbal Space Program 1.8.1 - 1.12.2 Download older version from Here source: GitHub If you appreciate what I create, please consider donating me a beer you can donate me with PayPal or support me by Patreon Download & Installation Instructions step 1: remove any existing KSPI installation (GameData\WarpPlugin folder) step 2: download KSPI-E and put the GameData in your KSP Folder (allow overwrite) License Info KSPI-E code and configfiles:are distributed under KSP INTERSTELLAR LICENSE Molten Salt Reactor model from USI Core by RoverDude licensed under CC 4.0 BY-SA-NC Tokamak model from Deep Space Exploration Vessels by Angel-125 licensed under CC BY-NC SA Solid Coie NTR, Nuclear Ramjet, Nuclear Lightbulb and Nuclear Candle models and textures from Atomic Age by Porkjet all licensed under CC BY-NC SA Super Capacitator Model from Near Future Electric Mod by Nertea licensed under CC-BY-NC-SA Surface Wrapper Radiators from Heat Control by Nertea licensed under CC-BY-NC-SA Microchannel radiators from Heat Control by Nertea licensed under CC-BY-NC-SA Inline RCS stack by TiktaalikDreaming for Inline licensed under MIT Nuclear Ramjet Model by Lack licensed under CC-BY-NC-SA retractable RCS by BahamutoD licensed under CC-BY-NC-SA Wrapper Tanks from Kerbal Hacks by enceos license under Creative Commons 4.0 Inline Thermal Dish Relay Receiver by @steedcrugeon licenced under CC-BY-NC-SA at JX2Antenna Plasma Wakefield Particle Accelerator Ring by Sin Phi CC BY-NC-SA 4.0 at Sin Phi Heavy Industries If you think I missed something, please notify me Credits @Fractalfor developing the original KSP Interstellar @Eleusis La Arwall for most of the new Reactors, new Power Dish transmitters and Beam generators @zzzfor most of the original models/texturing @Boris-Barborisfor porting KSPI to 0.90 and fixsing many bugs @Northstar1989for providing theoretical basis for many of the new features in KSP Interstellar Extended @SpaceMouse for Magnetic Nozzle, MHD generator and EM drive engine @EvilGeorgefor programming Solar Wind collector and ISRU processing and several other ISRU processes @Cyne Daedalus Fusion Engine Model and Texture @Arivald Ha'gel for helping to fix several issues @MrNukealizer for his help in C# development work on KSPI @Snjo for making the code FSFuelSwitch public available Olympic1 for his help with the integration of KSPI with CTT KaiserSnow for providing Icons for Integration with Filter Extension InsanePlumber for converting part textures to DDS format A2K For helping get KSPI-E on CKAN Bishop149 for Helpi improve the Wiki and OP ABZB for Helping to find many bugs and developing Mk2 EXtension Mod SmallFatFetus for giving permission to use is Vasimr model michaelhester07 for creating Particle Accelerator NathanKell for creating ModuleRCSFX. Trolllception for helping new players understand the tables on the OP and MM scripts Nli2work for creating the Magneto Inertial Fusion Engine @Nansuchaofor helping to create documentation and guides for KSPI-E @th0th for providing Icons for the tech node @Tonas1997 for proving new technode nodes Recommended AddonMods Recommended Planet Packs/Star System/ Galaxy mods: Recommend Tech Tree: Recommended Tool mods: Suggested Challenges: Documentation & Tutotials KSPI is one of the most sophisticated mods for KSP. To help you get started, you can make use of the following resources: KERBAL INTERSTELLAR EXTENDED GUIDE KSPI-E for Dummies KSPI-E Guide by Nansuchao KSPI-E Technical Guide KSPI-E Wiki KSPI-E Youtube Videos: 9 part Russian Tutorial by @ThirdOfSeven 3 part EnglishTurorial by @Aaron Also: Support KSPI-E add support for the following mods
  20. I like history and how humans tend to repeat the same mistakes and not notice when things start to look bad. I could give other examples, such as the scam that ended up blowing up and leaving millions without homes or jobs in 2008, but it is more convincing to talk about WWII, from which money is still made. Captain America and Wonder Woman are my certificate.
  21. They're the kind of people we've always looked for, the kind who drop money and don't talk or question.
  22. hey don't talk about him in the past, he'll still be a great modder and the guy that made KSP2's atmospherics look amazing in like a month.
  23. Scott Manley was steering away from KSP yes but I do feel if the game was good or got good he would’ve made some videos because 1. It’s still fun 2. It would’ve made money. 3. He likes teaching space and it would’ve helped with that. I’m sure he would’ve done new tutorials, probably one career play through, and the occasional video demonstrating something he’d like to talk about in real space. Having got none of those, I think his views are clear. ShadowZone may have presented a very optimistic possibility, but he made a clear line between the facts and the theories, and presented multiple possibilities. I really do think he made a good video on the situation.
  24. Who’s angry? I’m not. did I label you for having an opinion other than my own? You did that with me but I’m not bothered. i am however bothered when you don’t like your medicine. anyway so this doesn’t get me banned maybe we call It a day and agree to disagree or whatever is appropriate around here to end a heated talk.
  25. Well, its worth a shot at least, with the most recent news I have been thinking of actual realistic ways microtransactions could be implemented without directly harming the game with some suggested prices to go along with it.. Also aswell even if they say "no microtransactions" it seems that they need if it if there is rumors that the game is going to be cut, or we will lose developers... As of right now we don't know the situation for ksp 2 and the team.. "unethical" or not if stuff is "cheap" some people will find a use of some things useful while others don't if there was a unethical way to monetize it instead of just being free QOL the game might be better for income.. (problem is t2 launched the game in EA when it was a YEAR away from being anything useful, pretty much destroying the reputation of the game).. Custom Kerbal Creator / Custom Director Kerbal - 5-10$ USD This is a highly requested feature for ksp 2, being able to create customer kerbals, i think if the feature was free it would allow a certain amount of cosmetics but the paid would allow all cosmetics in ksp 2. Custom Director Kerbal, could be a pfp a kerbal that is "the director (which is you btw)" that would be able to interact more "kerbal friendly" compared to just the characters talking to the "screen", this could also be used as PfP for saves or in multiplayer settings you could use your custom director to be the pfp instead of either a custom photo or your steam pfp. This could be a little high, but i think the amount of work that is required to get it running and then making sure it works on multiplayer/ (if) there is more cosmetics it would allow "People to create kerbals of there own imagine" Custom Flag Implementation - 3-5$ USD Quite a few people request this to be a main in-game FEATURE, there is a mod that does this however the mod misbehaves a lot and does the stock flag instead of the custom one, They can be extremely high detailed flags I think they could make it a microtransaction that is cheap enough that almost anyone could buy it but it would not affect the users if they didn't have it, A Few CC's and a lot users could want such a thing in game. I think this shouldn't controlled in the sense of company censoring what photos are and are not allowed. In multiplayer it should be the owner of the server or local server that should be able to "remove" the offending flags and have an outright option to ban users from uploading and using Custom Flags.. Users can have as many as they want and can be limited on multiplayer if the owner so chooses. This will also include adding "parts" to add large flags that wrap around crafts in many sizes, or just straight huge flags that could be lit up by lights, and stock ksp 2 flags can use this for free. Hex Color Editor - 3-5$ USD Cheap easy mod that adds Hex color fine control to the game (Unethical) in my mind and should be free, however using Spicats Suggestion if all UI updates was approved i don't see why this couldn't be a paid feature its cheap at relative cost and would make users VERY happy, while also not breaking the bank, Supporter Pack #1 - 15-25$ USD This would include a "Music Bouns" of 1 additional song for each situation, planet, and ambient noise, The music is one of the key notes that i have found and have seen many others saying its "very good" for the game. This would include a "Banner Around PfP" or Color Change or A Speical Title.. saying that you purchased the supporter pack.. Would include a special flag(s). Be able to put custom crafts in the menu screen(s) We do not know if multiplayer would even have pfp or titles however, i think it would be a cool thing to add. yes this is pretty much try convince to keep intercept games with ALL of there developers with a job, is absolutely silly to think that we will sit down with people getting fired, and only getting corporate talk. These could be microtransactions that keep small amount of income coming to the game to show people might be interested besides the absolute devestion of trust when the game got forced to be released. (perhaps don't launch a game a year to early and then try to can the developers when we are getting remotely close to an actual game cause of your mistakes cause you are down a few million dollars..)
×
×
  • Create New...