Please make sure you've installed all of the requirements. You should be able to see each of them being loaded in "red4ext/logs/red4ext.log" (order does not matter): * Input Loader * Mod Settings (optional) * TweakXL * ArchiveXL * Let There Be Flight
For more information on the Cyberpunk 2077 startup process & the errors/crashes that may happen at each stage, see this flowchart.
If you're seeing "REDScript compilation failed", you may need to delete your "r6/cache" folder & re-verify your game files. If the error keeps happening, please upload your "r6/logs/redscript.log" to a website like pastebin.com and link in a comment/post. Do not expect the mod/game to work when this error happens.
To play Let There Be Flight on >2.0 as of the 11/02/2025:
- Uninstall previous versions of Cyberpunk - Find and install Cyberpunk 2.10 (not 2.12, not 2.13, not 2.0) - Install Let There Be Flight's requirements and mod files found on Jack Humbert's GitHub page here. - Install Mod Settings 0.2.3 for 2.10 found on Nexus here.
You should now have a bootable Cyberpunk with functioning Let There Be Flight and Mod Settings.
BUT IT'S NOT ALL, you now need to set a few things up.
- Navigate to and open "Cyberpunk 2077\red4ext\plugins\let_there_be_flight\inputs.xml" with a notepad - Look around the inputs and set up the controls you think would be best
(If at that point you're lost, here are my inputs that I use exclusively with a gamepad and Anti Grav Drone mode, the controls are LS Y = Pitch, LS X = Yaw, RS Y = Lift, RS X = Strafe/Sway, L1 R1 = Roll, L2 R2 = Throttle, select all and copy paste in the said file:
Spoiler:
Show
<?xml version="1.0"?> <bindings> <!-- VEHICLE DRIVE - used when player is mounted as driver and can control vehicle -->
The flight controls are very sensitive at first and you need to disable a few things to make everything ok, so you most likely will need to change the settings, here are mine:
Spoiler:
Show
BUT WAIT! There are a few bugs, some you can fix:
- Unable to see the phone calls on screen (fix: Auto Answer Call) - Erratic audio after 30-40mins of playing (fix: restart the game (with No Intro Videos installed to save time)) - Exploding vehicles (fix: Open "Cyberpunk 2077\red4ext\plugins\let_there_be_flight\packed.reds" with Notepad, search "if biggestImpact" set number above 1.0)
AS FOR OTHER MODS you can get some working, I'd select a date closest to the release of LTBF preview, sort the file sections by version and choose what you need.
Mind you, after a month of having to restart my game every 40 mins, I caved in and started playing on an updated version without Let There Be Flight. I still have a 2.10 version in case I wanna fly but, even though I didn't play for a year cause the mod wasn't updated, I don't regret playing without it now.
It is not compatible with the current version, it's written in huge red letters just above your message ^^
And as with most mods, there is no file to uninstall. You have to delete the files manually (look in the files you've downloaded to see all the files to be deleted) or via Vortex.
I think the reason you get people upset is, yes you explain what version is needed for the mod to work. But you have all of it in the comments and not in the description. So people get the mod and install it following what you have described in the description under installation, find out it doesn't work, then end up in the comments only to find out it indeed doesn't, the dev put the explanation in the comments for people to find later after the fact getting a bunch of in my opinion inflated downloads, then complain when people comment complaining about it.
Either explain it only works on 2.10 in the description or take it down.... Or just keep it the way it is and keep getting frustrated people in your comments.
You're confusing the dev with the people who provide information in the comments. But whatever the case, you should always do your research BEFORE installing a mod. If you don't because you're lazy, fine. But then you definitely shouldn't complain afterward.
Everything here is free, so it would be particularly inappropriate to complain that it's not perfect. Plus, you get help in the comments. You seem to have forgotten that dev have lives, work for free, receive very little recognition, and, above all, have to deal with people who don't care about what they are going through. Rather than complaining, realize how lucky we already are with all these mods.
You're right, but hey... writing 2 lines stating that it's only available on version 2.10 takes about 30 seconds and can save a lot of people wasting download and installation time.
@Fracture17 As I said before: you should always do your research BEFORE installing a mod. If you don't because you're lazy, that's fine. But don't complain afterwards.
The first thing you see is that the mod hasn't been updated for years, and that's already a red flag for such a complex mod. Then you just have to make a minimum of effort and read the pinned comments.
Anyway, many people here have forgotten that mods are completely free, not a service for which you can claim anything. Especially if you're too lazy to read the comments.
Hey! Does anyone know how to get in contact with Jack these days? I'd like to put down a chunk of $$ to commission him for one final Let There Be Flight update, because it's worth the money to me (and a bunch of you, I recon).
But Nexus is telling me he is no longer accepting messages here, and I can't find any email links on his personal website. So, anyone have any leads?
Seriously, I'd considered starting a "Let's all chip in a few bucks for him to get this made" sorta campaign, but I feel like a much more straightforward "I'd love to pay you X dollars in exchange for an update" deal is just the better way to go about it.
If you want it has a very easy-to-find Github page, all you had to do was read the pinnedcomments.
But anyway, if you do a little search in the comments (it takes between 3 and 5 seconds ;-) you'll see right away that you're not at all the first to want to offer money in the belief that it will bring Jack back, but no it won't.
Because JackHumbert, the author, has abandoned this mod, not least because CD Projekt's updates break the mod every time. And since we're not immune to a new update,... I understand perfectly why he refuses to come back to it. In short, we must forget this idea and mourn this mod. Or offer money to another modder who will want to take over. But after several years no one has had the desire/capacity to update this mod. So good luck finding someone motivated ^^
Bro, do yoursellf a favor and read the entire comments page here, from top to bottom. As you should have - apparently trying to run a complex, highly experimental and massively popular mod that hasn't been updated in a while (and 99,99% won't ever).
It's a sad moment if you do read everything (I just did) to land on your post. Come on, bro.... Inconsiderate. Rude. Have some respect for other people (and their time), bro <3 This is not what modding is about either.
3941 comments
Please make sure you've installed all of the requirements. You should be able to see each of them being loaded in "red4ext/logs/red4ext.log" (order does not matter):
* Input Loader
* Mod Settings (optional)
* TweakXL
* ArchiveXL
* Let There Be Flight
For more information on the Cyberpunk 2077 startup process & the errors/crashes that may happen at each stage, see this flowchart.
If you're seeing "REDScript compilation failed", you may need to delete your "r6/cache" folder & re-verify your game files. If the error keeps happening, please upload your "r6/logs/redscript.log" to a website like pastebin.com and link in a comment/post. Do not expect the mod/game to work when this error happens.
If you get the corrupted/missing script error or game crashes, please install CTD Helper and follow this guide to get appropriate information - you can upload this log to pastebin.com as well.
If you think you've encountered a bug, please check the issues on Github before making a comment about it.
Here's a quick demo of the custom FPP camera & Drone mode using a HOSAS setup with Custom Game Controller:
Here's a quick demo of some of the quickhacks introduced in 0.1.4:
- Uninstall previous versions of Cyberpunk
- Find and install Cyberpunk 2.10 (not 2.12, not 2.13, not 2.0)
- Install Let There Be Flight's requirements and mod files found on Jack Humbert's GitHub page here.
- Install Mod Settings 0.2.3 for 2.10 found on Nexus here.
You should now have a bootable Cyberpunk with functioning Let There Be Flight and Mod Settings.
BUT IT'S NOT ALL, you now need to set a few things up.
- Navigate to and open "Cyberpunk 2077\red4ext\plugins\let_there_be_flight\inputs.xml" with a notepad
- Look around the inputs and set up the controls you think would be best
(If at that point you're lost, here are my inputs that I use exclusively with a gamepad and Anti Grav Drone mode, the controls are LS Y = Pitch, LS X = Yaw, RS Y = Lift, RS X = Strafe/Sway, L1 R1 = Roll, L2 R2 = Throttle, select all and copy paste in the said file:
<?xml version="1.0"?>
<bindings>
<!-- VEHICLE DRIVE - used when player is mounted as driver and can control vehicle -->
<context name="VehicleDriveBase" append="true">
<include name="VehicleFlightToggle" />
</context>
<!-- VEHICLE DRIVER COMBAT - used when player is mounted as driver and has weapon equipped -->
<context name="BaseVehicleDriverCombat" append="true">
<include name="VehicleFlightToggle" />
</context>
<!-- VEHICLE COMBAT - used when player is mounted as passenger and has weapon equipped -->
<!-- <context name="VehicleCombat" append="true">
<include name="VehicleFlightToggle" />
</context> -->
<context name="VehicleFlight">
<!-- <include name="CameraMovement" /> -->
<!-- <include name="VisionActions" /> -->
<include name="UIExploration" />
<include name="PhotoMode" />
<include name="QuickLoadAndSave" />
<include name="Items" />
<include name="VehicleFlightToggle" />
<!-- <include name="Combat" /> -->
<!-- <action name="ShootPrimary"map="Flight_Fire1" /> -->
<!-- <action name="ShootSecondary"map="Flight_Fire2" /> -->
<!-- <action name="ShootTertiary"map="Flight_Fire3" /> -->
<!-- <action name="Flight_Trick" map="Flight_Trick" /> -->
<action name="Flight_Options"map="Flight_Options"/>
<action name="Flight_UIToggle"map="Flight_UIToggle"/>
<action name="Flight_RightStickToggle"map="Flight_RightStickToggle"/>
<action name="Flight_ModeSwitchBackward" map="Flight_ModeSwitchBackward"/>
<action name="Flight_ModeSwitchForward"map="Flight_ModeSwitchForward"/>
<action name="Flight_HoodDetach" map="Flight_HoodDetach"/>
<action name="Roll"map="Flight_Roll"/>
<action name="Pitch"map="Flight_Pitch"/>
<!-- <action name="FlightCombat_Toggle" map="FlightCombat_Toggle" /> -->
<action name="UseConsumable"map="UseConsumable_Button" />
<action name="SurgePos"map="Acceleration_Axis" />
<action name="SurgePos"map="Flight_SurgePos" />
<action name="SurgeNeg"map="Deceleration_Axis" />
<action name="SurgeNeg"map="Flight_SurgeNeg" />
<action name="TurnX"map="Flight_Yaw" />
<action name="Yaw"map="Flight_Yaw" />
<action name="Lift" map="Flight_Lift" />
<action name="Sway" map="Flight_Sway" />
<!--action name="LeanFB"map="LeftY_Axis_Vehicle" /-->
<!--action name="RockFB"map="LeftY_Axis_Vehicle_RockFB" /-->
<action name="ToggleVehCamera"map="VehicleCameraToggle" />
<action name="VehicleCameraInverse"map="VehicleCameraInverse_Button"/>
<action name="Exit"map="ExitVehicle_Button" />
<!-- <action name="CycleLights"map="Vehicle_CycleLights" /> -->
<action name="Flight_LinearBrake" map="Flight_LinearBrake" />
<action name="Flight_AngularBrake" map="Flight_AngularBrake" />
<action name="ZoomIn"map="ZoomIn_Button"/>
<action name="ZoomOut"map="ZoomOut_Button"/>
</context>
<context name="VehicleFlightToggle">
<action name="Flight_Toggle" map="Flight_Toggle" />
</context>
<!-- EVENTS -->
<acceptedEvents action="Flight_Options">
<event name="BUTTON_PRESSED" />
<event name="BUTTON_RELEASED" />
</acceptedEvents>
<acceptedEvents action="Flight_Trick">
<event name="BUTTON_PRESSED" />
<event name="BUTTON_RELEASED" />
</acceptedEvents>
<!-- MAPPINGS -->
<mapping name="Flight_Toggle" type="Button">
<button id="IK_Pad_LeftThumb" />
<button id="IK_E" overridableUI="vehicleFlight"/>
</mapping>
<mapping name="Flight_RightStickToggle" type="Button">
<button id="IK_Pad_RightThumb" />
</mapping>
<mapping name="Flight_Options" type="Button">
<button id="IK_Pad_X_SQUARE" />
<button id="IK_R" />
</mapping>
<mapping name="Flight_Trick" type="Button">
<button id="IK_Pad_RightShoulder" />
<button id="IK_3" />
</mapping>
<mapping name="Flight_ModeSwitchBackward" type="Button">
<button id="IK_Pad_DigitLeft" />
</mapping>
<mapping name="Flight_ModeSwitchForward" type="Button">
<button id="IK_Pad_DigitRight" />
<button id="IK_G" />
</mapping>
<mapping name="Flight_HoodDetach" type="Button">
<button id="IK_Joy5" />
</mapping>
<mapping name="Flight_UIToggle" type="Button">
<button id="IK_Pad_DigitUp" />
<button id="IK_Y" />
</mapping>
<mapping name="Flight_Fire1" type="Button">
<!-- <button id="IK_Pad_RightShoulder" /> -->
<button id="IK_LeftMouse" />
<button id="IK_Joy3" />
</mapping>
<mapping name="Flight_Fire2" type="Button">
<button id="IK_Pad_DigitUp" />
<button id="IK_RightMouse" />
<button id="IK_Joy6" />
</mapping>
<mapping name="Flight_LinearBrake" type="Button">
<button id="IK_Pad_A_CROSS" />
<button id="IK_C" />
</mapping>
<mapping name="Flight_AngularBrake" type="Button">
<button id="IK_Pad_A_CROSS" />
<button id="IK_C" />
</mapping>
<mapping name="Flight_SurgePos" type="Axis" >
<button id="IK_JoySlider2" />
<!-- <button id="IK_Joy1" val="0.5" /> -->
<!-- <button id="IK_Joy2" val="2.0" /> -->
</mapping>
<!-- <mapping name="Flight_SurgeNeg" type="Axis" >
<button id="IK_Joy4" val="0.5" />
<button id="IK_Joy5" val="2.0" />
</mapping> -->
<mapping name="Flight_Roll" type="Axis" >
<button id="IK_Pad_RightShoulder" val="1.0" overridableUI="vehicleFlightRollRight"/>
<button id="IK_Pad_LeftShoulder" val="-1.0" overridableUI="vehicleFlightRollLeft"/>
</mapping>
<mapping name="Flight_Pitch" type="Axis" >
<button id="IK_Pad_LeftAxisY" />
<button id="IK_JoyY" />
</mapping>
<mapping name="Flight_Yaw" type="Axis" >
<button id="IK_Pad_LeftAxisX" />
<button id="IK_JoyX" />
</mapping>
<mapping name="Flight_Lift" type="Axis" >
<button id="IK_Pad_RightAxisY" />
<button id="IK_JoyV" />
</mapping>
<mapping name="Flight_Sway" type="Axis" >
<button id="IK_Pad_RightAxisX" />
<button id="IK_Right" val="1.0" overridableUI="vehicleFlightSwayRight"/>
<button id="IK_Left" val="-1.0" overridableUI="vehicleFlightSwayLeft"/>
</mapping>
<!-- PAIRED AXES
<pairedAxes name="RightFlightStick" xAxisMapping="Flight_Sway" yAxisMapping="Flight_Lift" deadzonePreset="Default" />
<pairedAxes name="LeftFlightStick" xAxisMapping="Flight_Roll" yAxisMapping="Flight_Pitch" deadzonePreset="Default" /> -->
</bindings>
The flight controls are very sensitive at first and you need to disable a few things to make everything ok, so you most likely will need to change the settings, here are mine:
BUT WAIT! There are a few bugs, some you can fix:
- Unable to see the phone calls on screen (fix: Auto Answer Call)
- Erratic audio after 30-40mins of playing (fix: restart the game (with No Intro Videos installed to save time))
- Exploding vehicles (fix: Open "Cyberpunk 2077\red4ext\plugins\let_there_be_flight\packed.reds" with Notepad, search "if biggestImpact" set number above 1.0)
AS FOR OTHER MODS you can get some working, I'd select a date closest to the release of LTBF preview, sort the file sections by version and choose what you need.
What a phenomenal game on its own.
__________________
NO THIS MOD DOESN'T WORK ON 2.21
There is no and there will be no further updating of the mod.
The author has abandoned this mod.
And as with most mods, there is no file to uninstall.
You have to delete the files manually (look in the files you've downloaded to see all the files to be deleted) or via Vortex.
Either explain it only works on 2.10 in the description or take it down.... Or just keep it the way it is and keep getting frustrated people in your comments.
Everything here is free, so it would be particularly inappropriate to complain that it's not perfect. Plus, you get help in the comments. You seem to have forgotten that dev have lives, work for free, receive very little recognition, and, above all, have to deal with people who don't care about what they are going through.
Rather than complaining, realize how lucky we already are with all these mods.
Thanks ^^
@Fracture17
As I said before: you should always do your research BEFORE installing a mod. If you don't because you're lazy, that's fine. But don't complain afterwards.
The first thing you see is that the mod hasn't been updated for years, and that's already a red flag for such a complex mod. Then you just have to make a minimum of effort and read the pinned comments.
Anyway, many people here have forgotten that mods are completely free, not a service for which you can claim anything. Especially if you're too lazy to read the comments.
But Nexus is telling me he is no longer accepting messages here, and I can't find any email links on his personal website. So, anyone have any leads?
I WANNA MAKE THIS HAPPEN.
If I can find a way to contact him, at least!
But anyway, if you do a little search in the comments (it takes between 3 and 5 seconds ;-) you'll see right away that you're not at all the first to want to offer money in the belief that it will bring Jack back, but no it won't.
Because JackHumbert, the author, has abandoned this mod, not least because CD Projekt's updates break the mod every time. And since we're not immune to a new update,... I understand perfectly why he refuses to come back to it. In short, we must forget this idea and mourn this mod. Or offer money to another modder who will want to take over. But after several years no one has had the desire/capacity to update this mod. So good luck finding someone motivated ^^
It's a sad moment if you do read everything (I just did) to land on your post. Come on, bro.... Inconsiderate. Rude. Have some respect for other people (and their time), bro <3 This is not what modding is about either.