hbkmog

New to this mod but just a stupid question here, what's the difference between this and EVE? I see that SVE includes EVE but what's added and different?

Oh yeah I can achieve that too. But when you do that for the 5th or 10th time, it gets tedious, especially when you try to set up a network on other planet with long signal delay.

Like I said, it is achievable. Limit thrust, RCS and capslock I can do that too. But it's tedious and time consuming. I can tweak that to perfection but with the same amount of time, I could do more other things, not to mention how much you have to do it when you set up multiple network. The table I provided is exactly the data from the synchronous orbit and yet you see 0.1 second error will collapse the network within just short 3 years. That's pretty low tolerance compared to real world. Moreover, I play career mode so high orbit isn't really possible in the beginning. With the starting Communotron 16, the highest orbit you can go without breaking the line of sight is around 840km. Even that is pushing the margin of error. I have done some extensive testing. Even with Hyperedit, with exact same orbit parameter, the orbit shifts by itself and the orbit periods desynchronize at an accelerated rate as time goes by. There's simply no way to lock the orbit or at least have it oscillate within certain margin. Even on the tutorial page, it clearly says this: It is nearly impossible to give two satellites exactly the same orbital period, because the period will change whenever the satellite rotates (for example, to keep facing the sun over the course of the year). For the last word in satellite synchronization, you may wish to edit your save file. Some RemoteTech players see this as essential to get around game engine limitations, others see it as cheating. You will have to decide for yourself.

I played it but now I'm thinking about stopping using it. It's fun if you play it the first time around. It feels great when you set up your first communication network. However it gets old and tedious when you do that the fifth time as you are basically repeating the same thing over and over. Another fatal flaw of this mod is that due to the game engine and scale of universe in this game, unlike real world, your satellites will drift within years and you have yo readjust them again. It becomes a chore when you have multiple network setup. Don't get me wrong. I like the mod but it's just not sustainable if you play for a long period of time.

You can see it with Kerbal Engineer or Mechjeb.

Well that's exactly my method as well. I launch 3~4 sats on one rocket and release them at apoapsis then change my orbit period to 4/3 to release the next one at apoapsis again. The thing is it's still tedious and time consuming to fine tune the orbit period of each satellite due to the game engine constraint, especially if you are doing this the 10th time. Seriously, in real life nobody jumps back and forth on different satellite fidgeting the orbit period. Here's the drift error data: [TABLE=class: data, width: 100%] [TR] [TH=align: center]Period Error[/TH] [TH=align: center]Drift Rate[/TH] [TH=align: center]Time to drift out of contact (38°)[/TH] [/TR] [/TABLE] 0.01 seconds 0.00067° per orbit10 Earth years (33 Kerbin years) 0.1 seconds 0.0067° per orbit360 Earth days (3 Kerbin years) 1 seconds 0.067° per orbit36 Earth days (140 Kerbin days) The problem is with the limitation of the game engine, you won't get the period error around 0.01 seconds stably. And even with 0.1 error, 3 kerbin years is simply too short because of the scale of the planet and universe in game. In real world, 1 second of period error isn't a big deal considering how big earth is but in the game, that simply won't work. - - - Updated - - - Let me tell you even with Hyperedit placing satellites in "perfect" orbit, it is still not accurate and the constellation deteriorate over time. You will see your orbit wobble a lot and orbit period flickering back and forth and all different on different satellite, even if you set exactly the same parameters for them. It's just the game engine that can't be that accurate.

Better way? Other than manually fine tune the orbit period? Yes it's totally possible to achieve rather stable network but it's just very grindy and unnecessarily time consuming. It's okay to do that with first 1 or 2 networks. But once you do the same thing for the 20th time, it becomes very tedious. Optimizing orbit is fun the first few times, after that, it becomes a chore and repetitive. To each their own though. Some people like grinding in MMOs and I absolutely hate it. - - - Updated - - - Yep, or better just use RCS, limit thrust, capslock fine tune. But even with that, it's quite tedious to switch back and forth the satellites to have the closest orbit period possible. I did that with the first several network I set up and then felt I was just repeating the chore with no real progression or new discover. It stopped being fun.

