[1.12.x] Docking Camera KURS Style Re-Adopted (Fixed in 1.9)

Atlas Gaming · March 26, 2023

Not sure if this is a known issue right now or not, but my Onboard Camera does not pop up the camera window after activating it. Last I used this mod was a couple years ago and remember it worked great. Runnin latest v 1.3.8.5 CKAN

LOG https://www.dropbox.com/t/x2NXgbuGA7zEuQD9

Atlas Gaming · March 28, 2023

Just checked the docking camera and it does not work either... the camera window does not pop-up. Runnin latest v 1.3.8.5 CKAN

LOG https://1drv.ms/u/s!AszZjw7kTT6zg7J-NmujgZDSW40vUQ?e=dafWPB

UPDATE: just installed Hullcam VDS to test and the cameras in that do work.

Edited March 28, 2023 by Atlas Gaming

OrbitalManeuvers · March 28, 2023

1 hour ago, Atlas Gaming said:

Just checked the docking camera and it does not work either... the camera window does not pop-up. Runnin latest v 1.3.8.5 CKAN

LOG https://1drv.ms/u/s!AszZjw7kTT6zg7J-NmujgZDSW40vUQ?e=dafWPB

pardon my butting in ... but you have about 100MBs of RocketSoundEnhancement exception text in your log file. I would recommend maybe either looking at that first, or perhaps just eliminating it while you figure out the other stuff. KSP does not do well with exceptions every frame, which is what it looks like you have there. I have 90+ mods and my log file is 10-15MB after a few flights. Yours is 134MB.

Just another player's opinion. LGG may have other thoughts!

Atlas Gaming · March 28, 2023

4 minutes ago, OrbitalManeuvers said:

pardon my butting in ... but you have about 100MBs of RocketSoundEnhancement exception text in your log file. I would recommend maybe either looking at that first, or perhaps just eliminating it while you figure out the other stuff. KSP does not do well with exceptions every frame, which is what it looks like you have there. I have 90+ mods and my log file is 10-15MB after a few flights. Yours is 134MB.

Just another player's opinion. LGG may have other thoughts!

Ya I can disable that next launch and copy updated log.

Atlas Gaming · March 29, 2023

5 hours ago, Atlas Gaming said:

Ya I can disable that next launch and copy updated log.

Ok fresh log file... same link https://1drv.ms/u/s!AszZjw7kTT6zg7J-NmujgZDSW40vUQ?e=dafWPB

linuxgurugamer · March 30, 2023

On 3/26/2023 at 6:12 PM, Atlas Gaming said:

Not sure if this is a known issue right now or not, but my Onboard Camera does not pop up the camera window after activating it. Last I used this mod was a couple years ago and remember it worked great. Runnin latest v 1.3.8.5 CKAN

LOG https://www.dropbox.com/t/x2NXgbuGA7zEuQD9

Can you please install the Notes2Log mod, write notes before and after you try to activate KURS, then get me the log. Also, a video would be helpful

Atlas Gaming · April 1, 2023

On 3/30/2023 at 11:01 AM, linuxgurugamer said:

Can you please install the Notes2Log mod, write notes before and after you try to activate KURS, then get me the log. Also, a video would be helpful

Crap! My year old game file got corrupted. starting from scratch with fewer mods, will see if Docking Camera works

Atlas Gaming · April 4, 2023

On 4/1/2023 at 4:59 PM, Atlas Gaming said:

Crap! My year old game file got corrupted. starting from scratch with fewer mods, will see if Docking Camera works

Must have been related to the bad save file... it's working on a new save!

xZise · October 22, 2023

Hi, I know this thread is quite old but I'm again playing KSP again. As I previously really liked this mod I installed it again via CKAN but for I get the following exception when loading a save game:

[ERR 13:42:40.669] Texture has out of range width / height

