xv323

Understood of course! In case it might be of use when you do come to it in the fullness of time - from examining the behaviour of this issue in a bit more detail, it seems that a) switching away from the vessel and then back to it reorients the IVAs to the correct place, and b) moving any kerbals between different parts within the vessel also reorients the IVAs to the correct place.

This mod is absolutely tremendous - a godsend for a particular ship I've been trying to build. Infernal Robotics has always had a glaring gap in it for proper rotational parts, and this is superb stuff. I was just wondering - there's an issue I'm experiencing, which I've seen mentioned a couple of times earlier in this thread but I don't know if a solution was ever explored. MaianTrey's explanation below of the issue matches pretty much exactly with what I'm experiencing: I was just wondering if anyone has any ideas for how to overcome this, or whether this is something that you might be able to look at sorting for the next update? In any case, a fantastic mod and thanks so much for all your work on it!

@alexustas @MOARdV any news on a fix for this issue?

Don't know what was up, but the problem's resolved itself now - I can get at the spreadsheet fine. Regardless, thanks for taking a look!

Thanks. If you need anything further from me at any point as you look into this, ping me a message and I'll do my best.

Hi @Nils277 Wanted to report something. Don't know if this is something only I'm getting, but any attempt to open the TAC-LS spreadsheet linked to in the OP is throwing me an error message. Specifically, it's a Google Drive error message that reads as follows: I'm getting this both on Google Chrome and Safari. My own Google Drive is working fine and I can get at my own uploaded files and stuff, no problem. I've been having this issue all day, so the 'coming back to it in a few minutes' option is pretty much exhausted. I know it's not a big issue in the grand scheme of things but could you take a look? Finally, thanks for your sterling work on this amazing mod!

@MOARdV Here's the log file as you requested. https://www.dropbox.com/s/lu5po1ye6gsc2u4/KSP_4.log?dl=0 Ancillary information - this is on 1.2.2, and the only mods installed are as follows: ModuleManager 2.7.5 ALCOR Pod 0.9.6 ALCOR Advanced IVA 0.9.6 ASET Props 1.4 RPM 0.28.0 Steps taken: I went into the VAB, selected the ALCOR pod, added no further parts, and hit launch. The crash occurred as before, in the loading screen before even getting to the launchpad.

Gotcha - will do. Which log file will the output from this go to - is it KSP.log or some other file?

Totally understand - and again, thanks for all the work you do to put these mods together. I'm sure I can live with this issue without too much of a struggle! I see @WildLynx has made a Git issue already, so I won't duplicate it.

Hi @Nertea Firstly, wanted to say a massive thank you for all the work you do on these mods. I use them extensively and they're just amazing! I wanted to report an issue I'm having with Near Future Spacecraft. Specifically, this is an issue with the IVA of the Mk3-9 pod. These screenshots show what's going on: As you can see, there's some issue with the 'upright' between the two windows. They look somewhat mangled and have transparency in places that don't look right. I'm on KSP 1.2.2, Mac OSX 10.9 'Mavericks', and I'm using the latest version of Near Future Spacecraft. The only mods I have installed are Near Future Spacecraft, B9 Part Switch (as it comes bundled with NFSpacecraft), and ModuleManager 2.7.5. Here's the log file, in case it's of use: https://www.dropbox.com/s/2wq2zkihfsjszxq/KSP_3.log?dl=0

Update to my previous post: This problem is still occurring in a 1.2.2 install in which the only mods installed are the ALCOR pod, ALCOR Advanced IVA and dependencies (ASET Props, RPM, ModuleManager). This time, I attempted to launch a craft which was just the ALCOR pod on its own and I had the same sort of crash as I was getting in my other 1.2.2 install. Here's the log file: https://www.dropbox.com/s/2493ciinx3t4ln7/KSP_2.log?dl=0

Hi Alex Firstly, thanks for all the work you've put into this mod - it's one of my favourites! However, I'm consistently getting crashes in my game with the new version. What happens, specifically, is that any attempt to load a craft that uses the ASET props causes a hard crash straight out of the game from the loading screen. This happens both when hitting 'launch' on a craft from the VAB and also when attempting to load an existing craft from the tracking station. The reason I think this is a problem with the props is that taking the newest version of ASET_Props out of the ASET folder in my GameData directory, and replacing it with the previous version, fixes these crashes. I'm on KSP version 1.2.2, and Mac OSX 10.9 'Mavericks'. The install I first identified this on has a lot of mods, but it's only switching between the old and new versions of ASET_Props that causes this. I'm about to put together an install of 1.2.2 with just the new versions of the ASET Props pack and the ALCOR pod installed, in order to double check that that's where the issue is - I'll report back what happens. Here's the log file for the most recent crash I had. In this case I was attempting to launch a craft consisting just of the Mk1-2 pod with the improved IVA pack from the VAB. I've also been getting this phenomenon occurring with the OPT Spaceplanes cockpits that use these props. https://www.dropbox.com/s/ziwfccnqkobag9h/KSP.log?dl=0

