tigerduck98 tigerduck98
Duck
关注数: 0 粉丝数: 678 发帖数: 25,365 关注贴吧数: 2
【2015-02-06】【官网野生翻译】64位KSP的未来(被吃了) 大家好: 你们都知道KSP有Windows64位版。我们在一些以前的版本中就加入了64位版(特别是0.25和0.90),但是很明显这个版本相对其他所有版本而言太不稳定。这个不稳定意味着64位版相对于一个值得发行的版本而言有些太遥远,【所 以 我 们 将 不 在 KSP 1.0 中 加 入 这 个 版 本】。 (剩下的翻译没有价值了) 大概就是为了大部分玩家的利益暂时牺牲Win64版 另外Squad说在找到一个稳定的64位Unity版本后才会加入Win64 Linux64位计划将在KSP1.0中加入 (如果以后modder不加入win64检测的话我就魔改KSP的引擎为对应版本的64位了) 原文如下: http://tieba.baidu.com/mo/q/checkurl?url=http%3A%2F%2Fforum.kerbalspaceprogram.com%2Fcontent%2F328-The-future-of-Windows-64-bit-builds-for-KSP&urlrefer=7f020f250fb2735469b5c098190e6681 The future of Windows 64-bit builds for KSP Hi all, As many of you will most definitely know, Kerbal Space Program has a Windows 64-bit version available to players. We’ve offered this version for a number of past releases of KSP and as of late (0.25 and 0.90, in particular), it has become very apparent that this version has been consistently less stable than all others. This level of instability means that the Windows 64-bit build falls far short of what we would consider a release-worthy product, and we will therefore not be releasing it for version 1.0 of Kerbal Space Program*. We’ve spent a considerable amount of time investigating the reasons for these issues. The QA & Experimental Testing Teams have assisted in this research as have the community - something that we are very grateful for. However, despite these efforts and although we have identified a number of probable causes for the instability, there is a very hard limit on what can be done on our end. Most platform-specific issues stem from parts of the engine we have no direct access to, and we simply can’t debug these problems in the same way we’d do with normal KSP bugs. We often can’t even reproduce them in our development environment, so we’re limited to guessing at both the causes and solutions. In short, there are no easy fixes we can do here, and we feel that the time we would be potentially wasting on attempting to increase the stability of the Windows 64-bit version of KSP would be far better spent on other improvements which would reach as many players as possible. We can all agree there is no shortage of other things we could be working on. We’re not giving up on the 64-bit build for Windows, though. The most we can do at the moment, however, is continue testing the Windows 64-bit build at each new version of Unity, and release it if viable. Additionally, we must take this opportunity to stress that Unity 5 - while a definite leap in the capabilities, performance and development power of the engine - is not going to inherently be a ‘cure all’ for issues, particularly in the matter of the instability of the Windows 64-bit build. We’re aware that some of you have come to embrace the Windows 64 bit version by this point and that our decision to discontinue development for this particular build may be an inconvenience to some, but we trust everyone will understand the necessity that prompted this decision. At any rate, we want to thank everyone for their efforts in assisting in all bug finding and bug fixing efforts for KSP, as well as the modding community for their efforts in dealing with a rather unstable platform. We hope you’re all looking forward to 1.0! We’ll be sharing more news with you as development continues. *Note that this doesn't affect those that run KSP on 64-bit versions of Windows, only those that run the 64-bit Windows version of KSP. Additionally, the 64-bit build for Linux is still planned to be released for 1.0.
【SAS-free杯】Kerbin超低空挑战赛(误) SAS虽然在火箭与飞船的航行中起到了很重要的作用 但是自从一块叫做FAR的大气笼罩在KSC的上空 小绿人们发现SAS对于大气内飞行造成了很大的影响 特别是偏航轴,因为ASAS的程序是针对火箭编写的 为此小绿人研发了一种叫做【摇杆】的辅助工具 并且他们派出了Jebediah Kerman,C7 Aerospace首席试飞员 进行一次超低空飞行测试,来证明这款新产品的优异性能 下面是Jeb在测试中的影像: 最新型研发的XF-86测试机开始滑跑 值得一提的是,自从FAR笼罩之后工程师发现TWR<1一样可以自由飞行 所以XF-86的推重比被设置为0.43,并且配置了3档襟翼,可在95kts起飞 【并且关闭了动量轮和SAS】起飞后例行作死,Jeb:我还能再飞低些!下面则是紧张的环节 Jeb:我要感受大海的气息! (100m平飞,图中可以见到Jeb忘记收起襟翼了)Jeb:我还在下降…… (30m,Jeb此时已经收起襟翼准备好最低纪录的刷新)Jeb:我已经能看到水花了! (10m平飞,坎星新纪录诞生!)Jeb:乌拉~~~~~~~~~~ (5m平飞,KSC惊呆了!)接下来就返回机场了机组合影————————分割线———————— 使用KSP版本:0.24.2 载具使用MOD:旧版B9(进气道),自定义机翼(机翼),自定义组件(油箱),FireSpitter(减速板),Texture Replacer(Jeb的头及其宇航服),TweakScale(起落架),TVPP(发动机曲线修正) 使用摇杆:T16000M 欢迎大家放出FAR下超低空飞行截图【超过了十个表情,手动斜眼笑】
【教程】【降分辨率大法】亲儿子续航党的胜利! 起因:http://tieba.baidu.com/p/3174045399 某个吧友提到了降分辨率大法的超级终端命令 于是我也一试……然后手机显示区域就跪了 最后重刷之后鼓起勇气仔细研究终于成功 先上图证明效果 手机:Google Nexus 5——流畅小王子跑分大弱哔平常2h30m只剩30%了证明我的分辨率####本人对使用此教程的导致的意外不负任何责任#### ####基佬们后果自负,请自行备份系统和文件#### ##前期准备: 1.一部已root,装了busybox和超级终端的手机 (建议)2.有第三方rec的备份整个系统,取消锁屏密码,开启ADB 3.确认你要修改的分辨率和DPI #示例# N5——4.95寸 1080p DPI480(build.prop的设定,不是实际DPI) 改为720p DPI320 4.如果有可能可以考虑OTG连接键盘,因为某些错误情况会导致输入法键盘无法显示 (比如只能显示1/4个键盘etc.) ##正式开始:(首先我把分辨率调回了1080p) #以N5由1080p改720p为例# 本人所用软件系统(不要问我为什么不是L,自行查Gravity Box)1.修改build.prop,把其中的lcd_density=480改为320,保存并做好原文件备份2.打开超级终端,勾选su选项,输入wm density 320(你需要的DPI),回车 #注意#为了生命健康请务必先改DPI,这样出错了还有改回来的希望 (图片是执行完的效果,所有字都缩小了一些)3.输入你需要的分辨率 wm size 720x1280 #注意1#为了生命健康请务必改完DPI再改分辨率,否则只有OTG键盘大法能救你 #注意2#务必是“小x大”的分辨率,否则后果自负 #注意3#乘号实际上是英文小写“x”,数字和乘号间不带空格,格式错了程序不会鸟你 (执行完之后,各个按键的比例恢复“异常”不怕我们还有下一步)4.重启手机5.如果没问题应该就成功了(比例正确) #可能切换回原分辨率后会出现systemui.apk崩溃的情况,暂时无解 #这也是为什么前面的壁纸是默认的因为一换壁纸就崩溃6.如果要换回来请把所有步骤反向操作,最好选择重刷##########全文完########## 对了我相信会有不少人先带小尾巴回复我“去试试” 然后半小时后不带小尾巴来骂我的
首页 1 2 3 下一页