Jump to content

Andrewwang66

Members
  • Content Count

    41
  • Joined

  • Last visited

Community Reputation

4 Neutral

About Andrewwang66

  • Rank
    Shipbuilder
  1. Hey, great work so far on updating this stuff! I really am thankful that you're taking the time to do this, I don't know what I would do without B9-PWings! At least 90% of the stuff I build uses B9-PWings and about 20% of the stuff I build is almost entirely made of B9-PWings. By the way, if its not too much to ask, is it possible to make the limits for the PWings a config file? I don't know how the stuff is coded since I haven't taken a peek at it, but would it be at all possible to have a configuration file which says maximum width, maximum length, maximum thickness, and maximum offset? Some
  2. Alright, finally fixed it, LOL that was horrible... remind me to back up my game before I update, oh wait, you did and I just didn't listen...
  3. Yeah, I've done it a couple times before, I'm currently trying to completely reinstall.
  4. It wasn't a save issue it was loading the saves in or creating a new save, neither would work on the new version so I attempted to return to 1.0.0, I guess my issues with the 1.0.0 version was probably to do with the fact that all these new files were installed. By the way, where would the patches be? I'm checking the .cfg files for the mods installed and I don't see any patches for them. I am reinstalling everything to make sure I isolate the issue to it being that. I probably should have backed up my GameData file but oh well, such is modding.
  5. Ok, uninstalled, I know this probably isn't relevant to this mod but I have issues with the loading of any save after installing and 1.1.0 and then attempting to fix the issue by downgrading to 1.0.0. Log file is here if you could help: https://drive.google.com/open?id=1VP3kLeX9_0UZrSYpZM1y021vOFWahuyL
  6. Alright, I'll uninstall Boomsticks but I still am encountering issues with loading saves. It's probably not an issue with BDAc so I'm currently working on reinstalling everything to make sure.
  7. Well, I uninstalled BDAc 1.1.0 and went back to BDAc 1.0.0 but it seems like there are still issues with save loading, I used a fresh copy of KSP 1.3.1 and placed all my GameData files there and it seems like it is clearly something in my GameData. My game worked perfectly with BoomsticksRev 3 though, it still functioned even though it is outdated, though maybe that was just SM Armory. Edit: Scratch that, definitely BoomsticksRev 3 still working on 1.0.0, I edited a file from there to create a tail gun for my aircraft and that worked as far as I know.
  8. Alright, I downgraded back to BDArmory 1.0.0 but I'm still getting the freeze and then unresponsive program issue when I attempt to either load or create a new game. At this point I'm fairly certain its not BDArmory's problem anymore and it's something with my game but if anybody knows what the issue is, please help. Also, note I'm playing with MM 3.0.0 if that makes a difference. The game was working perfectly prior to this, I might need to do a complete reinstall of the game. Log file is here: https://drive.google.com/file/d/1hyY28MKbl1fQtTVYryC4_RFh3KDGEdBw/view?usp=sharing
  9. Aaaaaand I'm getting a game freeze on load of a save or on the creation of a new save with this new one, probably because of incompatibility somewhere. The log file is here: is what I would like to say but right now it's getting late and I need to get some sleep and my internet is being terrible so I'll be uploading that tomorrow, full mod list is as follows: I'm currently running with: WW2 Warships (Outdated but still works for KSP 1.3.1, no parts used from that so I doubt that's the issue), Air Park, Airplane Plus with the Tweakscale patch and the Raster Prop Monitor patch, Atmosphere Autopi
  10. It seems it does work, not sure what that error message was about cargo bay, that craft does not seem to have one... So here is the thing, we are in beta mode right now and so much has been updated it will be hard to track this down, we have a lot of fixes and changes in our dev branch now. I know it works with the latest build, so if you are willing you can try it here: https://github.com/PapaJoesSoup/BDArmory/releases/tag/v1.1.0 Of course this is experimental and if you are squeamish, then I suggest you wait a bit until we do the final release.
  11. Ok just removed the fairing and now it fires... I guess that's an issue. Can we get a fix? Like it seems just because there's a fairing on the jet it refuses to fire.
  12. Craft file is uploaded in KerbalX in the original post, link is here: https://kerbalx.com/Andrewwang66/SMF-15-Production-SAS-FJS Full log file here by the way: https://drive.google.com/file/d/1HCG2qWmAs1L4shRdpzkYkt2cAFmggByY/view?usp=sharing
  13. Ok internet is really slow, I'll throw in the log from when the fight starts: [LOG 21:26:38.328] [AtmosphereAutopilot]: vessel switch to SMF-15 Production (SAS) (FJS) [LOG 21:26:38.329] FF: EventObserver:: OnVesselChange SMF-15 Production (SAS) (FJS) [LOG 21:26:38.330] Trajectories: Initializing cache [LOG 21:26:38.331] 12/18/2017 9:26:38 PM,KerbalAlarmClock,Active Vessel changed - resetting inqueue flag [LOG 21:26:38.346] 12/18/2017 9:26:38 PM,KerbalAlarmClock,Removing DrawGUI from PostRender Queue [LOG 21:26:38.349] [Dynamic Battery Storage]: Summary: vessel Mark2Cockpit (
  14. Erm, wait what log? I thought you meant the BD Armory Debug labels... please explain. Edit: I got what log you meant now, KSP.log, I'll upload it now Edit: Internet being really annoying, the gist of what is happening is: [LOG 21:07:30.481] [BDArmory] : SMF-15 Production (SAS) (FJS) - Selected weapon AIM-120 [LOG 21:07:30.482] [BDArmory]: SMF-15 Production (SAS) (FJS) is engaging an airborne target with bahaAim120 (BDArmory.Parts.MissileLauncher) [LOG 21:07:30.482] [BDArmory]:SMF-15 Production (SAS) (FJS) launchAuth=True, pilotAut=True, missilesAway/Max=0/1 [LOG 21:07:30.4
  15. Video is uploading, the internet is pretty slow but I'll post as soon as I can, was switching between the two crafts to provide debug info on both and also turned off and turned on guard mode mid-flight after failure to fire any ordnance to demonstrate how no matter what it refuses to fire.
×
×
  • Create New...