Yeah I feel the same about RemoteTech. I like the concept and have successfully set up some communication networks. It feels really great the first few times when you do that and watch the network nice and tidy. But the problem is the satellites drift away way too fast even if you have set up a very closely synced network. The game engine itselfs limits how fine tuned the orbit can be and it gets quite tedious and boring to have to manually correct it every few hundred days. I hope there could be a feature like ground satellite control that the system automatically synchronize and adjust the orbits of satellites, provided you have launched them properly within a reasonable margin of error(eg. 5 seconds). That would relieve a lot of tedium of maintaining the networks.

If you really want immersion or realism, you shouldn't do everything manual. Flight computer is pretty much essential in real life space mission. Just opinion.

The skin bug: when you open set menu to change the skin the KSP style, it changes as intended. However when you click set button to close the window, the skin returns to black transparent default one. Also I have noticed that it seems the electricity drain calculation doesn't support ScanSat? I tried with altemetry sensor and multispectral sensor but their power consumption wasn't reflected. Edit: Also it seems it doesn't calculate the omni antennas from remotetech. The dishes are fine but not antennas.

I don't know why but when I use MJ to execute maneuver node, it's always inaccurate, as in it doesn't execute the node at the correct burn time. Sometimes it burns too early and sometimes it burns too late. Anyone else with the same problem?

I really hope Squad can open up tech tree modding a bit more. With the current state, there are too many empty nodes or nodes with only one or two part. I chose USI LS instead of TAC so a bit portion of the tech tree is empty because of that. The early to mid game is good but further on the tech tree becomes a lot less exciting.

Regarding RemoteTech tech tree placement, I have a question. This is the RemoteTech parts: https://remotetechnologiesgroup.github.io/RemoteTech/guide/parts/ I noticed that I unlocked Reflectron KR-7 before Comms DTS-M1, which seems a bit odd because Reflectron KR-7 is an upgraded version of the latter. Is that intended?

That's great idea. I think what's gonna be most helpful is a tech tree map indicating what mods are where in the nodes. I know right now there's one out there but that doesn't seem complete, especially that near future technology and interstellar extended seem a bit confusing.

One small request regarding the UI. Is it possible to use yellow font on the background? I think it's a bit hard to read the red on dark background. Also will you fix the KSP skin bug?

Can confirm that this workaround works other than the KSC facilities upgrade/downgrade bug. But that's very minor compared to the huge benefit of stability. My RAM usage is well over 4GB and no crash yet. It gets a bit unresponsive in VAB but that may be due to the overall high RAM usage with other programs as I only have 8GB RAM in total in my rig.

I think he has answered before that the empty nodes are a "feature" in 1.0 game. There's nothing can be done about it.

One suggestion. Since now Station Science mod has been updated to 1.0 compatible, is it possible to integrate that into SETI? It adds more space station science stuff to do.

Hi Magico, another question here. I built a rover and tested it at the base. Then I returned to space center and recovered it. As usual I got the parts refund and everything. However, I'm thinking with this mod, is it possible to "store" the undamaged vehicle or spacecraft in the hangar? Like if I use plane or rover, I still have them after the mission is over so I don't need to build them every single time. Is that already in the KCT or did I miss anything?

Yeah I tried to do different science tests at different biomes but it gets kind of tedious. :/ Also the science return isn't all that great compared to vanilla game. - - - Updated - - - Thanks for the reply yeah I do have a working airplane even though I always try not to put a rocket booster on it because it just feels unrealistic and ugly. So I guess I really have to do that different biomes science experiments to get science then. I just did a rover run on KSC and got some science from all facilities from KSC.

Most of the contracts I have are part testing and tourists(not possible before manned flight) and high altitude visual survey. Other contracts are remotetech and Scansat which are also not possible at the moment.

