Jump to content


2.0.3 Camera Development -- file breakdown


  • Please log in to reply
36 replies to this topic

pigeon_kicker #1 Posted 10 February 2018 - 07:46 PM

    Second Lieutenant

  • Open Beta Tester
  • 1493 battles
  • 1,520
  • [SF] SF
  • Member since:
    08-04-2013

Moved from other post, we can work on it here.

Not in a developers posting.

 

With some guess work involved...

 This is the start of ALL of the 10 different camera scales, each has a unique  ID name

<camera>
<id>camera_assault</id>
<minMouseCombatFov>90</minMouseCombatFov>
<maxFov>150</maxFov>
<minFov>90</minFov>

I do believe this is the location of the recticle
<targetCamPos>0 30.2 -30.0</targetCamPos>
<targetCamSpeed>5.0</targetCamSpeed>

I think that this is where you can adjust the scale of the ingame slider, so not 0 to 10, but 0 to 6

<camSpeedYawPitch>6.0</camSpeedYawPitch>

<camSpeedRoll>6.0</camSpeedRoll>
I think you can raise the below 3 up to 1000 max
<camSniperSpeedYawPitch>500</camSniperSpeedYawPitch>
<camSniperSpeedRoll>500</camSniperSpeedRoll>
<camSniperSpeedTarget>500</camSniperSpeedTarget>

These are for the Side, front, back, top, and bottom camera positions that are used by gamepads and joysticks, the HUD switch

<backCamPos>0 2 -2</backCamPos>

<backCamSpeed>7.0</backCamSpeed>
<backTargetCamSpeed>7.0</backTargetCamSpeed>
<backCamFov>90</backCamFov>
<rearViewCamPos>0 0 -10</rearViewCamPos>
<rearViewCamDir>0 22.0 -350</rearViewCamDir>
<rearViewCamFov>90</rearViewCamFov>
<leftCamPos>15 2 0</leftCamPos>
<leftCamDir>-15 2 0.1</leftCamDir>
<rightCamPos>-15 2 0</rightCamPos>
<rightCamDir>15 2 0.1</rightCamDir>
<topCamPos>0 -15 -0.1</topCamPos>
<topCamDir>0 0 4</topCamDir>
<bottomCamPos>0 15 -0.1</bottomCamPos>
<bottomCamDir>0 0 4</bottomCamDir>

Defines Max and Min for distance from aircraft center point

<pivotDistMax>150</pivotDistMax>

<pivotDistMin>90</pivotDistMin>

Free Cam Min and Max definitions

<freeCamDistHalflife>0.06</freeCamDistHalflife>

<freeCamFovNear>90</freeCamFovNear>
<freeCamFovFar>150</freeCamFovFar>

<normalCamInterpolationTime>0.2</normalCamInterpolationTime>

<freeCamInterpolationTime>0.2</freeCamInterpolationTime>
<freeCamFovInterpolationTime>0.2</freeCamFovInterpolationTime>
<freeCamZoomFactor>0.01</freeCamZoomFactor>
<backCamInterpolationTime>0.0</backCamInterpolationTime>
<bombCamInterpolationTime>0.3</bombCamInterpolationTime>
<sideCamInterpolationTime>0.05</sideCamInterpolationTime>
<sideCamJInterpolationStartTime>1.0</sideCamJInterpolationStartTime>
<sideCamJInterpolationEndTime>1.0</sideCamJInterpolationEndTime>
<sideCamJInterpolationTimeTransitionTerm>0.02</sideCamJInterpolationTimeTransitionTerm>
<spectatorCamInterpolationTime>0.0</spectatorCamInterpolationTime>
<targetCamInterpolationTime>0.2</targetCamInterpolationTime>
<freeFixableCamInterpolationTime>0.2</freeFixableCamInterpolationTime>
<freeFixableCamSpeed>0.2</freeFixableCamSpeed>

After death camera settings, like an increased or decreased spin, twist, point of view angle, POV distance both before and after you crash into the worm garden...

