Jeast

1.0.4 has pretty much messed up the aero of the latest release (1.6) guys. It seems that its nose down after reentry. Can anyone confirm this? I'll update it a.s.a.p.

Yes a joystick. Hmm is that it? When I save my settings with a controller and it cannot find it on a restart it messes up the config?

I still have all my settings reset on restart. It keeps showing the window where KSP asks you to share your data what it normally does on the first run only. It resets all my graphic and controller settings every single restart. Does anyone know the solution to this? Thanks, Jeast

Mike, dude.. Thats freaking awesome! :-D

Yes FAR compatability is the first step. When thats done we only have to rescale it to RO standards.

Yes please!!

Yes it all starts with making clear goals! You can do it man, this is going to be an awesome mod.

This is exactly what I was afraid for and why I tried getting it a little bit more organized. Mike has litteraly worked days and nights and being the type who likes to please everyone, a burnout is inevitable. First of all its not my mod, its Mikes. He can do whatever he pleases whenever he pleases. I love the shuttle and I am a professional structural engineering 3D modeling teacher at university so when I found Mike was getting a little bussy I could step in to help a bit with the aero and the IVA. I have created a shuttle from scratch for RSS last year (for private use) and had a bit experience with getting the shuttles aero done okay. My work done is only a little drop in the bucked compared to what Mike did and I know that probably my continues pushing to get the development more structured is part of the reason Mike is burnt out. Mike my guess is you will come back, you just love this thing too much I will leave the aero to you and let you handle it without me yelling and whining about organization here.

Why not use 1.6 for the time being. I'm having a lot of fun with it ;-) https://github.com/Jeast85/CSS-unofficial/releases

No I still fly and use 1.6.0.1 for the IVA modeling. Do you have a complete version with all Mikes latests adds Cheech? I have no clue what to merge with 1.6 tbh because a lot of files/updates have passed the revue lately and I care too much about the flying characteristics and like them in the 1.6 Doesnt mean I dont want to update btw. Just dont know the status of objects and tests Mike you want acces to the Github? Maybe I can even transfer it all to you if you want that?

Sounds good! How about this: you just go on doing how you are doing things now, and I organize things on Github paralel? I know essentially these are 2 different projects but I wil continually try to merge your updates. Maybe the best of both worlds. You dont have to pay any atention and just keep on doing things at the rate youre doing now, and I keep the people who desire a little bit more structure happy. Is that an idea?

Okay. You did not comment on the Github idea? What do you think about that? It will make it very easy to keep track of changes and versioning. It wil also make it a lot!! easier to work together with more devs on the same project. I have made an example page so you can see how it works. Let me know what you think of it. https://github.com/Jeast85/CSS-unofficial BTW we are not acting like its the end of the world, but why not get a bit more organized? You have given a reaction to what was said on organization. If you just say: I don't want it,than thats okay and Ill shut up about it.

It is a dev thread but that doesnt mean to not be organized. If you go gradually and make sure everything that is done already keeps on working, so version control is a must, saves you a lot of time and frustration and keeps everything clear. Dont forget we are working on this with multiple people at the same time. There must be some kind of organization to get things managed right. The way it is going now only works on projects where only one person is working on. For example If I post something and someone else posts something other 5 minutes later not including the change I made or rendering my change invalid, thats counter productive. Even when you look at this as early acces, compare it to Steam early acces. You can only download one version so only test one version so the input you give is clearly based on that one version and all the devs are clearly working on that same one version. I cannot understand how one can argue against this. Mike, let me setup a Github. Are you okay with that?

Mike, please let me do some organization on the mod. I feel like giving up on this but I would hate to do so. It has a lot of potential. Cant we go a bit slower and add stuff step by step while continually testing the FM? I think we all agree release 1.6 is the most stable and a good default/fallback version. Since 1.6 Mike added a lot of great stuff but these also changed a lot on the 1.6 aero model. I think you really have to add new stuff gradually and testing yourself after every single change you make if it still flies as it should. If you test it yourself there is little change that when you release something/ send out links for other testers, they are having a lot of problems and this tackles a lot of potential stress. In a nutshell. Use 1.6 as a basis and add stuff gradually from there. Keeping track of versions using my mini-AVC implement so that we know everyone is on the same version.

Aerodynamics are way off indeed... I don't know man. I have put in litteraly days to get them right for 1.6 and I thought they were spot on. I don't feel like putting in days again while this thing still is in developement just to see them get outdated in a week again.

Sure thing! Let me know when its rdy for it. I'll also include the mini avc version checker.

OK guys, this is where the SAS buttons shall be. (ps don't pay attention to the dashboard panel, not textured yet)

The bible. Explain capitalism

Lol. Say byebye to your smooth fps haha.

I think this should be optional.

Its a guess but I think so yes. - - - Updated - - - Here you can clearly see the docking alignment indicator. So I want to implement that at the exact location. The MFD on the left I want to use for the RPM docking cam.

I have the idea to create realistic MFD's for the new IVA. This means that it is not possible anymore to get the docking cam or alignment indicator on the cockpit MFD's. I want to place a kerbal with two MFD's (with docking cam) in front of the backwindows so you can only dock using this kerbal and looking trough the back/up windows. What do you guys think of this?

Its not about hitting T but the direction. Prograde, target etc.

Does anyone know how SAS was inplemented in the shuttle and where the buttons where? Was every orbital move done by autopilot? It seems to me after reading the manual there werent many controls in the cockpit for actually flying the thing out of the atmosphere. I ask this cause Im trying to find the right place for SAS direction buttons.