Jump to content

Electrocutor

Members
 View Profile  See their activity

  • Posts

    699

  • Joined

  • Last visited

 Content Type 

Everything posted by Electrocutor

  1. Electrocutor
    Honestly, I wish all modders would just have less toolbar spam altogether and find a way to better integrate the interfaces into the game itself. Most of the gameplay settings displayed there could easily just be setup as GameSettings or DifficultySettings instead of having their own settings window that pops-up from the toolbar; and most other things could be integrated into the right-click menus of parts or added into already-existing GUI elements on the HUD. Many settings could also just be delegated to a config file, as only very few people would be interested in changing them from default values (like pop-up window transparency and such).
  2. Electrocutor
    *rolls the dice* "the runes say 'No'." However, when you say that Contract Configurator is not the answer, do realize that most games, including big-named ones like Skyrim, are largely not even playable without mods. Honestly, I think if Squad/Take-Two, or whoever it is that owns KSP now decided to setup a website where people could submit ideas, estimate dev cost, vote on, and allow payments toward new features, they could make KSP pretty profitable while still continually adding features and updates. We'll see how the DLC goes for them, as I suspect Take-Two will not be interested in funneling money into a black-hole if it doesn't do well: in which case, mods are all we have.
  3. Electrocutor
    In all likelihood, stock KSP 1.4 will work perfectly fine in dx12 mode, just like the current version works fine in dx11. Unfortunately, that does not mean that all the mods will.
  4. Electrocutor
    Which is probably why KSP 1.4 will only be using Unity 2017.2. I know that scatterer is currently being worked on, but I'm not sure if dx11 is on his to-do list or not; which other mods do not support dx11? I cannot tell if Kopernicus is or not because KSPRC terrain seems to like dx11 just fine, but SVT does not.
  5. Electrocutor
    You may consider thinking about what options you want available before pouring in your time. KSP_MODEL_SHADER forces whatever you set to be the default. You may have noticed that my newer cfgs are instead using the KSPTextureSwitch part module, because then the person can choose between default, having it be metallic, but using the built-in specular values, forcing it to be metallic, or custom painting. You can also create your own versions of textures/patterns and things like the B9 or Firespitter partmodules.
  6. Electrocutor
    Greetings, Are there any mods that add normal maps to the KSC buildings, pavement, airstrip, pad, tanks, dishes, launchpad, etc? SVT and KSPRC both do not contain these.
  7. Electrocutor
    PorkjetStock is now finished with pass 2.
  8. Electrocutor
    @PART[*]:FOR[zzzz_PorkjetStock]:HAS[#author[*Porkjet*]&!@MODEL[*]|@MODEL:HAS[#model[Squad*]]] I'm looking for (author=*Porkjet* && (no MODEL node || MODEL.model=Squad*)); but this doesn't seem to work? on the syntax page it says that ORs have priority of order so that a|b&c|d would be ((a || b) && (c || d)), but this doesn't seem to actually be the case? [Update] Ignore. I think my test environment had gotten gummed up.
  9. Electrocutor
    So... basically I am working on building smarter cfg files that will detect mods and such. Porkjet has both his own mod pack (Part Overhauls) and parts that he made that are in stock. The parts that he made in stock are more complete than the stock parts made by other authors, so they are much easier to make work properly with TU. The TexturesUnlimited_Stock.cfg is the 'generic stock' I listed above. It was my first pass to just get metal stuff kind of working. If you combine Ven's and Porkjet's stock parts, it pretty much covers all stock parts and the result looks far superior to just using all stock parts. Porkjet's Part Overhaul does not overwrite any stock parts, so it is its own thing. so... Option 1: Generic Stock Option 2: Ven's + PorkjetStock Additional: Porkjet's Part Overhauls
  10. Electrocutor
    @PART[*]:AFTER[Squad|VenStockRevamp] This doesn't work; what I need is for this to always run, but if VenStockRevamp is installed, then it has to run after it. The above, however, only works when VenStockRevamp is installed. Is there some kind of (optional) AFTER?
  11. Electrocutor
    Quick Consolidation... 1. Download Textures Unlimited Mod Here 2. Set your KSP shortcut to use DX11 or GLCore ...\KSP_x64.exe -force-d3d11 ...\KSP_x64.exe -force-glcore 3a. Download Ven's VenStockRevamp and the VenStockRevamp TU_Config 3b. Download Porkjet's stock TU_Config 3c. Download generic stock TU_Config (* don't use this if you are using Ven's and/or PorkjetStock) 4. Download Porkjet's PartOverhauls and the PartOverhauls TU_Config Stock and Ven's config can be considered as pass1, Porkjet's can be considered as pass2. Ven's look much, much, much better than stock due to the original models and textures being more complete. [Update] Fixed landing gear issue. Fixed transparency issue. PorkjetStock Pass 2 PartOverhauls Pass 2 VenStockRevamp Pass 1 B9Aerospace Pass 1 RemoteTech Pass 1 FarFutureTech Pass 1 DMagicScience Pass 1 UniversalStorage Pass 1 // white tanks are silver
  12. Electrocutor
    I wonder if there could be a setting on the drive to control the size of the bubble: larger would allow bigger ships, but require exponentially more power (and create more heat) to activate.
  13. Electrocutor
    #@KSP_TEXTURE_SET[Transparent]/TEXTURE,0 { mesh = Shine } In the above example, the TEXTURE node is copied in, but the additional 'mesh' property is not added. Adding a % before 'mesh' does not change this either. Is this by design or a bug?
  14. Electrocutor
    Okay... #@MY_NODE_LIBRARY/MODULE[MechJebCore] { } I assume that @MY_NODE_LIBRARY is the same as @MY_NODE_LIBRARY,0 and is not required that you create an arbitrary node library? Which means I should be able to use: #@PART[OldPart2]/MODULE[ModuleName] {} to pull everything over?
  15. Electrocutor
    So... getting back on topic, is there a way to clone nodes from a different hierarchy instead of just siblings?
  16. Electrocutor
    The biggest problem is that previously, a lot of broken syntax was being written that didn't actually work, but was just being ignored by MM. Now a lot of that broken syntax actually throws errors saying that it is broken (and prevents that part from moving forward while broken).
  17. Electrocutor
    Is there a way to copy nodes between different roots? for example, something like: +PART[OldPart] { @name = NewName +Child(PART[OldPart2].MODULE[ModuleName]) } The idea if there are tons of properties set in some other parent node, it'd be easier to just copy them than to re-write it all; it would allow you to pull in any value changes from other mods from it.
  18. Electrocutor
    You can use the paint png's from that with the PBR-Masked shader to do recoloring on stock parts if you wish. From a quick look, it seems that most of the paint masks are not stock but instead have designs such as added stripes, gradients, and other details to 'make it look cool'.
  19. Electrocutor
    Using The ease of converting parts to use it on depends on the attention to detail of the original models and textures. (diffuse, specular, normal, material meshing) I've been working on a USI patch, but it will take quite a while finish as most of the parts have a simple model/texture (like non-pork stock), thus more manipulation is needed to make them look right.
  20. Electrocutor
    Just wanted to share some engines from Porkjet and Ven... so dramatically better than stock.
  21. Electrocutor
  22. Electrocutor
    @REFLECTION_CONFIG[default] { %enabled = true %interval = 1 } KSP_TEXTURE_SET { name = reflect TEXTURE { shader = SSTU/PBR/StockMetallicBumped mesh = WINDOWS2 PROPERTY { name = _Metal float = 0.0 } } } @PART[<partname>] { MODULE { name = KSPTextureSwitch currentTextureSet = reflect TEXTURESET { name = reflect } } } or @REFLECTION_CONFIG[default] { %enabled = true %interval = 1 } KSP_MODEL_SHADER { model = <model path> TEXTURE { shader = SSTU/PBR/StockMetallicBumped mesh = WINDOWS2 PROPERTY { name = _Metal float = 0.0 } } }
  23. Electrocutor
    For those who like to tinker, and for those who really want metal in their mod parts before any compatibility patch comes out... This is what I use as a base to work backward from; it will allow you to set all parts to a couple of basic metallic, specular, or dull options. Of note: it will make anything that uses transparency look horrible, and how good each part looks by default depends on how well the textures were originally made.
  24. Electrocutor
    @PART[*]:FOR[zzzVSRPathPatch] So the FOR keyword does not require that some mod exists with that name, but instead gives this cfg a name that decides when it will be applied in alphabetical order? It looks like Ven's cfg is set to apply to all parts at the end if that is the case.
  25. Electrocutor
    so... is it designed behavior for any cloned parts to also be affected by future cfg edits to their parent? Test.cfg: +PART[fuelTank] { @name = TestFuelTank @title = TestFuelTank @mesh = Squad/Parts/FuelTank/fuelTankT400/model -mesh = DELETE -MODEL {} MODEL { model = Test/fuelTank } } ModuleManager.ConfigCache: UrlConfig { name = TestFuelTank type = PART parentUrl = Squad/Parts/FuelTank/fuelTankT400/fuelTankT400 PART { name = TestFuelTank ... MODEL { model = VenStockRevamp/Squad/Parts/Propulsion/T400Tank } } }
×
×
  • Create New...