StarVision

Okay, been a long time, but I've essentially removed the previous license, and 'formally' discontinued this. Apologies for taking so long. I feel bad enough bumping this thread to the front when there's nothing new, but it seems others have been doing that anyways. I kept thinking I was going to get back to this, but clearly not. I don't have any of the unity files anymore, but I don't know if those are needed to update to the current version. I haven't played in awhile. Anyways, hope someone can make use of this license change. At the very least it's not holding anyone back now. Cheers!

You could try removing the BackLight,FrontLight stuff, as that isn't supposed to be there. I'm not really sure what else to do. There must be some special thing in Unity that it needs. The new version is uploaded, and hopefully is bug free. Voyager can fly a lot better in atmosphere now that I've adjusted some things. No more flipping out (within reason). Everything in the pack has also been rebalanced, and should run a lot better. Anyways, try it out. And don't be afraid to tell me if something doesn't seem right or should be adjusted. That's one of the main reasons this update came out anyways.

I think I know how to fix it. From what I can tell, the torpedoes and phasers are emitted from gameObjects which have to be specified in the cfg. In the LCARSMarkII module, after the line where it says TractorAssembly, paste this in: PhaserBanks_GameObjects = thrustTransform TorpedoTubes_GameObjects = thrustTransform It's kind of a dirty way of doing it, but unless they need some sort of special of tag or collider, I don't see why it wouldn't work.

From what I gather, you just have to copy the modules from this post into Voyager's cfg (located in SciFi/_Voyager/Parts/voy_saucer/part.cfg) So basically just copy this code into the cfg somewhere before the final closing bracket and you should be good: MODULE { name = LCARSMarkII engine_type = 0.1 // valid settings: 0.1,0.25,0.5,1,2,3,4,5 CrewQuartiers_MaxCrewSpace = 0 // int seat number; set to a reasonable value for this model // resource options max_resource_tanks = 1 // int tank number; set to a reasonable value for this model max_resource_amount = 0.5 // float in tons; set to a reasonable value for this model TractorAssembly_GameObjects = // a list of GameObects, that are actually present in the model. If you don't know the exact name(s), leave it empty. } RESOURCE { name = CondensedDeuterium amount = 100 maxAmount = 500 } and you'll have to change Voyager's current ElectricCharge resource to this (delete the old one and paste this one in.) RESOURCE { name = ElectricCharge amount = 50000000 maxAmount = 50000000 } Of course there are no guarantees this will work, but here's hoping.

Why would you ask for that here? Anyways, as required by the forum rules you can look over Philotical's code if you want to, but you can't copy it or anything, as that would be stealing. His thread is here. In regards to my mod, I think the balancing update is good to go. I took the sort-of-easy way out for the warp drive. I just made a separate part for the module, so you can attach it to the current ships, which have had a node placed at 0,0,0 for you to place it into (except for the phoenix, which has it's own part as it should). I'm actually on holiday right now, but I might be able to get it uploaded later this week, after a bit more testing.

I guess I could make the impulse a separate part, but that would require editing the model and putting the whole thing through unity again. I'm kind of scared to do that because I've been using the same exported model for a really long time now, so I'm worried I'm going to break it if I change something. I suppose Voyager wouldn't have this problem, because it already has two big parts. I just have to use MODEL{} to put in a new thrustTransform, because the current one is designed for landing vertically.. Something that might work though is to have just another engine on the part. That would mean two 'activate engine' things, but it would be pretty obvious which engine you activated by the presence of the giant warp bubble. There's still another solution to this though: obscenely overpowered RCS. On the topic of docking, maybe I can edit the existing docking port to blend in better, and barely stick out of the hull. Something like that would be a lot nicer. Or I could just create a new one entirely. Maybe it could have an animation that makes it invisible, kind of like the Tardis but even more so. edit: problem solved

I've basically done the same thing so far. The balancing is hard though. Since I made the ships heavier, I also need to make them more powerful, and then that leads to even more complications. I think I've got them balanced for stock, I just need to somehow find a way to get them to work with the warp plugin. I'm hoping I'll be done sometime tomorrow. Also the photon torpedo is really awesome with BDArmory now.

I think it is still using old wing parameters, so that's probably it. Should be working fine by the end of the week. There's no special way to do it. Just radially attach a docking port or something. Yep.

1. The ships definitely don't explode as often now, and I think I messed with the thrust values a bit for the new update. I will however later this week actually go through everything and balance them out. Hopefully some level of consistency can be reached. 2. Fixed. That was an issue with the new node system. In the new system nodes can only face one way (to prevent placing parts inside of each other) so I had to go through all the parts and make the nodes face the right way. 3. That was something to do with texture formats I think. I haven't had any of those issues so far, although I also haven't tried out ATM since 1.0 was released. 4. I was always sort of looking at those module manager patches and thinking "good enough", so I'm not too surprised they didn't always work. I think you're right, and I should just stick to the standalone warp drive. Next release I'll try and get a working patch going. 5. Once again a balancing issue, which I'll go over next update for sure. Thank you very much for your in depth report. It should help me sort through some of the issues and correct them. It's nice to get feedback that isn't just "make this ship from this series". I appreciate it. hopefully I can deliver a fully working and balanced update by the end of the week. edit: you're saying the nodes didn't work with newest version. That's weird, because they were definitely working for me. I'll look into it. edit 2: Did you per chance just click download? I originally had 3.0 as an alpha release, so you might have downloaded the last file marked as a regular release instead. I've already fixed that problem, so it shouldn't happen again, if it even did to begin with.

You are correct. The blueprints I was using placed it on the wrong side. I'll see if I can move it. I have not actually seen Firefly (nor do I plan to in the upcoming future). I tried watching it, but I just couldn't get past the western music. Anyway, That's besides the point, as I'm not really doing any more big things. Also my computer is actually fine, and it has been for months. The thing holding me back right now are Exams (almost over), and the Crimson Pig. I've tried everything but the wings always seem to explode when loaded. I'm not sure if it's related to the new aerodynamics, or if its just a new collider issue. Hopefully I should be able to finally finish this update once school is done, but until then not much is going to get done.

That's a good idea. I'll see if I can implement it. Sorry, I kind of forgot about it. I did create the .ckan file, I just never did anything with it. I guess I have to add the file to the CKAN github or something. If I have some free time this weekend I'll try and get it working. It's near the end of school so things are getting kind of busy.