<destroyedFall>

      <stateInterpolationTime>0.5</stateInterpolationTime>
      <animationNeedTime>10.0</animationNeedTime>
      <animationStartTime>3.0</animationStartTime>
      <animationPitch>30</animationPitch>
      <animationYaw>25.0</animationYaw>
      <animationPitchClockwise>true</animationPitchClockwise>
      <animationYawClockwise>True</animationYawClockwise>
      <animationDistance>150.0</animationDistance>
      <animationTime>6.0</animationTime>
      <animationFov>150.0</animationFov>
      <animationFadeInTime>1.0</animationFadeInTime>
      <animationFadeOutTime>1.0</animationFadeOutTime>
      <animationGroundNeedTime>5.0</animationGroundNeedTime>
      <animationGroundTime>4.0</animationGroundTime>
      <animationGroundFov>5.0</animationGroundFov>
      <animationGroundSpawnRadius>1000.0</animationGroundSpawnRadius>
      <animationGroundHeight>50.0</animationGroundHeight>
    </destroyedFall>
<destroyedLanded>
      <stateInterpolationTime>0.0</stateInterpolationTime>
      <fov>150.0</fov>
      <pitch>45.0</pitch>
      <pitchMin>25.0</pitchMin>
      <yaw>30.0</yaw>
      <rotationSpeed>1.2</rotationSpeed>
      <distance>150.0</distance>
    </destroyedLanded>

 


If you want to make god laugh, tell him about your plans for survival..

Lead developer for the NACCW web site. Author of the Pigeon Pak Mod Installer

www.team-sf.com

 

 


pigeon_kicker #2 Posted 10 February 2018 - 07:48 PM

    Second Lieutenant

  • Open Beta Tester
  • 1493 battles
  • 1,520
  • [SF] SF
  • Member since:
    08-04-2013

Pigeon Pak 6-test setup

Here is my camera test mod, please be aware that i am tuning it still, But it is close to my original one.

View Postmnbv_fockewulfe, on 10 February 2018 - 11:30 AM, said:

 

Sorry, but cockpit view is currently broken, unless you found a way to fix it? :hiding:

 

Have no fear, PK is here.

I am making a video explaining the different sections of the camera file, and how to decipher it.

A while back i was on the brink of releasing my CameraTuner mod with the Pigeon Pak.

 

BUT, thank you wargaming i had to redo it.

Not really a bad thing after i looked at the changes, the math is easier, and you have less variables that need changing, it is actually a better and easier way to tune it.

There are 10 total sections in the .xml file, and it is DEcompressed.

These sections id's refer to the size and type of aircraft, You don't want to use the view from a big ole heavy with a tiny biplane do ya ?

Sample of the first ID settings

 

<!--pigeon_pak_camera-->
<!--Version_for_wowp_2_0_3-->
<!--CM-PK005_PT1-->
 <camera>
<id> camera01 </id>
<minMouseCombatFov> 90 </minMouseCombatFov>
<maxFov> 150 </maxFov>
<minFov> 90 </minFov>
<targetCamPos>0 30.2 -30.0</targetCamPos>
<targetCamSpeed>5.0</targetCamSpeed>
<camSpeedYawPitch>6.0</camSpeedYawPitch>
<camSpeedRoll>6.0</camSpeedRoll>

 

Each of these id's have 7 zoom tables as shown below

Zoom table example

 

      <zoomPreset>
        <id> directSniper </id>
        <normalZoomData>
          <position>0 11 -8</position>
          <fovPercent>0.5</fovPercent>
          <angle>0.0</angle>
          <hideModel> 1 </hideModel>
        </normalZoomData>
        <sniperZoomData>
          <position>0 8 -4</position>
          <fovPercent>0.5</fovPercent>
          <angle>0.0</angle>
          <hideModel> 1 </hideModel>
        </sniperZoomData>
      </zoomPreset>
 

 

So, when you break it down each firing selection available in game has 2 available set points. Again below.

Single camera position example for sniper view

 

       <id> directSniper </id>
        <normalZoomData>
          <position>0 11 -8</position>

 

Those 3 numbers tell the system where to position the camera on an X, Y, Z system.

  • 1st of the 3 is for Left and Right of center
  • 2nd is Above and Below center, A negative number is UNDER or BELOW center
  • 3rd is Forward or Backward from the center, negative number is behind the plane.

 

The other three available settings

 

          <fovPercent>0.5</fovPercent>
          <angle>0.0</angle>
          <hideModel> 1 </hideModel>

 

FOV is Field Of View, 1 to 0 scale, 0 being nill.

Angle points the camera view up or down, A negative number shifts it UP.

Hide Model is a 0 or 1 selection, use a 0 to view and a 1 to hide your aircraft model from view, such as a close zoom.

If you don't hide it you will see the framework inside the plane.

This is one of the cockpit view mod needs to be changed thing.

 

