xx_mortekai_xx

Members
  • Content Count

    55
  • Joined

  • Last visited

Community Reputation

16 Good

1 Follower

About xx_mortekai_xx

  • Rank
    Rocketry Enthusiast

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ok, cool. I tend to use procedural parts tanks to measure things in game, and that gets down to the thousandths of a meter. It has worked out pretty well so far. I pulled the top node info from the original engine config, though. I have some questions about...converting?...some other model's textures to use with TU, as I'm a big fan of the shaders, but I'll play around with that and get an idea of my limits of understanding before unpacking that. However, if you have a link to an existing tutorial that may help, that would be much appreciated. I must say, on the clustering module, that is a genius way of cutting part counts. And it is so well implemented. Again, thanks for the work, and for the help
  2. Yeah I noticed the same thing last night, as per my post on the previous page. It does work after those changes. Thank you for the help. I do greatly appreciate it.
  3. I think i found the issue.....you have the model for the engines set to "EmptyProxyModel", which appears to be just that - a model of nothing that serves as placeholder. The cluster module adds the model, and duplicates it as needed. To the game, its one part. To the eye, its not. The engine I am trying to cluster still has its own model set as the model instead of the empty one. So the clustering module is doing its job just fine, but its doing it over the model that is already there.
  4. Sure, that WOULD be the easy way. But if I can learn how to do it the right way, especially from the one who wrote the module, that would be preferable. I like learning how to do things. Judging from your posts, you do too. So I am relatively sure you can understand that. I do appreciate the suggestion, though.
  5. The Raptor engine from the TundraExploration mod. It does not use ModulePartVariants. It looks to be a fairly normal engine config, but most of my experience has been 1.5.1 and older. I have never seen FXModuleLookAtConstraint before, but all the others I believe I have seen. The config is below, with my modifications below that. I havent gotten to getting the correct numbers for the cluster module, and have simply used the module from the LR81-8096 in your pack. PART { name = TE_18_BFS_SL_RAPTOR module = Part author = Damonvv MODEL { model = TundraExploration/Parts/GOJIRAII/TE_18_BFS_SL_RAPTOR } rescaleFactor = 1 node_stack_top = 0.0, 0.6502519, 0.0, 0.0, 1.0, 0.0, 0 node_stack_bottom = 0.0, -0.664, 0.0, 0.0, -1.0, 0.0, 0 TechRequired = veryHeavyRocketry entryCost = 13000 cost = 9120 category = Engine subcategory = 0 title = RPTR-21 "Raptor" Engine manufacturer = Tundra Exploration description = This vacuum optimized engine is designed to be one of the best in class. Without these you probably won't get far. tags = cck-tundra falcon Raptor s0 engine BFS BFR SpaceX attachRules = 1,0,1,0,0 mass = 2.4 // heatConductivity = 0.06 // half default skinInternalConductionMult = 4.0 emissiveConstant = 0.8 // engine nozzles are good at radiating. dragModelType = default maximum_drag = 0.2 minimum_drag = 0.2 angularDrag = 2 crashTolerance = 8 maxTemp = 2000 bulkheadProfiles = size0 // autoStrutMode = Grandparent EFFECTS { running_closed { AUDIO { channel = Ship clip = sound_rocket_spurts volume = 0.0 0.0 volume = 0.2 0.25 0 0 volume = 1.0 1.0 pitch = 0.0 0.2 pitch = 1.0 0.5 loop = true } PREFAB_PARTICLE { prefabName = fx_smokeTrail_veryLarge transformName = smokepoint emission = 0.0 0.0 emission = 0.05 0.0 emission = 0.075 0.25 emission = 1.0 1.25 speed = 0.0 0.25 speed = 1.0 1.0 localOffset = 0, 0, 1 } MODEL_MULTI_PARTICLE { name = flare modelName = TundraExploration/FX/rptrFlare transformName = thrustTransform emission = 0.0 0.0 emission = 0.3 0.15 emission = 1.0 1.0 speed = 0.3 0.2 speed = 1.0 1.0 energy = 0.2 0.4 energy = 1.0 1.0 } MODEL_MULTI_PARTICLE { name = shock modelName = TundraExploration/FX/rptrShock transformName = thrustTransform emission = 0.2 0.0 0 0 emission = 0.4 0.4 0 0 emission = 0.8 1.0 0 0 speed = 0.2 0.2 speed = 1.0 1.0 energy = 0.2 0.5 energy = 0.4 1.0 } } engage { AUDIO { channel = Ship clip = sound_vent_soft volume = 1.0 pitch = 2.0 loop = false } } flameout { PREFAB_PARTICLE { prefabName = fx_exhaustSparks_flameout_2 transformName = smokePoint oneShot = true } AUDIO { channel = Ship clip = sound_explosion_low volume = 1.0 pitch = 2.0 loop = false } } } MODULE { name = ModuleEnginesFX runningEffectName = running_closed thrustVectorTransformName = thrustTransform exhaustDamage = True ignitionThreshold = 0.1 minThrust = 0 maxThrust = 420 heatProduction = 350 fxOffset = 0, 0, 1.2 EngineType = LiquidFuel PROPELLANT { name = LiquidFuel ratio = 0.9 DrawGauge = True } PROPELLANT { name = Oxidizer ratio = 1.1 } atmosphereCurve { key = 0 356 key = 1 330 key = 3 0.001 } } MODULE { name = ModuleAlternator RESOURCE { name = ElectricCharge rate = 10.0 } } RESOURCE { name = ElectricCharge amount = 0 maxAmount = 0 isTweakable = false hideFlow = true } MODULE { name = ModuleSurfaceFX thrustProviderModuleIndex = 0 fxMax = 0.8 maxDistance = 50 falloff = 2 thrustTransformName = thrustTransform } MODULE { name = ModuleGimbal gimbalTransformName = gimbalTransform gimbalRange = 2 useGimbalResponseSpeed = true gimbalResponseSpeed = 10 } MODULE { name = FXModuleLookAtConstraint CONSTRAINLOOKFX { targetName = Pipe2 rotatorsName = Piston2 } CONSTRAINLOOKFX { targetName = Piston2 rotatorsName = Pipe2 } CONSTRAINLOOKFX { targetName = Pipe1 rotatorsName = Piston1 } CONSTRAINLOOKFX { targetName = Piston1 rotatorsName = Pipe1 } } MODULE { name = FXModuleThrottleEffects fxModuleNames = heatColor responseSpeed = 0.005 dependOnEngineState = True dependOnThrottle = True } MODULE { name = FXModuleThrottleEffects fxModuleNames = throttleColor responseSpeed = 1.0 dependOnEngineState = True dependOnThrottle = True } MODULE { name = ModuleColorChanger moduleID = heatColor animRate = 1 shaderProperty = _EmissiveColor toggleInEditor = false toggleInFlight = false redCurve { key = 0 0 key = 1 1 } greenCurve { key = 0 0 key = 1 1 } blueCurve { key = 0 0 key = 1 1 } alphaCurve { key = 0 0 key = 1 1 } } MODULE { name = ModuleColorChanger moduleID = throttleColor animRate = 1 shaderProperty = _EmissiveColor toggleInEditor = false toggleInFlight = false redCurve { key = 0 0 key = 1 1 } greenCurve { key = 0 0 key = 1 1 } blueCurve { key = 0 0 key = 1 1 } alphaCurve { key = 0 0 key = 1 1 } } } @PART[TE_18_BFS_SL_RAPTOR]:NEEDS[RealFuels,TundraExploration]:FOR[TundraExploration] //0.75 - L+ { @attachRules = 1,1,1,1,1 @MODULE[ModuleEnginesFX] { //@name = ModuleEnginesRF @maxThrust = 332.26 %powerEffectName = RaptorPlume %heatProduction = 69.91924082 !PROPELLANT[*],* {} PROPELLANT { name = LqdMethane ratio = 43.0255036406703 DrawGauge = True %ResourceFlowMode = STACK_PRIORITY_SEARCH } PROPELLANT { name = LqdOxygen ratio = 56.9744963593297 %ResourceFlowMode = STACK_PRIORITY_SEARCH } @atmosphereCurve { @key,0 = 0 355.63 @key,1 = 1 283.04 } } MODULE { name = SSTUModularEngineCluster engineModelName = TundraExploration/Parts/GOJIRAII/TE_18_BFS_SL_RAPTOR currentEngineLayoutName = Single engineSpacing = 0.65 engineHeight = 1.45290 engineYOffset = 0 engineScale = 1 partTopY = 0.6502519 smokeTransformName = smokepoint smokeTransformOffset = -1.75 diameterIncrement = 0.625 engineMountDiameter = 0.8 upperStageMounts = true lowerStageMounts = false } }
  6. @Shadowmage I have a question about your engine clustering plugin. I am attempting to add this to another engine, and I am getting an odd issue where the engine will duplicate itself, with one instance being what seems to be the engine as it is without the clustering plugin, and one that will conform to the specifics of the cluster. Do you have an idea about why this might be happening? I can happily provide any info you would like. I just like the clustering you have done with that plugin, and wish to use it on most, if not all, of the engines that I have, not just yours. On a side note, it seems that your package here has been a big step away from my ProceduralParts addiction. Thank you much for your work. I see that you are having frustrations with the state of the game, and the direction of the sequel, but rest assured that many of us are immensely grateful for your contributions in making this game far more than it ever would have been without you and those like you.
  7. I got it working by removing the directory entry for the Mk1-3 from the blacklist (GameData\ReStock\Restock.restockblacklist) and commenting out the modulemanager file in the patches folder (\GameData\ReStock\Patches\Command\restock-command-pods.cfg). Removing the blacklist entry allows the stock textures to load, while commenting out the modulemanager file entry removes the instruction for the model and textures to be changed. If you only remove the blacklist entry, the pod wont change, as it will still change the model and texture, but the stock textures will load only to be unused. If you only comment out the .cfg, youll get a strange version of the stock pod that has no textures and is impossible to select again once placed in the VAB or SPH. If you are going to spend any time at all inside .cfg files, I would HIGHLY recommend picking up a good text editor like Notepad++ or Sublime Text. Your eyes and nerves will thank you.
  8. Nevermind, I see the whitelist/blacklist thing.
  9. I love the work you have done here, and I would love to use it, but I use SDHI for my CSM, and it doesnt really fit with your overhaul of the Mk1-3 pod (the umbilical decal doesnt show up, and the dimensions are different, which means the heat shield and the adapter ring dont fit) Is there a way to exclude specific parts from being changed by your mod?
  10. http://bfy.tw/MrjJ It took longer to get that link than to find the package. MAYBE 10 seconds.
  11. is it possible for me to add ModuleAnimatedDecoupler to the joints that are reinforced? I tried adding it as decouplerStiffeningExtensionType5 (replacing the entry that was there), but it doesnt seem to work. I am trying to prevent bouncing in the joint between the crew adapter and heatshield from the SDHI mod, and the decoupler is not a standard one (which is likely why its not already strengthened by this mod, at least in my thinking).
  12. Cool. That would be ideal. Thank you for keeping this going.
  13. Because at times it will call over and over and over, filling my logs. This makes it difficult to find other log entries at times.