I have been playing with SETI for some time and here's one suggestion I'd like to make, In early games, earning science feels quite grindy mostly due to the contract. The tech tree allows early airplane and rover but there are basically no contract with them. Most of the visual survey contracts are high altitude(also one of my complains about the stock contract) which is not possible with the early airplane. Then rover serves no purpose as there are no contract related to them. Because you cannot do manned mission in the beginning, the fastest way to accumulate science only lies in tests which is a chore and grindy. Especially when paired with RemoteTech mod, it's almost impossible to set up a Kerbin comsat network without manned mission, which greatly limits the usage of probes due to lack of linkage to KSC. So in the early game, it's kind of like a catch 22 with RemoteTech or SCANsat. You need manned mission to set up the comsat network, then SCANSat. But the fastest and most interesting way to gain science to do unmanned orbital, suborbital probe missions which is not possible without comsat network.

Even with aggressive ATM, I still have over 3gb memory use with mods at initial load up. Over the time it goes to 4gb. I have to use the 64bit work around to play it in that state. If you want a stable game, forget about most extra part or visual mods.

Yeah the 32bit RAM limit really reminds of Fallout3, New Vegas. They also had extremely limited RAM usage in vanilla game. 4GB RAM limit is actually not bad. The thing that really kills it is everything, whether needed or not, is loaded into RAM, which is absurd in modern day technology. Unity 5 port really can't come out soon enough. - - - Updated - - - Yeah it seems they have gone radio silence since the 1.0.2 came out, even though they went on vacation.

Found a bug. I uninstalled all my mods and tried to reinstall all of them again from the backed up .ckan file. It asked me to choose one of the Distant Object Enhancement preset. I chose default and continued. Then I got the error message saying there's already a config for Astronomer's pack despite that I didn't choose that. I even deleted all the mods from GameData folder but still got the same message. Please see the error message below: ----------------------------------------------------------------------------------------------------------- First this from installing mod tab: About to remove: Done! The following inconsistencies were found: DistantObject-default v1.5.5 conflicts with AstronomersPack-DistantObjectEnhancement Interstellar.V2, can't install both. Error! -------------------------------------------------------------------------------------------------- Then the pop up error message: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.ArgumentException: Mod installed-default is not in the list at CKAN.RelationshipResolver.ReasonStringFor(Module mod) at CKAN.RelationshipResolver.ReasonStringFor(Module mod) at CKAN.RelationshipResolver.get_ConflictList() at CKAN.MainModList.ComputeConflictsFromModList(Registry registry, IEnumerable`1 changeSet, KSPVersion ksp_version) at CKAN.Main.UpdateChangeSetAndConflicts(Registry registry) at CKAN.Main.ModList_CellValueChanged(Object sender, DataGridViewCellEventArgs e) at System.Windows.Forms.DataGridViewCell.SetValue(Int32 rowIndex, Object value) at CKAN.Main._MarkModForInstall(String identifier, Boolean uninstall) at CKAN.Util.Invoke[T](T obj, Action action) at CKAN.Main.PostInstallMods(Object sender, RunWorkerCompletedEventArgs e) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll ---------------------------------------- ckan Assembly Version: 0.0.0.0 Win32 Version: 0.0.0.0 CodeBase: file:///C:/Users/Jingquan%20Guo/Desktop/CKAN.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34250 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34239 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- Microsoft.GeneratedCode Assembly Version: 1.0.0.0 Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- Microsoft.CSharp Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.33440 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.CSharp/v4.0_4.0.0.0__b03f5f7f11d50a3a/Microsoft.CSharp.dll ---------------------------------------- System.Numerics Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll ---------------------------------------- System.Dynamic Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.33440 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Dynamic/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Dynamic.dll ---------------------------------------- Anonymously Hosted DynamicMethods Assembly Assembly Version: 0.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/mscorlib/v4.0_4.0.0.0__b77a5c561934e089/mscorlib.dll ---------------------------------------- System.Transactions Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll ---------------------------------------- System.ComponentModel.DataAnnotations Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.33440 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ComponentModel.DataAnnotations/v4.0_4.0.0.0__31bf3856ad364e35/System.ComponentModel.DataAnnotations.dll ---------------------------------------- System.Runtime.Serialization Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll ---------------------------------------- System.Xml.Linq Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll ---------------------------------------- System.Data Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- System.EnterpriseServices Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.