A quick post about what we've been up to this weekend.
I've added some shader effects for the GUI, drawing focus to active elements on screen. Nothing fancy. The joystick / command editor has been fixed in stone, too late to redesign it but it does contain 4 panels (yes a whopping 4 separate pages).
- Quick start with major control axis shown as an active display
- Command list by category
- Axis control per device
The special page is for any joysticks we add OEM support for. Currently we plan to add special support for Saitek LCDs on the X52 Pro and Logitech G940. The cockpit database contains a list of lamps which can be mapped to the G940 indicators, I'll be adding a similar list for some digital values such as torque settings for output to the X52 Pro.
Other hardware will be added when I get units I can tinker with.
This is the last of the major "end-user" areas apart from the mission preview panel.
The config file had more user options added to it.
The FCR is updating the TSD but I'm not sure if the TSD tracks should fade over time. I will be adding the next to shoot symbology shortly.
I need to fix the DAY/NIGHT settings on the MFDs (brightness works, but the all green mode doesn't).
AD is back in the CH-47 cockpit with detail on canopy frame and foot controls. We aim to have around 64k polys for our interiors with materials batched efficiently for real-time performance.
The CH-47 presents a bit of a challenge in that it's intended to be a portalised object or POB. Meaning you'll be able to walk from the outside into a detailed cockpit interior and hopefully you won't notice much of a transition.
I had a stab at programming this a few weeks back and I haven't found a method that works in DirectX. There doesn't seem to be a mechanism for setting the centre unless I'm missing something obvious. I don't know how Eagle Dynamics accomplished this with Black Shark. The only effect I tried was applying a constant-force with a magnitude calculated to keep the stick in a fixed position. Since you're not supposed to send force commands too quickly in case it makes the hardware overheat (according to Microsoft's documentation) I was reluctant to increase the stick updates.
I really need to talk to someone who knows about FF joystick programming to get force-trim working properly.
This is the working title for the firing range since we didn't have a handy name for it. Since then I've had a couple of pretty nice suggestions, my favourites being, "Combat-Helo: Nickel Ride*" or simply "Combat-Helo: Gunnery".
*Nickel ride being the name given to a WOC Warrant Officer Candidate's first flight.
That's all for now.