

Bullant
Members-
Posts
622 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Bullant
-
Final (for now) version uploaded. Can't see that there should need to be many changes from this point forward.
-
DCS-BIOS F/A-18C library. Get it here!
Bullant replied to Bullant's topic in Controller Questions and Bugs
Final (for now) version updated. All switches except the static air source switch are working. Only other issue is that there is no export for the top fuel display line in the IFEI when in time set mode. Enjoy, and let me know if you spot anything that doesn't work. -
DCS-BIOS F/A-18C library. Get it here!
Bullant replied to Bullant's topic in Controller Questions and Bugs
Good news. I have fixed the input settings for the Standby Attitude Indicator and RADALT. And with some great help from the awesome Capt Zeen I have added outputs for all of the analog outputs (servos) as well as the UFC and IFEI. There are a couple of analog outputs that are causing issues, so it will be tomorrow before I upload the (for now) final version. -
It's called early access for a reason.
-
Yep aware of all of those, new version updated and every switch except for HUD VIDEO and FLIR is working with my new custom code ... even Eject :) New version uploaded. I have completely reworked the control groupings so that it matches the layout in the NATOPS manual and so that controls/indicators etc are grouped by panel. This has resulted in renaming quite a few controls, so sorry for anyone who already has sketches made up. But I won't be changing them any more. I've got some info from Capt Zeen to set me on the right path, and the next step is to get the other (non indicator) outputs working.
-
DCS-BIOS F/A-18C library. Get it here!
Bullant replied to Bullant's topic in Controller Questions and Bugs
New version uploaded. I have completely reworked the control groupings so that it matches the layout in the NATOPS manual and so that controls/indicators etc are grouped by panel. I have written extensive custom code to handle non-standard buttons like the weird toggles and spring loaded switches, even got the eject switch to actually eject after calling it just once. I've got some info from Capt Zeen to set me on the right path, and the next step is to get the other (non indicator) outputs working. -
OK I have written custom lua code to fix every button other than the HUD VIDEO and FLIR switches, these appear to be broken badly inside the module code and do not respond to commands the way they should. I will attempt to log a bug for them and hopefully they will be fixed in a future release. I have NOT updated the archive in the first post, I am going to complete the reorganisation into panel groups tomorrow and then I will update it.
-
Anyone good at writing LUA code? I have a problem with the Hornet emergency/parking brake handle rotation. You would expect it to return a value of 0 or 1 based on all the other 2 position "switches" in the aircraft, but it actually returns 1 for Emergency and 2 for Parking. It also has two command parameters, which is more like a rocker than a 2 position switch. This does not fit into any of the existing switch/control definition so I am trying to write one specifically for it. I based it on the Rocker template, and have this so far. But it doesn't work ... edit: fixed it. Guess I can add lua to my list of know languages ;) function defineEmergencyParkingBrake(msg, device_id, emergency_command, park_command, arg_number, category, description) local alloc = moduleBeingDefined.memoryMap:allocateInt{ maxValue = 1 } moduleBeingDefined.exportHooks[#moduleBeingDefined.exportHooks+1] = function(dev0) if dev0:get_argument_value(arg_number) < 0.5 then alloc:setValue(0) else alloc:setValue(1) end end document { identifier = msg, category = category, description = description, control_type = "emergency_parking_brake", inputs = { { interface = "set_state", max_value = 1, description = "set the switch position -- 0 = emergency, 1 = parking" } }, outputs = { { ["type"] = "integer", suffix = "", address = alloc.address, mask = alloc.mask, shift_by = alloc.shiftBy, max_value = 1, description = "switch position -- 0 = emergency, 1 = parking" } } } moduleBeingDefined.inputProcessors[msg] = function(toState) local dev = GetDevice(device_id) local fromState = GetDevice(0):get_argument_value(arg_number) if fromState > 0.5 then fromState = 1 end if fromState == 0 and toState == "1" then dev:performClickableAction(park_command, 0) dev:performClickableAction(park_command, 1) dev:performClickableAction(park_command, 0) elseif fromState == 1 and toState == "0" then dev:performClickableAction(emergency_command, 0) dev:performClickableAction(emergency_command, 1) dev:performClickableAction(emergency_command, 0) end end end
-
Yes they have added a lot of new switch types, and a lot of my time was spent looking into those definitions to see what changes I needed to make in the dcs-bios settings to work with the new changes. To be honest most of them are simply changing things like the switch sounds so it doesn't really matter for dcs-bios's purposes. Thanks for doing that testing. Did you have the latest version of the files, because the errors you are seeing in those 3 positions switches tells me that you probably aren't (they were fixed in the last update). I will look into the other switches though, I tested them all using the dcs-bios live view and they worked there but there is a possibility that real switches work differently. So thanks again for saving me the effort of testing them all with real switches.
-
DCS-BIOS F/A-18C library. Get it here!
Bullant replied to Bullant's topic in Controller Questions and Bugs
Not yet, just waiting to hear back from Capt Zeen, I am sure he will set me on the right path for getting the output values. -
DCS-BIOS F/A-18C library. Get it here!
Bullant replied to Bullant's topic in Controller Questions and Bugs
Before anyone dives too far into using the current files ... coming up next I am reorganising all of the entries so they are broken down by panel in the aircraft rather than the sometimes confusing way they are at the moment which is based on the layout in the module's configuration files. -
DCS-BIOS F/A-18C library. Get it here!
Bullant replied to Bullant's topic in Controller Questions and Bugs
Yes and know. Some of them are magnetically held, others are simply spring loaded and return to center as soon as you let go of them. In the hornet module controls they are all currently defined the same. Hopefully they will include parameters to tell us when a magnetically held switch is held in position or not allowed into a position like they currently do in the A10 in a future build. The important thing is that these three way switches weren't working in my original version but they are now :) Thanks, that is greatly appreciated. -
DCS-BIOS F/A-18C library. Get it here!
Bullant replied to Bullant's topic in Controller Questions and Bugs
New version uploaded. All of the 3 way springloaded switches were functioning incorrectly, I have fixed all of them except for the MC switch which stubbornly refuses to work. So at this point every switch works in the cockpit except for: MC Switch Launch Bar Hook Bypass -
Thanks mate, yes a ton of work but someone had to do it. Now I can start building prototype panels at full speed :) And yeah, not sure what happened to the rep system ...
-
DCS-BIOS F/A-18C library. Get it here!
Bullant replied to Bullant's topic in Controller Questions and Bugs
The control reference should auto-generate the first time you start a mission with a Hornet ... but I have updated the zip file to contain the generated files so that the control reference works right from the start. edit: was missing an important file. Updated the zip again, should all be good now. -
The json files will generate automatically once you launch a mission with the F18. But I've updated the zip file to contain the json files. edit: need sleep. I missed the updated AircraftList.lua file, zip file updated again, will definitely work now.
-
And I am done. For now. You can grab a copy of the profile here
-
While everyone else has been flying it, I have spent the last couple of days building a library for the F/A18C for DCS-BIOS, in the hopes of one day getting my pit built. Until I can get in contact with Ian to get it rolled into an official build of DCS-BIOS, I've attached the files for anyone who wants to try it out. Simply extract the zip file into your Saved Games\DCS.openbeta\Scripts\DCS-BIOS folder overwriting when asked. The only things that I am aware are missing at the moment (due to limitations in the hornet module which I am sure will be fixed as development progresses): 1. An input for static source switch (switch does not appear to be currently implemented in the cockpit) 2. An input for fan test switch (switch does not appear to be currently implemented in the cockpit) 3. An export for the top fuel total line when the IFEI is in time set mode 4. An export for the engine nozzle positions on the IFEI Final disclaimer: This is a beta module, things will change and this will likely break this library. I will try and keep on top of updating it as the Hornet gets updated. All I ask is that if you find something that doesn't work, please let me know. Even better, if you figure out how to fix it let me know that as well so I can roll it into the final version. edit 7th June - I have completed the initial version, please let me know if you find anything that doesn't work as expected. This has been tested with the latest 2.5.2.18307 build. note 13th June - I have discovered that I forgot to include updated json files in the latest package. No problem, they will auto-generate with every flight, so just go fly a mission. Will include updated files in next version. update: 1st October - Updated to v0.6 supporting Beta 2.5.3.22176 update: 9th November 2018 - Updated to v0.7 supporting Beta 2.5.3.23788 update: 12th November 2018 - Updated to v0.8 fixing COMM1/2 Channel selection rotaries update: 13th November 2018 - Updated to v0.9 to remove AV8B entry that was causing lack of comms with DCS update: 21st January 2019 - Updated to v1.0 to correct errant FUEL DUMP switch behaviour NOTE: You should only download the latest version, I am only keeping the old versions here so I can get an idea of how many people are actually using the module. DCS-BIOS v0.6.zip DCS-BIOS v0.7.zip DCS-BIOS v0.8.zip DCS-BIOS v0.9.zip DCS-BIOS v1.0.zip
-
Thanks mate, about to start on round 2 will send you a PM if I get stuck on anything.
-
Definitely eyefinity. Using the standard 1 monitor config and selecting 5760x1200 as the resolution (1200p monitors, not 1080p)
-
More information ... The problem goes away running at 1920x1200, so it appears that the issue is caused by running my eyefinity setup at 5760x1200 These screenshots are running on one monitor at 1920x1200
-
Yeah that is possible, will need some more playing with and might even need a change in the way dcsbios works? Anyway, been working on this all day. I have done: Control System Electrical System Power Plant Hydraulic System Gear System Exterior Lights Cockpit lights Going to go and have an actual fly now! Tomorrow, moving on to: Fuel System Cockpit Mechanics Mirrors Oxygen System ECS Master Arm Panel Fire Systems HUD Left MDI Right MDI APMCD Instruments IFEI Sensor Panel UFC Intercom Antenna Selector RWR CMDS ICMP
-
More progress. I have the switches and controls working on the gear, exterior lights and interior lights panels. However ... all of the two positions switches work correctly except for the launch bar and hook bypass switches. For both of these, rather than mimicking the position of the physical switch I find that the down/off position does nothing and each time I move the switch to the up/on position it toggles the switch in the aircraft. Very strange as they are defined the same as the other switches both in the clickabledata.lua file and in my f18 dcsbios aircraft definition file. Perhaps it is an early release bug? Not sure.
-
OK I have figured it out. I thought the 300x numbers were just assigned sequentially but they need to be done in a particular order. The problem is that the only way I can figure it out is by try and error, setting up a heap of "commands" and toggling them through live view to see which switches flip. Talk about painful. Does anyone know if there is an easier way to determine the 300x numbers (second parameter)? The first and third parameters are easy to determine ... defineToggleSwitch("GEAR_LEVER", 5, 3001, 226, "Gear Panel", "Gear Lever")
-
Is the seat armed? I have ejected several times without issue ;)