I hope this will help out some of you to decipher the file and create your own camera mod.

BTW the file is 2,168 lines long. ALWAYS, make a backup, then a backup of that,

What i am telling you is that it will literally be impossible to find a missing colon or slash in the code lines.

Have a blast editing it, use Notepad++, easy and works right out of the box, and its free.

GET NOTEPAD++

Pigeon Pak 6-test setup

PK


If you want to make god laugh, tell him about your plans for survival..

Lead developer for the NACCW web site. Author of the Pigeon Pak Mod Installer

www.team-sf.com

 

 


Catch21 #3 Posted 10 February 2018 - 07:55 PM

    Senior Master Sergeant

  • Closed Beta Tester
  • 2631 battles
  • 374
  • [DOG5] DOG5
  • Member since:
    05-19-2013
Just to confirm (from my Qs here), is the file you're referencing aircraft_camera_presets.xml, which some modders have changed for FoV and other setting already (goes in res_mods\2.0.x.x\scripts\db)?

pigeon_kicker #4 Posted 10 February 2018 - 07:56 PM

    Second Lieutenant

  • Open Beta Tester
  • 1493 battles
  • 1,520
  • [SF] SF
  • Member since:
    08-04-2013

View PostCatch21, on 10 February 2018 - 02:55 PM, said:

Just to confirm (from my Qs here), is the file you're referencing aircraft_camera_presets.xml, which some modders have changed for FoV and other setting already (goes in res_mods\2.0.x.x\scripts\db)?

 

YES

 

EDIT: Dont forget to include a BLANK "cacheddb.bin" file to wipe the old settings out.

 


Edited by pigeon_kicker, 10 February 2018 - 07:58 PM.

If you want to make god laugh, tell him about your plans for survival..

Lead developer for the NACCW web site. Author of the Pigeon Pak Mod Installer

www.team-sf.com

 

 


hawkeyededic #5 Posted 10 February 2018 - 08:40 PM

    Resident Researcher

  • -Community Ace-
  • 962 battles
  • 2,035
  • [WG-CA] WG-CA
  • Member since:
    10-05-2012

View Postpigeon_kicker, on 10 February 2018 - 01:56 PM, said:

 

YES

 

EDIT: Dont forget to include a BLANK "cacheddb.bin" file to wipe the old settings out.

 

 

Just a note, I have found that sometimes a blank cacheddb.bin file isn't enough, you will still need to delete or rename the origianl as well.


 

Hawkeye's Hangar, your one stop spot for all my repaints. Like me on Facebook for news, updates and more.


mnbv_fockewulfe #6 Posted 10 February 2018 - 11:39 PM

    Captain

  • Member
  • 254 battles
  • 3,101
  • [3NIC] 3NIC
  • Member since:
    12-06-2013

You should ask GP to pin this.

 

You said you need complex software in order to decode the xml files from the binary code they are in.

Do you have the proper software other than WoT tools to decode the camera_effects.xml file? 

if you try to use WoT tools, you get this message


Be sure to check your logic privileges before posting on the forum.

 

mnbv_fockewulfe.png


 


Catch21 #7 Posted 10 February 2018 - 11:55 PM

    Senior Master Sergeant

  • Closed Beta Tester
  • 2631 battles
  • 374
  • [DOG5] DOG5
  • Member since:
    05-19-2013
When I use the tool I mention here (wottools 0.5.3 multy.exe), I can decompile and save (elsewhere) no problems.

mnbv_fockewulfe #8 Posted 11 February 2018 - 12:51 AM

    Captain

  • Member
  • 254 battles
  • 3,101
  • [3NIC] 3NIC
  • Member since:
    12-06-2013

Thank you thank you thank you!

I could just see it and I had no way to get to it, and you sir, just helped restore the cockpit view mod (early celebration) and deserve an honorable mention.:medal::medal::medal::honoring:


Be sure to check your logic privileges before posting on the forum.

 

mnbv_fockewulfe.png


 


mnbv_fockewulfe #9 Posted 11 February 2018 - 01:38 AM

    Captain

  • Member
  • 254 battles
  • 3,101
  • [3NIC] 3NIC
  • Member since:
    12-06-2013

No success as of yet, I'd give it another 3 hours of work or so before I find the cause of it.

hmm...as far as I can tell, the zoom affect is not tied to a particular axis, as when I try to eliminate anything in the z axis nothing works and when using the hat switch the zoom affect still happens even when looking to the right or left.:unsure:


