Panzuur

20251027_163053_1.mp4 Almost done with the F6F Trim Controls.....

Ok thanks!

Thanks for the reply, I know I can't save the mission, but I was not able to keep up with the AI in climb-out, So I started snooping around , granted I have about 1 hour experience with Mission Editor, so I know nothing, And the guy who made the missions is a MASTER at it. but I didnt see the afterburner off on the AI planes in the editor, I could add that parameter, but yes I can't save it as you said. So I may be looking in the wrong place for this afterburner setting, Just starting to try and learn the Mission Editor, so I am probably 99.99% wrong. 1st picture is the mission settings as is, 2nd picture shows that I can add the restrict afterburner=on to the waypoint, just again , can't save. But I would like to know if this is the correct location so if I ever can make some missions I can do this. Also I there any good tutorial sites to help learn The Mission Editor?

If I open a miz file and want to disable the AI from using WEP on climbout to altitude, where would this be defined? and how would I check this on campaign files I have bought? Thanks!

I was wondering if the afterburner setting will be set to off in the campaigns? Would this allow us to keep up with the group during climb out? I know i cant edit and save the miz file, but I did look and at least on mission 1 of wolfpack it is not disabled. Thanks for the Great Campaigns!

I watched some YouTube videos and GTFreeFlyer helped me and now I understand, I was 100% wrong in my assumption, I have learned something new which is awesome, Thanks!

Ok, I stand corrected, I do need to research this more, I don't fully understand this.

Technically on a Warbird , the trim moves the trim tabs on the control surfaces, not the control surface itself so when trimming, the tabs move not the control surfaces, thus the stick should not move.

Yea , Just tried it, that works Thanks.

This worked for me to correct the trim moving the stick the opposite it should, hopefully they will fix that the trims should not move the stick at all in the next patch.

I was thinking of starting a Patreon, just haven't looked into it yet, been very busy with many projects ...

Sorry, no I get my drawings from Aircorps Library also, some are not readable at all. Yea all the consoles are 3d printed.

The keybinds for the droppable tank switch do not work, and the clickable cockpit does not allow the switch to goto the release position.

I have a physical trim wheel that turns an encoder, in game the trim wheel moves opposite of the physical trim, My joystick works the elevator correctly, I went into the Default.lua file for joystick input and changed the +/- values for trim nullup and down, they were backwards. picture shows the correct values after fix. it seems to work , i need to test more.

I align it in CAD when I design it, so it's pretty close to correct locations, I've found it does not need to be exact, it does have some adjustability, but being close works just fine. Currently the F6F will be next.

1) How long did it take to build? A bit less than a year, from start to finish, but I just retired so next one should be less. But each one I build I gain experience, and each build is better than the previous, 2) How difficult is it to get into? My simpit is very basic but it is a challenge to my hips and knees. Pretty easy to get into, the sides slide out for easy access. 3) Does than fan sound more like the real Corsair engine than the sim? Lol, currently yes.

Nope, The gauges dials don't function, it could be done but I fly in VR so it's not needed.

I designed and made everything from original factory drawings.

Just Finished my F4U Simpit , programing the inputs, Hopefully the next update will have more button binds included.

If your comfortable editing your Input.lua file you can add these lines to get the rocket box button binds. {down = device_commands.RocketsBox_SwitchCover, cockpit_device_id = devices.WEAPON, value_down = 1.0, name = _('Rocket Box Switch Cover OPEN'), category = _('Weapons')}, {down = device_commands.RocketsBox_SwitchCover, cockpit_device_id = devices.WEAPON, value_down = 0.0, name = _('Rocket Box Switch Cover CLOSED'), category = _('Weapons')}, {down = device_commands.RocketsBox_Switch, cockpit_device_id = devices.WEAPON, value_down = 1.0, name = _('Rocket Box On'), category = _('Weapons')}, {down = device_commands.RocketsBox_Switch, cockpit_device_id = devices.WEAPON, value_down = 0.0, name = _('Rocket Box Off'), category = _('Weapons')}, {down = device_commands.RocketsBox_ArmSafe, cockpit_device_id = devices.WEAPON, value_down = 1.0, name = _('Rocket Box Arm'), category = _('Weapons')}, {down = device_commands.RocketsBox_ArmSafe, cockpit_device_id = devices.WEAPON, value_down = 0.0, name = _('Rocket Box Safe'), category = _('Weapons')}, {down = device_commands.RocketsBox_SingleAuto, cockpit_device_id = devices.WEAPON, value_down = 1.0, name = _('Rocket Box Auto'), category = _('Weapons')}, {down = device_commands.RocketsBox_SingleAuto, cockpit_device_id = devices.WEAPON, value_down = 0.0, name = _('Rocket Box Single'), category = _('Weapons')},

I'm having the same issue, can't access the communication menu. Has anyone else have the issue and a fix, mission 10 next, loving the campaign.

Trying to use Modelviewer 2.0 to view the cockpit models and using free camera mode to move the camera around. The camera movement is very fast, and hard to get the camera located correctly (especially the W and S keys) . Is there a way to manually put in the camera distance number in? or slow down the movement per key press? Thanks.

Took about a year to make, of free time after work or weekends. About the same for the P47 cockpit. Working on the Corsair cockpit now.

I have no issues in VR finding controls, cockpit is 1:1 and everything is located correctly, you look at a switch in VR , reach out and its there, sure you don't see your arm or hand in VR, that really never broke immersion for me. After a bit you really don't think about it, it just works.

Thats what I have been doing So the values I changed were in the code you sent last , the value down was 0.1 and 0.3 , I changed to 0.0 and 0.2. otherwise the cover triggered the switch to goto open and closed. I could not find a 3 way position switch for sale and originals are too expensive so I made my own switch, each position activates a Normally Open micro switch , currently a switch at positions AUTO, OPEN and CLOSED, I have a switch at the Manual Position but thats not available in the default.lua ( maybe I should try to add that Command? that may be the answer. ) and a Normally Open reed switch that triggers when the cover is open. I may look at joystick gremlin , I may be able to make a macro to do what I need. I appreciate your help! , I will get this working eventually .