modbox555

Just google ksp rve and click on the girhub for 1.0.4, thats how I find it.

Sounds awesome! can't wait to check it out

Guess it is . Are you using any mods other than RO specific mods?

Aw man thats really weird. Well whatever it is, I'm sure that it will be gone after the 1.1 update. Maybe try stock and see if the issue is still there.

I hear you on that, I remember when I was first doing RO and I had to install again 3 times in a row since mods kept breaking eachother . Im sure CKAN will do the trick and it will also save you searching for updates to mods. Good luck!

I used CKAN for the entire RO install (including mods like DRE and FASA) but any additional mods no. Thats pretty strange though, have you tried on a clean RO install?

No Problem Do you mean the reentry heating effect? I've never had a problem with it so far, however I almost always use deadly reentry so that could be why its working the way it is. Did you change the quality slider for aerodynamic effects?

Sounds right to me, the config style is slightly different since the linux version uses the new version of eve

Well whats going on is that I'm using the textures from the Windows version (excluding city lights, I dont use those to save memory), then downloading the newest wip eve overhaul release(only the environmental visual enhancements folder), scatterer, then using all of the configs from the linux 64 version overwriting all files (besides the windows textures). Worked perfectly for me so far, hope this helps.

With the new update to RP-0, RVE now works perfectly as the name of Kerbin is irrelevant. Also since Kerbin isn't named Earth anymore, I managed to make a hybrid between the windows and linux version with scatterer included and it looks amazing

Well to start, which version of the mod are you using and did you follow the readme exactly? When you first launch a vessel with the mod installed, hit alt+e on the launchpad, pause the game and then hit the apply button. After you close out of that window (alt+e) again it should be fixed. I had the same issue with the windows version. Hope I helped .

I see, thats pretty annoying. I just tried using the new dlls and changed the names before i saw your message and i got the same result as my second update above with everything other than the atmo working. Somethings bound to work at some point .

Oh thats great to hear! So its really just down to Scatterer if all goes well then, I actually havent used scatterer in my career install with the windows version though . I thought that was only working for the Linux version.

Sure thing! I get to that now and see how it goes. Update: Well this is an odd one... On the first go, with the ccNameLater line active, Earth is renamed to Kerbin on the map and the contracts still showed up in mission control and become invalid once active. Once I disabled the line, the atmosphere stopped rendering, (scattering, clouds, and color entirely) leaving a black sky. Strangely enough, now Earth is back to being called Earth (probably the Kopernicus config, should I try changing that?) AND the terrain/ocean shaders are working as intended (I think? There is a large blue saturated circle coloring the ocean directly beneath the spacecraft but then gradually goes greyscale) It seems that the contract archive is intact, showing completed RP-0 contracts and I do not see any more error boxes. However I dont see any sign of NEW RP-0 contracts either . Another incompatibility could be how RP-0 relies on Earth biomes such as Earth Tropics while Kerbin Tropics do not exist. Im not quite sure, but once I get some more free time I'll try the Kopernicus config as well.

I understand, also its a good thing notepad++ allows you to replace content from all open files because I actually just did some testing and it seems that even with every "targetbody = Earth" changed in every config the same error messages come up. Looks like I'll have to be patient and see how things go. Thanks anyway though

For reference I have actually gotten both working, Linux (with the 64 bit workaround for Windows) and the Windows version. I see, so only with a new EVE and Scatterer build with name functionality fixes would this problem be completely fixable. Honestly I can probably just change Earth to Kerbin myself in all of the configs to get it working for now. If only i wasn't so picky about the name being Earth. Thats what I was thinking about, its not too bad with a quick replace all I guess.

Hey Pingopete, I've just gotta say that you are so awesome for making this. I got it working for my sandbox install with the 64 bit workaround, but the only thing stopping me from using this in my career save is the rp-0 incompatibility. I understand that you are already looking into the problem, but is there some form of workaround that I can use to change the contract data to keep them from being terminated? Something like changing Earth to Kerbin (or vice versa) in the config files? Sorry if this is a stupid question, but again thanks for everything you've done so far. Cant play RSS without it! Thanks.

Which version of the mod have you installed?

Having the same issue, I recently started a RP-0 career and cant see the mark1/mercury pod or the early command pods node. The thing is that even in the tree file, it says that both should be in the enhanced survivability node (which I can't see either). I would really appreciate some advice on steps to take to fix this. Thanks EDIT: Misread community resource pack as community tech tree, silly me

Im pretty sure that in this version of EVE the combo is Alt+E or if not, Control + E

No problem! Its the whole putting them in the same stage part that makes the fairing base disconnect before the fairing thirds can separate since they're disconnected before they get activated.

You probably already know that when you've placed on the fairing halves/thirds more than one new icon appears in the staging setup, (the halves/thirds look like radial decouplers). In order to separate the fairing halves/thirds rather than the base you need to locate those new icons in your staging setup. Stage those first before activating the fairing base's stage. For instance, the 3.75m fairing base has thirds so there should be a stack of 3 radial decoupler looking images in your staging setup that are at least in the stage before you activate the fairing base. Sorry if this sounds confusing, hope this helps.

Thanks, but unfortunately it didn't work, I still keep getting this message infinitely inside the debug log when I try to take out a radial parachute from one of the A/B containers. [Log]: [KAS] WaitAndGrab(Container) - Waiting rigidbody to initialize... Not sure what else to try. Also, thanks for all you've been doing to help me and everone else out.

I'm not sure if your problem is related to the same one I'm currently having, but after some testing it seems the only part that causes this bug for me is the radial parachute, I am not 100% sure about this but it seems to be an issue with Real Chutes since it modifies parachutes. Once I removed Real Chutes I was able to grab the chutes out of the containers, however Real Chutes is far too essential for me to play without . Guess I'll be packing parachutes in some cargo bays then, now to rescue that runaway science lab on a decaying orbit.

Same problem here, Dropbox is blocking it because of too much traffic.