Edited by mnbv_fockewulfe, 11 February 2018 - 01:57 AM.

Be sure to check your logic privileges before posting on the forum.

 

mnbv_fockewulfe.png


 


Catch21 #10 Posted 11 February 2018 - 02:42 AM

    Senior Master Sergeant

  • Closed Beta Tester
  • 2631 battles
  • 374
  • [DOG5] DOG5
  • Member since:
    05-19-2013

View Postmnbv_fockewulfe, on 11 February 2018 - 12:51 AM, said:

Thank you thank you thank you!

View Postmnbv_fockewulfe, on 11 February 2018 - 01:38 AM, said:

Hmm...as far as I can tell, the zoom affect is not tied to a particular axis, as when I try to eliminate anything in the z axis nothing works and when using the hat switch the zoom affect still happens even when looking to the right or left.

 

You're welcome, I get a lot of help here, so nice to give a little back. Just to merge in from another thread I started before I saw this one posted a couple of minutes later:

 

Is there any way to set sniper mode zoom settings so they are stepped, rather than going just from normal to sniper mode- similar to the zoom steps you can use in World of Tanks? 

 

Just guessing, but possibly in aircraft_camera_presets.xml, which some modders have changed for FoV and other setting already (goes in res_mods\2.0.x.x\scripts\db)?

 

There's a zoomTable section in there, but just on the off chance someone has been there/done that already, so I'm not reinventing the wheel here (or going down a blind alley).

 

I think (judging from your post above) you're looking in camera_effects.xml, but for all I know could be either or neither.

 

Any help/pointers appreciated.

 



mnbv_fockewulfe #11 Posted 11 February 2018 - 02:58 AM

    Captain

  • Member
  • 254 battles
  • 3,101
  • [3NIC] 3NIC
  • Member since:
    12-06-2013

I was able to "accidently" get two steps for sniper view by editing these presets:

  <id> directSniper </id>

and

 <sniperZoomData>

to have different values. It also requires a fine touch on the mouse wheel to scroll slowly enough to see the difference, not exactly a reliable method.

The "stepping" of the camera is controlled by a .pyc file and I don't know if anyone here has any experience or knowledge about how to mod it.


Be sure to check your logic privileges before posting on the forum.

 

mnbv_fockewulfe.png


 


pigeon_kicker #12 Posted 11 February 2018 - 06:30 AM

    Second Lieutenant

  • Open Beta Tester
  • 1493 battles
  • 1,520
  • [SF] SF
  • Member since:
    08-04-2013

View Posthawkeyededic, on 10 February 2018 - 03:40 PM, said:

 

Just a note, I have found that sometimes a blank cacheddb.bin file isn't enough, you will still need to delete or rename the origianl as well.

 

Wargaming corrected this issue.

 

Now to "Reset" the game files, you need only click the little arrow next to the play button of the game launcher.

Then click on Run game and clear all cached data.

This will force the game into a state that does this for you.

The game will then rebuild the cached data using the up to date mods.

 

PK


If you want to make god laugh, tell him about your plans for survival..

Lead developer for the NACCW web site. Author of the Pigeon Pak Mod Installer

www.team-sf.com

 

 


pigeon_kicker #13 Posted 11 February 2018 - 07:39 AM

    Second Lieutenant

  • Open Beta Tester
  • 1493 battles
  • 1,520
  • [SF] SF
  • Member since:
    08-04-2013

View Postmnbv_fockewulfe, on 10 February 2018 - 09:58 PM, said:

I was able to "accidently" get two steps for sniper view by editing these presets:

  <id> directSniper </id>

and

 <sniperZoomData>

to have different values. It also requires a fine touch on the mouse wheel to scroll slowly enough to see the difference, not exactly a reliable method.

The "stepping" of the camera is controlled by a .pyc file and I don't know if anyone here has any experience or knowledge about how to mod it.

 

The main thing to remember is that you are using the primary values from the camera ID settings normally.

 

The other settings below the main settings are the Firing position settings.


If you want to make god laugh, tell him about your plans for survival..

Lead developer for the NACCW web site. Author of the Pigeon Pak Mod Installer

www.team-sf.com

 

 


pigeon_kicker #14 Posted 11 February 2018 - 09:28 AM

    Second Lieutenant

  • Open Beta Tester
  • 1493 battles
  • 1,520
  • [SF] SF
  • Member since:
    08-04-2013

