jrodriguez

@R-T-B Thank you for all the effort. It works pretty well! I just uploaded a new video doing a Earth test of the latest release with RSS.

Would you mind to test this BDArmory version? https://1drv.ms/u/s!AixZLrjtqp-Rgswh2rsG5TEv36pfTA?e=gkkfNf I have fixed the shaders there, if it works fine I will do an official release @Box of Stardust I'm thinking that it might be possible that @TheKurgan found the root cause. Would you mind to test also https://1drv.ms/u/s!AixZLrjtqp-Rgswh2rsG5TEv36pfTA?e=gkkfNf ? Thanks

New release here! https://github.com/jrodrigv/PhysicsRangeExtender/releases/tag/1.19.0 Changelog: = v1.19.0 - Recompiled for KSP 1.9.1 - Fixed critical issue causing KSP to crash when extending terrain in other planets like Moon in RSS. - Fixed NREs issue when extending terrain in orbit around the Sun - Increased Crash Tolerance in landed vessel when loaded to avoid RUDs due to physics.

This looks amazing @pingopete looking forward to give a try! Regarding TUFX and KS3P I think the best option at the moment is to mix both of them.

Thank you for the feedback I'm working on a fix for this issue and some other opened issues

Hi all, This is the current profile I'm using for a realistic Earth view in RSS. I still doing changes because at the end is always a trade-off specially regarding light intensity (Autoexposure/PostExposure are the key values here). This profile is specially tailored for earth-orbit view and ground view. However, other celestial bodies like Moon are a bit darker or brighter depending on its "albedo". Also the Earth view from Moon is much more brighter than in reality but as I said before, it is a trade-off. TUFX_PROFILE { name = Default-Flight // Current profile name. Please make copies of the default profiles and specify new names if you wish to change settings. hdr = False antialiasing = FastApproximateAntialiasing EFFECT { name = AmbientOcclusion Intensity = 4 NoiseFilterTolerance = -5.38364744 BlurTolerance = -5.02830172 UpsampleTolerance = -5.63522005 ThicknessModifier = 0.00999999978 Radius = 1 } EFFECT { name = AutoExposure Filtering = 0,82.5999985 MinLuminance = -3.36037779 MaxLuminance = -5.7 KeyValue = 0.02 EyeAdaption = Progressive } EFFECT { name = Bloom Intensity = 0.200000003 Threshold = 1.5 SoftKnee = 0.709999979 DirtIntensity = 5 } EFFECT { name = ColorGrading GradingMode = HighDefinitionRange Tonemapper = ACES ToneCurveToeStrength = 0 Temperature = 6 HueShift = -6 Saturation = 2.8499999 PostExposure = 4 Contrast = 6 Gain = 1,1,1,-0.5 } EFFECT { name = ChromaticAberration Intensity = 0.0299999993 SpectralLut = KS3P/Textures/SpectralLut_RedBlue } } @Shadowmage I'm using a spectralLut from KS3P but I'm not completely sure if this feature is currently supported. I can't see on the UI if the defined spectrallut is being used (I have created a Fork and I'll investigate it)

Everything can be fixed.

That's right. There is no way to keep the tracking windows open when using a different active vessel.

Yes but if you switch you will not be able to see the camera tracking window (this is because the camera tracking window is bound to the vessel that has the camera tracking module)

uhm as you can see on the video. I'm not really controlling the rocket, the rocket is controlled by itself (mechjeb) I'm only acting as an spectator, enjoying a beautiful and success launch.

If a Pull Request is made and it works, of course You will need to tweak the radar to have an increased locking range (I'm using like 2000 km in that video) , you will need to change the camera tracking FOV resolutions to be able to continue zooming , increase the bdarmory settings ranges and attach a weapon manager to the rocket that you want to track. By the way I have plans to create a separate mod to include just a tracking camera for rockets and satellite tracking using the BDArmory camera but without any logic regarding radar locking or anything related with BDArmory.

Do you mean something like this?

Nicely done I'm happy to see someone implementing new things.

- HDR is not working properly with EVE clouds. All the sky is black so I decided to not use HDR for the moment. - I think it not a good idea to mix KS3P and TUFX. I'm using the latest Multi Scale Volumetric occlusion because it has better performance and once tweaked it doesn't look bad

This is all thanks to TUFX power

I think the weapon should fire explosive bullets like the 30x173HEBullet and the weapon cfg should have airDetonation = true Regarding the other questions I can't give you an answer without investing few hours sorry. You will have to install Visual Studio, Unity Studio and start debugging the code and profiling to find the root causes and implement the solutions

2) Thanks for the feedback I guess I did not test to switch the mesh. 3) I know the ideal thing is to include new specific textures for B9 ProcWings but I'm not an expert in creating textures so for the moment I made the decision to just use the ones included in ProceduralParts. 4) If you have the time to add those features/improvements feel free to do Pull Request or even a fork. I only decided to make public the TU support because I did it for my own benefit and a lot of people were begging me to make it public but I don't have plans to make any further improvements. I will do the basic maintenance or bug fixing to keep the mod alive. Thanks, I will include that config as part of the release, cheers.

I have spent most part of the weekend creating a profile for RSS/Earth. This is the result .(DX 12) Thanks @Shadowmage

jaja es muy loco lo tuyo. No, nos han dando absolutamente nada de información por ahora.

Hi all, I just did a new release of this mod compatible with KSP 1.8.X and KSP 1.9.X https://github.com/jrodrigv/B9-PWings-Fork/releases/tag/v0.93 Changelog: Shaders should work again in OpenGL TU support added (it is mandatory to install https://github.com/KSP-RO/ProceduralParts/releases/tag/v2.0 and https://github.com/shadowmage45/TexturesUnlimited/releases/tag/1.5.10.25) I would like to say thank you to @DRVeyl and @nepphhh for their beautiful work with ProceduralParts and the new metallic textures And of course @shadowmage45 for his amazing TU mod (and TUFX of course...) Summarizing: @Jebman82 Would you mind to test it to see if the new shaders using SM 3.0 are working in OpenGL mode?

I have recompiled CameraTools for KSP 1.9.1 You can find it here: https://github.com/jrodrigv/CameraTools/releases/tag/v1.14.0

I will provide a fix for this

Don't get me wrong. I'm a Dev myself and KSP modder. I really hope that the Scatterer can be fixed with just one line of code to deactivate the single camera setup. My main concern is that these things can go from one line of code, to require a nasty serenity patch or to even require a new KSP release. By the way, is the Ambient Occlusion the new Multi Scale Volumetric Occlusion?

Thank you @Shadowmage I was about to implement the same for KS3P when @Poodmund talk me about this I will give a go using DX12 (I might recompile the shaders if necessary) After the Scatterer blocker issue with the single camera setup I have the feeling that DX12 is going to become mandatory for me.

The current release of BDArmory is targeting SM 5.0 for its shaders. I guess that it will not work unless you have a DX11 compatible GPU/OS I will consider targeting a lower version in the future for better compatibility with Mac Haven't tested it yet. I will let you know.