[ERR 13:42:40.670] Module PartCameraModule threw during OnStart: UnityEngine.UnityException: Failed to create texture because of invalid parameters.
  at UnityEngine.Texture2D.Internal_Create (UnityEngine.Texture2D mono, System.Int32 w, System.Int32 h, System.Int32 mipCount, UnityEngine.Experimental.Rendering.GraphicsFormat format, UnityEngine.Experimental.Rendering.TextureCreationFlags flags, System.IntPtr nativeTex) [0x00021] in <12e76cd50cc64cf19e759e981cb725af>:0 
  at UnityEngine.Texture2D..ctor (System.Int32 width, System.Int32 height, UnityEngine.TextureFormat textureFormat, System.Int32 mipCount, System.Boolean linear, System.IntPtr nativeTex) [0x0003d] in <12e76cd50cc64cf19e759e981cb725af>:0 
  at UnityEngine.Texture2D..ctor (System.Int32 width, System.Int32 height) [0x00000] in <12e76cd50cc64cf19e759e981cb725af>:0 
  at OLDD_camera.Utils.Util.MonoColorTexture (UnityEngine.Color color, System.Int32 width, System.Int32 height) [0x00000] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Utils.Util.MonoColorVerticalLineTexture (UnityEngine.Color color, System.Int32 size) [0x00000] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Camera.BaseCamera.InitTextures () [0x000e2] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Camera.BaseCamera.DoResizeWindow (System.Int32 WindowSizeCf) [0x00020] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Camera.BaseCamera.LoadWinSettings () [0x00020] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Camera.BaseCamera.InitBaseCamera (Part thisPart, System.Single windowSizeInit, System.String windowLabel, System.Boolean firstTime) [0x00140] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Camera.BaseCamera..ctor (Part thisPart, System.Single windowSizeInit, System.String windowLabel) [0x000d2] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Camera.PartCamera..ctor (Part thisPart, System.String resourceScanning, System.Double electricchargeCost, System.String bulletName, System.Int32 hits, System.String rotatorZ, System.String rotatorY, System.String zoommer, System.Single stepper, System.String cameraName, System.Int32 allowedScanDistance, System.Int32 windowSize, System.Boolean isOnboard, System.Boolean isLookAtMe, System.Boolean isLookAtMeAutoZoom, System.Boolean isFollowMe, System.Boolean isTargetCam, System.Single isFollowMeOffsetX, System.Single isFollowMeOffsetY, System.Single isFollowMeOffsetZ, System.Single targetOffset, System.String restrictShaderTo, System.String windowLabel) [0x00007] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Modules.PartCameraModule.OnStart (PartModule+StartState state) [0x00013] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at Part.ModulesOnStart () [0x00120] in <4b449f2841f84227adfaad3149c8fdba>:0

Unfortunately I wasn't able to find anything related to this exception and mod. I compared the installed files with the release the from github and every file is identical with the following two files only existing in the GameData directory of my Steam installation (so I'd assume that CKAN did it not mess up):

Parts/@thumbs/OnboardCamera_icon.png
PluginData/DockingCamera.cfg

I'm using KSP version 1.12.5.3190, Making History 1.12.1, Breaking Ground 1.7.1 with mod version 1.3.8.5.

linuxgurugamer · October 23, 2023

On 10/22/2023 at 8:08 AM, xZise said:

Hi, I know this thread is quite old but I'm again playing KSP again. As I previously really liked this mod I installed it again via CKAN but for I get the following exception when loading a save game:

[ERR 13:42:40.669] Texture has out of range width / height