I think that i found the solution to the cockpit view camera.

In the C:\Games\World_of_Warplanes\res\scripts\db\curves folder there are two XML files.

  • camera_duration_from_speed.xml
  • camera_position_from_speed.xml

 

They are short compressed .xml files. you will need the WoT tool to extract, then put them into the res_mods folder in the same spot.

Hope it helps

 

PK

 


Edited by pigeon_kicker, 11 February 2018 - 09:29 AM.

If you want to make god laugh, tell him about your plans for survival..

Lead developer for the NACCW web site. Author of the Pigeon Pak Mod Installer

www.team-sf.com

 

 


Catch21 #15 Posted 11 February 2018 - 10:28 AM

    Senior Master Sergeant

  • Closed Beta Tester
  • 2631 battles
  • 374
  • [DOG5] DOG5
  • Member since:
    05-19-2013

View Postmnbv_fockewulfe, on 11 February 2018 - 02:58 AM, said:

I was able to "accidentaly" get two steps for sniper view by editing these presets:   <id> directSniper </id> and  <sniperZoomData> to have different values. It also requires a fine touch on the mouse wheel to scroll slowly enough to see the difference, not exactly a reliable method.

The "stepping" of the camera is controlled by a .pyc file and I don't know if anyone here has any experience or knowledge about how to mod it.

