Dynamic Engine
  • Starting your engine
    • Introducing Dynamic
    • The simulation
    • The network
  • Your first drive
    • Setting the script
    • Creating a Dynamic vehicle profile
    • Editing a Dynamic vehicle profile
    • Migrating from C.H.A.S.E.R
  • Fine Tuning your vehicle
    • Adapting your NUI
    • Editing the engine
    • Creating engine swap profiles
    • Creating a transmission data
    • Creating tyre profiles
    • Creating a new camera
    • Tweaking HUD
    • Setting Up Performance Index
    • Tuning your vehicle
    • Utilizing offsets
  • Exports
    • Learning the exports
    • Brake Exports
      • getBrakeTemp
      • toggleBrakeDebug
      • setBrakeTemp
  • Caller Exports
    • stopDynamic
    • startDynamic
  • Camera Exports
    • getCameraData
    • getCameraAmmount
    • startCamera
    • swapCamera
    • stopCamera
    • setCurrentCameraPitchOffset
    • setCurrentCameraFovOffset
    • setCurrentCameraSpacingOffset
    • setCurrentFpvCameraSpacingOffset
    • toggleBikeYawCorrection
  • Differential Exports
    • getIsVehicleCurrentlyDrifting
    • getIsVehicleCurrentlyDriftingThrottleLess
  • Drivetrain Exports
    • setFrontTorqueDist
  • Ecu Exports
    • setCurrentVehicleTcsLevel
    • toggleTcs
    • toggleEsc
    • getAssists
    • getTelemetryData
    • getGlobalTelemetryData
    • getWheelData
    • getVehicleData
    • getAvailableTyres
    • getTyreData
    • getAvailableEngineSwaps
    • getEngineData
  • Performance Index Exports
    • getPerformanceIndex
    • getPerformanceIndexCalibrationMetrics
  • Transmission Exports
    • getTopSpeedTable
    • getTopSpeedTableFromTransmissionData
    • setTransmissionMode
    • getTransmissionMode
  • Tuning Exports
    • loadTunedSetup
  • Tyre Exports
    • warmTyre
  • From enthusiasts to everyone
    • With Passion.
Powered by GitBook
On this page
  1. Camera Exports

setCurrentFpvCameraSpacingOffset

setCurrentFpvCameraSpacingOffset(usedOffsetY [Float] , usedOffsetZ [Float] )

Controls the camera offset for both Z and Y axis, exclusively for first person view cameras.

        -- since Lua numbers are passed by value, not reference we need to repeat this inside the func(). Are there better ways to doing this? Yes. But this is just a simple exports demo.
        local usedOffsetY = cameraData.isFpv and camFpvYOffset or camChaseYOffset
        local usedOffsetZ = cameraData.isFpv and camFpvZOffset or camChaseZOffset

        inputContextButton(
            "Y Offset: ",
            "Y Offset",
            "Controls the camera offset on the y axis.",
            0, 10, -10, 0.05,
            usedOffsetY,
            function(val)
                if cameraData.isFpv then 
                    camFpvYOffset = val
                    dynamic:setCurrentFpvCameraSpacingOffset(usedOffsetY, usedOffsetZ) 
                else 
                    camChaseYOffset = val
                    dynamic:setCurrentCameraSpacingOffset(usedOffsetY, usedOffsetZ) 
                end
            end
        )

        inputContextButton(
            "Z Offset: ",
            "Z Offset",
            "Controls the camera offset on the Z axis.",
            0, 10, -10, 0.05,
            usedOffsetZ,
            function(val)
                if cameraData.isFpv then 
                    camFpvZOffset = val
                    dynamic:setCurrentFpvCameraSpacingOffset(usedOffsetY, usedOffsetZ) 
                else 
                    camChaseZOffset = val
                    dynamic:setCurrentCameraSpacingOffset(usedOffsetY, usedOffsetZ) 
                end
            end
        )
PrevioussetCurrentCameraSpacingOffsetNexttoggleBikeYawCorrection