Ven

Members
  • Content Count

    237
  • Joined

  • Last visited

Community Reputation

635 Excellent

About Ven

  • Rank
    Spacecraft Engineer

Recent Profile Visitors

4,957 profile views
  1. You can't find it because I never defined them, the new engines refer to certain Stock engines for data, then change them slightly to make a new part. Squad probably added a spare transform for the visual effects that doesn't exist in the my models. That transform would need to be added or the parts need to have their Effects node specified to use the thrustTransform instead. As for the Shiba, I couldn't get the smoke to work inside the EFFECT node, so I left the sleeping dog lie.
  2. RadialLFOlong is a radial mounted LFO tank akin to the stock 'Stratus-V Cylindrified Monopropellant Tank.' The VenLV909b, is actually the LV-900. I have no idea as to why the docking ports would be so inconsistent. If they were configured incorrectly on my end, then they would never dock, or would dock in the wrong place/direction. Even if the game changed its way of handling docking ports over the past year, I keep going back to the reasoning above. *shrugs.* I don't believe pointing you towards manually downloading the github repo would help, as the docking port has remained unchanged. Check to see if others have the same issue in the stock game? Validate your game's install? Reinstall the game? Do you have any other mods? The arrows are just cosmetic... They mean nothing. XD
  3. To be blunt, it's also impolite to accuse someone of wrongdoing without evidence. Anyways, my permission is irrelevant, the license I picked allows Toric5 to do as he wishes as long as he gives attribution. And yes, he did contact me about this and I told him the same thing. Otherwise, I'm not really sure why he didn't just fork and then submit a pull request on GitHub for some changes, I'm still watching it and will merge the pull requests that make sense. Be aware that I've just pushed my updates to the repository, a whole lot of background config cleanup and added a few tidbits that were previously unused.
  4. VSR replaces most of the assets used by WindowShine, making the majority of the mod redundant/ non-functional. The Parts that remain unchanged by VSR are the only bits of WS that function correctly.
  5. If people believe that those business practices effect the game, then they have every reason to post their opinions as a review, regardless on how overblown their reactions really are.
  6. Mainly this was done to let an ejected escape pod yaw when the escape tower is fired, otherwise the offset was added to simulate the real thing.
  7. Pretty much. Though, there's quite a bit more stuff in there than just the models and textures currently seen (like the wheels/ landing legs, their finished. An unfinished LVN Turboprop and V2 engine) Plus it could be a learning tool for new modders I suppose, even with the broken Unity files. Sadly, during the unity 5 editor conversion, half of the mod vanished, kinda ending development. It's hard to believe that anyone could be slower... *shivers* Thanks for taking the time to do that! I've added the links to the OP.
  8. Dumping the source files, if any of you can re-host the files, and post a new link here that would be fantastic. Same licensing rules as the base mod (https://creativecommons.org/licenses/by/4.0/) : https://www.dropbox.com/s/2hst7myddq34kuk/VSR_Models.zip?dl=0 https://www.dropbox.com/s/t9lw5dm33x7i6g5/VSR_Textures.zip?dl=0 What remains of the unity files will be uploaded when I have more space to upload them. It took two days to upload that second file.
  9. I think you're giving me too much credit... But whatever, I'll just say that it's the case. I've accepted your pull requests and made a proper release and shiz.
  10. Are you dead ven? I hope you are'nt cause this is the best mod ever!

  11. Ven... We need you to officially fix your mod! I cant live without it! I mean the community got almost the whole thing done for you! But we need those spaceX landing legs and such! Please?

  12. Go to Data and then check Auto-Smooth, that'll fix the issue.
  13. Regardless of version, the normal map artifacts (or "blocky lighting") are likely the result of the poor texture compression of DXT5 DDS files. The only way to fix this it is to move to a higher DDS format like DXT7 or to a different format entirely.