Forgive me if this is a stupid question - people have been talking both in this thread and the thread for the ASET Avionics pack about some dropbox links containing the most-recently-released versions of these mods. I'd be keen to get my hands on those, but the only dropbox links that I can find posted in either thread lead me to a 'not found' page. Has the mod now been taken down from these links? Any help much appreciated.

I may be able to help with this despite not being associated with the mod's upkeep. In the download, there are two folders - an 'extras' folder and a 'GameData' folder. All of what's in the GameData folder has to go into the folder called 'GameData' in your KSP folder. The 'extras' folder contains just that - extras which are optional. The 'installation instructions' .txt file that I spoke about earlier, that comes with the download, explains this all step-by-step. Hope that helps!

Hi there. Firstly, major thanks to everyone involved for maintaining this mod and updating it. Coming back to the game, I'm very glad indeed that it's being kept current, it's one of my favourite mods. Just wanted to highlight a very minor issue I spotted - in the installation instructions .txt folder that comes with the download of the mod, there's a passage that I believe has an error in it that makes things slightly confusing. It concerns the installation of the graduated power response config. The passage reads as follows; (My emphasis) I'm wondering whether this ought to read 'graduated power response' instead? The same words as here also show up in the section below this one on how to install the instant power response config: Having gone back in the thread a bit I wasn't able to spot anyone else who'd mentioned this. My apologies if I am in fact repeating a known issue.

That's good news! Thanks for your reply, I'll keep an eye out. Can't use 1.1 at the mo as I bought KSP direct from Squad's own store instead of via steam, but I'll try it out when I can.

@rbray89 I know you must be busy with the 1.1 stuff but could I pester you to take a look at the issue I've been having? I posted about it on the previous page including an imgur album and a log file.

Hey man - thanks for the tip! This worked out for me and definitely counts as a great workaround. Fingers crossed for 1.1, although I didn't get the game via steam so I can't yet try out the beta. I found out about the 64-bit workaround a while back as well, so far haven't used it for my 1.0.5 install as I've been keeping that as a non-modded install for now. My heavily-modded install is still 1.0.4 and I used the 64-bit hack for that. Saved my life in terms of all the mods I wanted to stick on there! For anyone else reading, would still very much appreciate it if anyone can tell me what the the origin is of the original bug both me and @gozzle are getting, and if there's a fix for it.

Hi all. Having an issue with EVE, unfortunately. I've had a read back through the recent pages on this thread, and I'm seeing a number of issues that people have had that sort of look like what I'm getting, but nothing that exactly replicates the issue I'm having, and I can't get a clear handle on what the fix might be. In essence, the problem is that the clouds on Kerbin and Laythe appear to only be showing up over one small sliver or segment of the planet - think along the lines of an orange segment. This is occurring in the tracking station view as well as in both the map view and ship view during a flight. It's one particular section of the planet, and it rotates around with the planet's rotation. In tracking-station view and map-view, different zoom levels produce a flickering, possibly Z-fighting (?) effect and past a certain zoom level the clouds disappear. Duna and Eve both look absolutely fine and as they ought to with this mod installed. I've included an imgur album link below that shows what's going on. Imgur album: http://imgur.com/a/oY9w6 My KSP install is an otherwise-unmodded 1.0.5 install. I am on a Mac running OSX 10.9 'Mavericks'. I've tried the 1-05-4, 1-05-3 and 1-05-2 versions of EVE, downloaded from the GitHub releases page for EVE, and this same issue occurs identically in all of them. I've checked the install steps I'm taking, and I'm correctly placing the 'BoulderCo' and 'EnvironmentalVisualEnhancements' folders in the 'GameData' directory. Log file link: https://www.dropbox.com/s/ziwfccnqkobag9h/KSP.log?dl=0 Anyone who can shed some light on this would be an absolute hero to me. This is my first time attempting to include EVE, and I'd love to get it working properly. EDIT: Sorry, uploaded the wrong log file when I first posted this. The log file I originally posted was from an old 1.0.4 install. I have now updated it to the correct log file.

Just came across this and read through the thread. The large rocket parts look brilliant but personally I'm getting grabby hands for that pod, it looks properly awesome! I'm a massive fan of the Taurus HCV pod because a) it's huge and b) it's got lovely big windows and a great IVA - and from what I can tell your Fortuna pod very much fits that mold, except it's a 3.75m-2.5m pod instead of a 3.75m-1.25m pod like the Taurus is. Would be absolutely perfect to fill a niche for me! If I may ask, is it planned that the first release of the pod itself will include an IVA or will that come in a subsequent update? This mod as a whole looks fantastic, can't wait to see more and to get said grabby hands of mine on it! :D