[ERR 13:42:40.670] Module PartCameraModule threw during OnStart: UnityEngine.UnityException: Failed to create texture because of invalid parameters.
  at UnityEngine.Texture2D.Internal_Create (UnityEngine.Texture2D mono, System.Int32 w, System.Int32 h, System.Int32 mipCount, UnityEngine.Experimental.Rendering.GraphicsFormat format, UnityEngine.Experimental.Rendering.TextureCreationFlags flags, System.IntPtr nativeTex) [0x00021] in <12e76cd50cc64cf19e759e981cb725af>:0 
  at UnityEngine.Texture2D..ctor (System.Int32 width, System.Int32 height, UnityEngine.TextureFormat textureFormat, System.Int32 mipCount, System.Boolean linear, System.IntPtr nativeTex) [0x0003d] in <12e76cd50cc64cf19e759e981cb725af>:0 
  at UnityEngine.Texture2D..ctor (System.Int32 width, System.Int32 height) [0x00000] in <12e76cd50cc64cf19e759e981cb725af>:0 
  at OLDD_camera.Utils.Util.MonoColorTexture (UnityEngine.Color color, System.Int32 width, System.Int32 height) [0x00000] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Utils.Util.MonoColorVerticalLineTexture (UnityEngine.Color color, System.Int32 size) [0x00000] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Camera.BaseCamera.InitTextures () [0x000e2] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Camera.BaseCamera.DoResizeWindow (System.Int32 WindowSizeCf) [0x00020] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Camera.BaseCamera.LoadWinSettings () [0x00020] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Camera.BaseCamera.InitBaseCamera (Part thisPart, System.Single windowSizeInit, System.String windowLabel, System.Boolean firstTime) [0x00140] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Camera.BaseCamera..ctor (Part thisPart, System.Single windowSizeInit, System.String windowLabel) [0x000d2] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Camera.PartCamera..ctor (Part thisPart, System.String resourceScanning, System.Double electricchargeCost, System.String bulletName, System.Int32 hits, System.String rotatorZ, System.String rotatorY, System.String zoommer, System.Single stepper, System.String cameraName, System.Int32 allowedScanDistance, System.Int32 windowSize, System.Boolean isOnboard, System.Boolean isLookAtMe, System.Boolean isLookAtMeAutoZoom, System.Boolean isFollowMe, System.Boolean isTargetCam, System.Single isFollowMeOffsetX, System.Single isFollowMeOffsetY, System.Single isFollowMeOffsetZ, System.Single targetOffset, System.String restrictShaderTo, System.String windowLabel) [0x00007] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Modules.PartCameraModule.OnStart (PartModule+StartState state) [0x00013] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at Part.ModulesOnStart () [0x00120] in <4b449f2841f84227adfaad3149c8fdba>:0

Unfortunately I wasn't able to find anything related to this exception and mod. I compared the installed files with the release the from github and every file is identical with the following two files only existing in the GameData directory of my Steam installation (so I'd assume that CKAN did it not mess up):

Parts/@thumbs/OnboardCamera_icon.png
PluginData/DockingCamera.cfg

I'm using KSP version 1.12.5.3190, Making History 1.12.1, Breaking Ground 1.7.1 with mod version 1.3.8.5.

No logs, no support

xZise · October 23, 2023

Here you go: KS-Kurs-Exception.log

xZise · October 24, 2023

Hi, in case it helps I uninstalled all mods with CKAN except this one (and the three dependencies). I uploaded the new (and shorter) log with the same exception: https://1drv.ms/u/s!Ajajofua0QHUgq9sav8ESTr1pkwC8A?e=6ZffWh

linuxgurugamer · November 2, 2023

On 10/24/2023 at 11:41 AM, xZise said:

Hi, in case it helps I uninstalled all mods with CKAN except this one (and the three dependencies). I uploaded the new (and shorter) log with the same exception: https://1drv.ms/u/s!Ajajofua0QHUgq9sav8ESTr1pkwC8A?e=6ZffWh

Sorry for the delay, I'll try to look at this soon

You still have the FAR cfg files, please remove those and do another file.

Thx

GlitchyTypo · December 14, 2023

Hey, wondering if you know of a way to disable the science aspect of the additional camera part, its been messing with some of my contract packs and I dont want to risk bricking my save if you know of a safe way. Thanks!

Aelfhe1m · December 14, 2023

5 hours ago, GlitchyTypo said:

Hey, wondering if you know of a way to disable the science aspect of the additional camera part, its been messing with some of my contract packs and I dont want to risk bricking my save if you know of a safe way. Thanks!

Add a ModuleManager patch file (create a new text file, copy in the below text and save it with the filename of your choice and a .cfg extension anywhere in your KSP GameData folder) :