Would you have an example with file name (not sure which file you're referencing here (presets or effects or another) I could insert/modify and try as a starting point? We could maybe then compare notes?

 

There are ways to decompile pyc files, but in this context (tinkering with WoP source code) I wouldn't recommend it.



mnbv_fockewulfe #16 Posted 11 February 2018 - 03:32 PM

    Captain

  • Member
  • 254 battles
  • 3,101
  • [3NIC] 3NIC
  • Member since:
    12-06-2013

View Postpigeon_kicker, on 11 February 2018 - 09:28 AM, said:

I think that i found the solution to the cockpit view camera.

In the C:\Games\World_of_Warplanes\res\scripts\db\curves folder there are two XML files.

  • camera_duration_from_speed.xml
  • camera_position_from_speed.xml

 

They are short compressed .xml files. you will need the WoT tool to extract, then put them into the res_mods folder in the same spot.

Hope it helps

 

PK

 

 

Thanks, I'll check these out.

Catch21,

I'll go in more depth later, I'm on a mobile atm.


Edited by mnbv_fockewulfe, 11 February 2018 - 05:18 PM.

Be sure to check your logic privileges before posting on the forum.

 

mnbv_fockewulfe.png


 


arasgrandpa #17 Posted 11 February 2018 - 06:02 PM

    Senior Master Sergeant

  • Closed Beta Tester
  • 3456 battles
  • 145
  • [-ES-] -ES-
  • Member since:
    01-26-2012
Here is a link to WoT XML Viewer.  I use it instead of WoT Tools.  It has color highlighting and a makes it easier to follow and read.  I then save it back unecrypted and use Notepad ++ to do my search and replace.

mnbv_fockewulfe #18 Posted 11 February 2018 - 07:31 PM

    Captain

  • Member
  • 254 battles
  • 3,101
  • [3NIC] 3NIC
  • Member since:
    12-06-2013

View PostCatch21, on 11 February 2018 - 10:28 AM, said:

Would you have an example with file name (not sure which file you're referencing here (presets or effects or another) I could insert/modify and try as a starting point? We could maybe then compare notes?

 

There are ways to decompile pyc files, but in this context (tinkering with WoP source code) I wouldn't recommend it.

 

View Postmnbv_fockewulfe, on 11 February 2018 - 02:58 AM, said:

I was able to "accidently" get two steps for sniper view by editing these presets:

  <id> directSniper </id>

and

 <sniperZoomData>

to have different values. It also requires a fine touch on the mouse wheel to scroll slowly enough to see the difference, not exactly a reliable method.

The "stepping" of the camera is controlled by a .pyc file and I don't know if anyone here has any experience or knowledge about how to mod it.

 

 

 

The above code is from the aircraft_camera_presets.xml.

The one I'm specifically thinking of is the file camera.pyc

The "stepping" of he camera is referenced by other files like the prefences.xml, but as far as I know these functions are defunct and only the camera.pyc actually controls it anymore.

I have a decompiler that works, I was able to compare the old camera.pyc to the new one to figure out the stuff I was previously talking about.

The organization is completely changed, but the basic lines that deal with the stepping of the camera are the same. I don't know if it's only a matter of switching out the new for the old in that one bit of coding.

Give me a bit and I'll find exactly where it is.


Be sure to check your logic privileges before posting on the forum.

 

mnbv_fockewulfe.png


 


Zapperguy #19 Posted 11 February 2018 - 08:35 PM

    First Lieutenant

  • Closed Beta Tester
  • 63 battles
  • 2,820
  • [CLOWN] CLOWN
  • Member since:
    04-04-2012

All modders should "follow" this topic. Some good stuff is already laid out, and mnbv_fockewulfe seems close to cracking some more camera code.

The sad part is that many players are dissatisfied with the default camera and WG doesn't care. It takes a community of dedicated end users to fix the devs mistakes.

:honoring:

 



mnbv_fockewulfe #20 Posted 11 February 2018 - 09:24 PM

    Captain

  • Member
  • 254 battles
  • 3,101
  • [3NIC] 3NIC
  • Member since:
    12-06-2013

Just gonna put here some of today's findings/ red is changes I made.

Camera effects can be turned off by editing this file: World_of_Warplanes_NA/res/scripts/db/preferences.xml

<cameraEffectsEnabled> false </cameraEffectsEnabled>

this will turn off shaking of the due to ramming, flying close to another plane, firing the guns, being close to aa etc. But it does not turn off the effects of the "speed zoom".

Also in that file are these lines:

<cameraZoomType> zoomTableAlt </cameraZoomType>

<camZoomIndex> 1 </camZoomIndex>

these appear to be hold overs based on the incorrect info they display


 

As far as I can tell, editing anything in /res/scripts/db/camera_effects.xml

yielded no results.

the .pyc files that appear to deal with the camera are (green is important):

/res/scripts/client/

Camera

CameraEffect

CameraStates

CameraStatesEffectsController

CameraStatesEffectsSettings

CameraStrategyLegacyProxy

CameraZoomStatsCollector

/res/scripts/common/

CameraEffectsSettings

/res/scripts/common/db/

DBCamera

DBCameraEffects

/res/scripts/common/ComponentModel

CameraComponents


 

in

/res/scripts/client/

Camera

 

stuff that looks like it might be important:


 

cameraStatesWithZoom = [CameraState.MouseCombat,
 CameraState.GamepadCombat,
 CameraState.MouseAssault,
 CameraState.NormalCombat,
 CameraState.NormalAssault,
 CameraState.JoystickCombat,
 CameraState.JoystickAssault,
 CameraState.Bomber,
 CameraState.Gunner,
 CameraState.Sniper,
 CameraState.JoystickSniper]

class ZoomStates:
    Normal = 1
    Sniper = 2


 

------------------------------------------

def __init__(self):
        LOG_DEBUG('Camera constructor')
        super(Camera, self).__init__()
        self.__createEvents()
        self.__createMatrices()
        self.__cameraStateMachine = BattleCameraStateMachine()
        self.__zoomDataPosition = Math.Vector3(0, 0, 0)
        self.__inputState = None
        self.__inputBattleMode = BATTLE_MODE.COMBAT_MODE
        self.__updateZoomCallback = None
        self.__modelVisible = True
        self.__backToCurrentZoomDataIdx = None
        self.__isZoomEnable = True
        self.__isSniperModeEnable = True
        self.__bombingPrevZoomDataIdx = CAMERA_DEFAULT_BOMBING_IDX + 1
        self.__altMode = False
        self.__effectFOV = 1.0
        self.__context = None
        self.__targetEntity = None
        self.__curZoomState = ZoomStates.Normal
        self.setEffectsEnabled(Settings.g_instance.cameraEffectsEnabled)
        self.__sniperOnZoomDataIdx = None
        self.__inputToCamState = inputToCamState
        self.__curZoomPreset = CAMERA_ZOOM_PRESET.DEFAULT
        self.setMaxMouseCombatFov(Settings.g_instance.maxMouseCombatFov)
        self.__cbOutro = None
        self.__cinematicStarted = False
        self.__cursorLocked = False
        self.__preintroStopped = False
        self.__preintroFinished = False
        self.__cinematicPlayed = False
        self.__isInOverview = False
        return

------------------------------------------------------------------

there's a lot of stuff in it and I have no idea what changing on anything here would result in.


 

 


 


 


 


Be sure to check your logic privileges before posting on the forum.

 

mnbv_fockewulfe.png


 





1 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users