Hi all. I've not been able to find any reference to this, I'm not sure if it's a bug or a feature - I'm attempting to pick up a rover with a crane using the electromagnet. Before I attach the magnet the rover functions perfectly well. However after I've attached the magnet and then detached it again once, the rover has frozen, as if the magnet's fried the probe core, and I can no longer move in any direction Is this something that's included in the mod on purpose? Edit: So, I was a massive idiot. It was just a case of me leaving the brake on. Face, meet palm. Carry on.

Thanks for your reply. In my particular case, I need the heat shield as a separate part from the command module, as I am using the command module as the top of a larger spacecraft which I'm constructing. Long story so I won't elaborate, but as far as those nodes go, it's a bit of a pain. I will keep fiddling around though! Again thanks for helping

Hi all. Unfortunately, I'm having a very specific problem with Realism Overhaul. This is my first time attempting to use this mod. I started to go through the process of getting log files etc, but I decided to do some troubleshooting myself first, and I'm pretty sure I found the source - but I'm slightly confused as to why the problem's there at all. Log files won't help, I don't think, as the problem is in the .cfg file for a particular part. Any info as to how to fix it would be very much appreciated. I'm on a Mac running OSX 10.9 (Mavericks). The problem I'm having is associated with the FASA Apollo Command Module and associated parts - the Apollo heat shield, particularly. As you all no doubt are aware, the Apollo CM part from FASA doesn't normally include the heat shield, which instead is is a separate part attached to the CM's lower attachment node. When Realism Overhaul is installed into my game, I get the following thing happening (imgur links): http://i.imgur.com/19gk2oO.png http://i.imgur.com/GrunMFE.png Importantly - the heat shield that you see misaligned there is not a separate part that I've added. That's what the CM part now looks like - when RO is installed the CM part has somehow had the heat shield added to it. As you can see, it's also not placed correctly. Firstly, I've double-checked that I have up-to-date versions of all the dependencies required for Realism Overhaul and furthermore that I have the latest version of Realism Overhaul itself. Having initially encountered this issue I re-downloaded RO to check that the latest version did indeed have this issue and it did. I was installing RO into KSP along with FAR and RSS and I checked all the dependencies for those as well. Furthermore, I tested adding each individual mod into the game in turn and found that the effect only occurred when RO was present. I have also ensured that I correctly followed all the installation steps for all relevant mods. This all led me to look into the FASA cfg files included in RO. I found that in the 'RO_FASA_ApolloCSM.cfg' file, within the '@PART[FASAApollo_CM]:FOR[RealismOverhaul]' part entry, there was the following section: MODEL { model=FASA/Apollo/ApolloCSM/FASAApollo_Heatshield scale = 1.0, 1.0, 1.0 position = 0, -1.371, 0 // 0, -1.271, 0 rotation = 0, 0, 0 } Removing this section from the config file got rid of the heat shield from the CSM model and that particular part subsequently seemed to be behaving normally. Again - this is present in the latest-version download, I have double-checked that it isn't anything I've personally done that's somehow screwed this up. In any case - having deleted this particular bit of the cfg file, the heat shield part itself is now having other issues. I now can't attach it correctly to the base of the command module - what instead happens is shown here: http://imgur.com/rxqMzPh Even with part-clipping enabled I can't get the heat shield to move up into its proper position - there isn't a node there to accept it, it seems. I've looked at the entry in the config file for the heat shield part and I can't seem to fix this latest problem. Fiddling around with the node positions doesn't seem to help. I'd really appreciate any help that anyone can give here - I'm slightly nonplussed as to why the entry in the cfg file for the command module part even includes the heat shield at all. Are there an earlier set of config files I could use? If not, what exactly is going on here - is this something that only I am having a problem with? Searching within this thread did not turn up anyone mentioning the same issue as far as I can tell. Thanks in advance.

Thanks for the response. I'm aware the 64-bit hack is not supported, but to be frank, it works, it helps with memory issues, and it's quite clearly not the problem here, so I'm going to be persisting with it. As it happens, I believe I've managed to find the source of the issues I've been having. Through testing each FASA part in turn I was able to work out it's only a very few parts causing issues - the Gemini and Apollo command modules are two such parts. It then turned out that deleting the 'plugins' folder from within the FASA folder in the GameData directory solved the issue. I can only presume there was some issue with the reflections. Regardless, thanks for trying to help, much appreciated

Apologies, should have thought to include that. Here is the log file.