!EXPERIMENT_DEFINITION:HAS[#id[TargetScanning]] {}

@PART:HAS[@MODULE[ModuleSpyExperiment]]
{
	!MODULE[ModuleSpyExperiment] {}
}

DISCLAIMER: Untested but it's a very simple patch, so I can't see any reason it won't work.

GlitchyTypo · December 16, 2023

On 12/14/2023 at 5:55 AM, Aelfhe1m said:
Add a ModuleManager patch file (create a new text file, copy in the below text and save it with the filename of your choice and a .cfg extension anywhere in your KSP GameData folder) :
!EXPERIMENT_DEFINITION:HAS[#id[TargetScanning]] {}

@PART:HAS[@MODULE[ModuleSpyExperiment]]
{
	!MODULE[ModuleSpyExperiment] {}
}
DISCLAIMER: Untested but it's a very simple patch, so I can't see any reason it won't work.

This worked like a charm! thanks!
Could you give me a quick rundown on where the "moduleSpyExperiment" came from though? im looking through the files and trying to understand how to write my own patches eventually

Aelfhe1m · December 16, 2023

8 hours ago, GlitchyTypo said:

This worked like a charm! thanks!
Could you give me a quick rundown on where the "moduleSpyExperiment" came from though? im looking through the files and trying to understand how to write my own patches eventually

I looked at the camera part config file to find a module that ran the science experiment and didn't find any of the usual suspects, with the only likely one being the moduleSpyExperiment.

To verify I then did a search for the code implementing the moduleSpyExperiment and confirmed it was based on the stock ModuleScienceExperiment. As a final check to make sure removing it wouldn't have any unintended side-effects, I also searched for other references to it in the source code and confirmed that the only other code referring to it was in the camera part code and it did a proper check to make sure that the module was actually present before trying to access it. (You can usually skip this last step if you aren't a coder, I was just being extra careful)

cyberKerb · January 30

Hey @linuxgurugamer!

New log file here for you when you get a chance: https://www.dropbox.com/s/545ci28oilowfpw/KSP.log?dl=0
Fresh install of latest KSP version and tried this mod.

No camera window is appearing for KSP 1.12.5.3190 after clicking the button in the PAW.
I only have the expansions and the necessary mods to run this test.
Had Notes2Log installed as requested and added a note before and after trying to open the camera window. (This doesn't help much as the part is erroring on scene load, not during operation)
The same error occurs when an instance of the part is added within the Ship editor scene.

It's giving an error in the function UnityEngine.Texture2D.Internal_Create within PartCameraModule during OnStart.
Happy to provide an additional logs or testing for you - just let me know when you have time to investigate and I'll be on it

Edited February 12 by cyberKerb

cyberKerb · February 10

This mod is (I think) the only mod that shows multiple external cameras, each within it's own resizable window.

When combined with another LGG mod - AnyRes - which allows me to resize the KSP window across multiple screens, I've been able to create 'this' when the mod was working.

Edited February 11 by cyberKerb

cyberKerb · February 19

Hi @linuxgurugamer, just a ping in case you didn't see the initial log file in the above post.

https://www.dropbox.com/s/545ci28oilowfpw/KSP.log?dl=0

Fresh install of latest KSP version and tried this mod.

The KURS camera mod isn't initialising when added to a scene (flight or VAB)

linuxgurugamer · March 7

On 2/19/2024 at 4:14 PM, cyberKerb said:

Hi @linuxgurugamer, just a ping in case you didn't see the initial log file in the above post.

https://www.dropbox.com/s/545ci28oilowfpw/KSP.log?dl=0

Fresh install of latest KSP version and tried this mod.

The KURS camera mod isn't initialising when added to a scene (flight or VAB)

That's very odd.

I found this in your log file:

[ERR 00:08:15.208] Texture has out of range width / height

[ERR 00:08:15.218] Module PartCameraModule threw during OnStart: UnityEngine.UnityException: Failed to create texture because of invalid parameters.
  at UnityEngine.Texture2D.Internal_Create (UnityEngine.Texture2D mono, System.Int32 w, System.Int32 h, System.Int32 mipCount, UnityEngine.Experimental.Rendering.GraphicsFormat format, UnityEngine.Experimental.Rendering.TextureCreationFlags flags, System.IntPtr nativeTex) [0x00021] in <12e76cd50cc64cf19e759e981cb725af>:0 
  at UnityEngine.Texture2D..ctor (System.Int32 width, System.Int32 height, UnityEngine.TextureFormat textureFormat, System.Int32 mipCount, System.Boolean linear, System.IntPtr nativeTex) [0x0003d] in <12e76cd50cc64cf19e759e981cb725af>:0 
  at UnityEngine.Texture2D..ctor (System.Int32 width, System.Int32 height) [0x00000] in <12e76cd50cc64cf19e759e981cb725af>:0 
  at OLDD_camera.Utils.Util.MonoColorTexture (UnityEngine.Color color, System.Int32 width, System.Int32 height) [0x00000] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Utils.Util.MonoColorVerticalLineTexture (UnityEngine.Color color, System.Int32 size) [0x00000] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Camera.BaseCamera.InitTextures () [0x000e2] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Camera.BaseCamera.DoResizeWindow (System.Int32 WindowSizeCf) [0x00020] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Camera.BaseCamera.LoadWinSettings () [0x00020] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Camera.BaseCamera.InitBaseCamera (Part thisPart, System.Single windowSizeInit, System.String windowLabel, System.Boolean firstTime) [0x00140] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Camera.BaseCamera..ctor (Part thisPart, System.Single windowSizeInit, System.String windowLabel) [0x000d2] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Camera.PartCamera..ctor (Part thisPart, System.String resourceScanning, System.Double electricchargeCost, System.String bulletName, System.Int32 hits, System.String rotatorZ, System.String rotatorY, System.String zoommer, System.Single stepper, System.String cameraName, System.Int32 allowedScanDistance, System.Int32 windowSize, System.Boolean isOnboard, System.Boolean isLookAtMe, System.Boolean isLookAtMeAutoZoom, System.Boolean isFollowMe, System.Boolean isTargetCam, System.Single isFollowMeOffsetX, System.Single isFollowMeOffsetY, System.Single isFollowMeOffsetZ, System.Single targetOffset, System.String restrictShaderTo, System.String windowLabel) [0x00007] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at OLDD_camera.Modules.PartCameraModule.OnStart (PartModule+StartState state) [0x00013] in <2fa12dd90643486eb0a7fee37d0754ba>:0 
  at Part.ModulesOnStart () [0x00120] in <4b449f2841f84227adfaad3149c8fdba>:0

I just loaded the exact same mods into a fresh 1.12.5 install, and didn't get this

But I'd prefer the Player.log, not the KSP.log. It shows things a little differently

Edit: Very important, I need to know how you are starting the game. Please list all the steps and click you do

Edited March 7 by linuxgurugamer

linuxgurugamer · March 7

On 2/19/2024 at 4:14 PM, cyberKerb said:

Hi @linuxgurugamer, just a ping in case you didn't see the initial log file in the above post.

https://www.dropbox.com/s/545ci28oilowfpw/KSP.log?dl=0

Fresh install of latest KSP version and tried this mod.

The KURS camera mod isn't initialising when added to a scene (flight or VAB)

I also need to know your UI settings, specifically the UI Scale

Also, screen resolution, and if you are running in windowed or full screen mode

Edited March 7 by linuxgurugamer

linuxgurugamer · March 7

On 2/19/2024 at 4:14 PM, cyberKerb said:

Hi @linuxgurugamer, just a ping in case you didn't see the initial log file in the above post.

https://www.dropbox.com/s/545ci28oilowfpw/KSP.log?dl=0

Fresh install of latest KSP version and tried this mod.

The KURS camera mod isn't initialising when added to a scene (flight or VAB)

Please try using this debug version:

https://www.dropbox.com/s/m2e679pdemdsjir/DockingCamKURS-Debug-1.3.8.6.zip?dl=0

It has some debugging statements, along with a quick patch to try to bypass the error. I NEED the Player.log so I can fix this permenantly

cyberKerb · March 8

17 hours ago, linuxgurugamer said:

Please try using this debug version:
https://www.dropbox.com/s/m2e679pdemdsjir/DockingCamKURS-Debug-1.3.8.6.zip?dl=0
It has some debugging statements, along with a quick patch to try to bypass the error. I NEED the Player.log so I can fix this permenantly

I also need to know your UI settings, specifically the UI Scale

Also, screen resolution, and if you are running in windowed or full screen mode

But I'd prefer the Player.log, not the KSP.log. It shows things a little differently

Edit: Very important, I need to know how you are starting the game. Please list all the steps and click you do

Thanks @linuxgurugamer

Same as you - I redownload KSP1, debugKURS, Toolbarcontroller, TuxLibrary, Notes2Log & ClickThroughBlocker

I've done a numbers of tests and the results are as follows:

For all program starts
Doubleclick on KSP_x64.exe in Folder (portable version, not steam or package install)

Launch 1 (Confirming you're not crazy - it does work out of the box)
No edit to resolution 1280x720 (Windowed mode) UI Scale is 100% - left all settings as default from fresh install
Created new sandbox game
Clicked VAB, added lander can and onboard camera from parts list, launch
Access camera PAW - Camera Launch (no issues)
Quit

Launch 2 (Re-Confirming you're not crazy - it still works)
Resolution 2560x1440 (Fullscreen mode) UI Scale is 120%
Swapped out KURS-Debug for new download from Spacedock
Added ModuleManager & Squad Expansion
Clicked VAB, added lander can and onboard camera from parts list, launch
Access camera PAW - Camera Launch (no issues)
Quit

Launch 3 (Confirming I'm not crazy - reproduced error)
Resolution 2560x1440 (Fullscreen mode) UI Scale is 120%
Swapped out KURS for KURS from old install
Clicked VAB, added lander can and onboard camera from parts list saw error in console (same as previous log)
Quit

Analysis
Compared installs of KURS, the only difference was the DockingCamera.cfg file under DockingCamKURS\PluginData (mentioned in another users error report)
Clearly the WindowSizeCoef shouldn't be 0 - also looks like the Window position data is in the winXXXX values and not the camWinXXXX values.
No idea what's caused the data to generate in that order (from old installed). Especially weird as the KURS object initialises with WindowSizeCoef = 2.

Below is the KURS generated file (I didn't set it manually) that is the culprit for the error:

DockingCamera
{
	WindowSizeCoef = 0
	winX = 1253
	winY = 341
	winWidth = 306
	winHeight = 210
	camWinX = 0
	camWinY = 0
	camWinWidth = 0
	camWinHeight = 0
}

Many 2-step Launches later trying to get a bad config file to generate:
Steps were:
Launch 1: Delete DockingCamera.cfg, launch under a resolution / window/ full screen instance. Go to launch pad with camera active, quit.
Launch 2: Change resolution to something lower to try and get the config to generate itself into a invalid state that is causing the error.
I kept reviewing the console for errors during part attachment in VAB

Failing at trying to fail
KURS did not fail once during these many attempts. It kept working and I was unable to reproduce the error with a cfg file containing WindowSizeCoef = 0
I suspect there is a mod interaction here and without loading other mods to find it, it's hard to troubleshoot in isolation. (I know, the opposite of what you'd usually want)

From memory, I had a number of IVA mods initially installed (ASET / ALCAR, RPM, maybe hullcam as well) when the KURS mod initially failed.
My normal practice when encountering an error is to strip all mods from the install (in this case, except KURS and it's dependencies) to troubleshoot.
However, in this specific error case, the invalid config was already in existence and continued to error.
In retrospect, a clean reinstall of the mod probably would of fixed it.

Suggested fixes:
If time is short / need to work on other priorities:
(No dev side changes required until known cause of cfg file being corrupted with invalid values)
User Side:
If getting a "Texture has out of range width / height" error during part onStart()
Best to either reinstall mod from ZIP (delete all old files first) or delete file DockingCamKURS\PluginData\DockingCamera.cfg and try mod again before submitting logs

Not sure if my error case is the same as others, but the error message is at least the same.
However, if a few people with the same error is enough to put in a pre-emptive blocker of bad data...
Dev Side: not allow WindowSizeCoef = 0 after reading in the plugin config data.

In the end, I didn't bother to load any log file as all the results were successes with no hint of a problem.
I'll reintroduce KURS into my KSP1 install with all other mods active.

If I see the error again, I'll have a better idea what I'm looking for now that I know it relates to the cfg file
That should allow me to track down what is causing it and report back here.

Edited March 8 by cyberKerb

linuxgurugamer · March 10

@cyberKerb Believe it or not, with what you said, I've just been able to reproduce the error.

I'm wondering if that setting got changed somehow by a rogue MM script, and it then got saved

I'll figure out what's going on and get a fix out soon

Edited March 10 by linuxgurugamer

[1.12.x] Docking Camera KURS Style Re-Adopted (Fixed in 1.9)

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation