Jusif

SOLD

I have a set of Slaw Device Viper V2 pedals for sale. They are in great and working condition, but I am not longer using them. The pedals come in the original packaging, box, including tools, hardware and the damper installation kit hardware (damper not included). I originally paid $640 for these (shipped). I'm asking for $450 + shipping (from NYC), OBO. Happy flying!

Still available? Interested.

+1 on the thank you, Bunny.

@Scaley or anyone have any further thoughts on this? The exported MPCD viewport showing the TADs VID is very dark. Makes it very difficult at night. In-game screens are blinding bright and the external monitor is still very dark. Any workarounds? Any reshade ninjas here? Any clowns with some guesses?

I was slightly misled as no one had seemingly tried using the KU in multiplayer in the same cockpit at the same time. Correct, with only one KU_init.lua file any exported viewports will show both KUs overlayed on top of each other if they are both in use.

Interesting. How were you able to export two different KU viewports?

Ahh, interesting. However, the module is allowing the PLT and the CPG to input different messages at the same time. The viewports overlay on top of each other and make it painful to read. Try it!

Ahhhh I was wondering if it was the older version looking nicer than these days. What are you flying these days, sir?

Where do you get this nice iphone 3gs border for your kneeboard?

Wonderful. I did run into an issue with the PLT and CPG using the KU at the same time. I think we need a PLT_KU and a CPG_KU hack if possible like we have for the MPCDs. Is that an easy update/patch?

Cheers, I see them working now. Any other useful kneeboard mods worth looking into once the pages are all generated? I've seen things that look like a tablet, etc. There is not way to leverage any grouping correct? If I have 300 pages of kneeboard pages, I have to navigate through them one by one?

Could you link your post or elaborate on get it working manually? This is my first time using kneeboard builder and I'm here for the ah-64. Simply create the necessary folder and let the app do its magic, or something more involved such as creating a kneeboard for a different aircraft then moving it into the ah-64's folder? Also, could you provide the exact folder name? Is it AH-64D_BLK_II or AH-64D?

Bunny, Any idea if we have access to the CMWS viewport for an export to use with Helios?

Ah, you are right. I finally installed the Nvidia DDS plugin for photoshop and can see the textures a lot better than IrfanView was showing. Thanks!

The people's champion is at it again, this is fantastic! I'm glad this interesting problem was tempting enough to draw you out of Helios retirement. You should record your screen while you do the people's work! I'll check these out shortly. But seriously what file has the actual color data for the white/yellow elements?

Oh, I didn't notice the CMWS buttons and switches in the interface - I'll take a closer look knowing this. Yeah, I figured you could update the interface much faster than I'd fumble through it. Sure, I can manage adding them to the profile. I do have a few questions for you as I've already started thinking about adding the Fire Detection Panel to my profile What is your preferred way of grabbing cockpit images? The textures are very strange to work with - as they have many different layers. I honestly have no idea where the yellow is coming from in the Fire Detection Panel as far as the textures are concerned. I ended up taking a screenshot from within the model viewer at at a slight angle - as part of the cockpit was blocking that panel... How would you go about implementing the interesting ENG 1, APU, ENG 2 buttons that have a flip cover and have 4 light states? FIRE - OFF, RDY - OFF FIRE - ON, RDY - OFF FIRE - OFF, RDY - ON FIRE - ON, RDY - ON My initial thoughts were to try and use the common guarded switch control, but the underlying control is a switch vs a button and the interaction with it is weird with a button. The button under the cover would also have to react to two different pieces of game data... Is there an existing common button that can handle that? Working around existing control limitations, I'm thinking of using a transparent button that handles RDY'ing the system when pushed, and does not change its state based on any game data. Three user images would live underneath the transparent button. One being the basic button graphic with no lamps on. The other two images would represent the FIRE and RDY lamps and have their visibility powered by their respective game data in the interface. I'm not sure about a 'push' state for the transparent button yet, perhaps a bit of semi-transparent shading around the edges. For the button cover, I'm thinking of using two buttons (or switches for the swipe gesture). The first cover switch representing the cover-closed state would be positioned on top of the momentary button and when switched up it would hide itself, and the second cover switch would unhide itself. The second cover switch would represent the open state and would be positioned up and out of the way of the actual momentary button for RDY'ing the system. When the second cover switch was switched down, it would hide itself and the first cover switch would unhide itself. This is my first time messing with Helios and a profile. I hope your expertise with the controls and guidance can reduce this complexity, but I don't mind working around things if needed. The apache is making me do crazy things Reference photo during a light test.

I'd love to see you add the Fire Detection/Extinguishing Unit that is left of the EUFD in the pilot seat. Any chance we can get that in the next update? CMWS panel off to the right would be slick as well. Thanks!

I'd love a video on the reshade brightness boosting. Even partial textual instructions would help get us started.