rocketeer

Looking good! :thumbup:

I believe there is a chrome extension to view photobucket pictures.

I'm out of town for a while. I'd test it when I get back. Figuring this out and getting it to work later would be pretty satisfying. Thanks, John.

Two new F-16 ebay listings. https://www.ebay.com/itm/223461490741 https://www.ebay.com/itm/223461503491

Wow John, you are like a DCS Bios coach! :thumbup: How I wish we have this as a course in college! It would be the most fun class and the exercises with dcs bios and arduino boards would be swell. I understand now where you got those strange lines of code. This: void onRightLouverChange(unsigned int newValue) { /* your code here */ } DcsBios::IntegerBuffer rightLouverBuffer(0x54ec, 0xffff, 0, onRightLouverChange); is from the advanced view of the Right Louver's Output type. I usually just use the simple view except when declaring multipos switch. Following your example, I looked at non functional toggle switch in the A10C's advanced view I get this for a toggle in the Antenna panel: void onAntEgihqtodChange(unsigned int newValue) { g_iForcePollCycles = FORCEPOLLCYCLES; } DcsBios::IntegerBuffer antEgihqtodBuffer(0x11bc, 0x0001, 0, onAntEgihqtodChange); The rest of your code I can just copy, except this part. DcsBios::tryToSendDcsBiosMessage("RIGHT_LOUVER", "+3200"); Right Louver you said you have declared it as an encoder. so it's declaration is DcsBios::RotaryEncoder rightLouver("RIGHT_LOUVER", "-3200", "+3200", PIN_A, PIN_B); when you send dcs bios message you used +3200 for this encoder. now if I use not an encoder but a toggle, how do i send the dcs bios message? For this switch it has several types of messages. Input fixed step message. DcsBios::RotaryEncoder antEgihqtod("ANT_EGIHQTOD", "DEC", "INC", PIN_A, PIN_B); Input set state message. const byte antEgihqtodPins[2] = {PIN_0, PIN_1}; DcsBios::SwitchMultiPos antEgihqtod("ANT_EGIHQTOD", antEgihqtodPins, 2); Input Action message. DcsBios::ActionButton antEgihqtodToggle("ANT_EGIHQTOD", "TOGGLE", PIN); Lastly Output type. void onAntEgihqtodChange(unsigned int newValue) { /* your code here */ } DcsBios::IntegerBuffer antEgihqtodBuffer(0x11bc, 0x0001, 0, onAntEgihqtodChange); In Simple View it would be just: DcsBios::Switch2Pos antEgihqtod("ANT_EGIHQTOD", PIN); so send message would be something like this? DcsBios::tryToSendDcsBiosMessage("ANT_EGIHQTOD", "TOGGLE"); I'm assuming we use the action message. I'm slowly wrapping my head around this :music_whistling:

John, i'm trying to digest your code. You have 4 players. 1. A trigger pin assigned to pin 4 2. fcsBitSw - a circuit breaker. a 2pos sw both connected to slave 5 board? 3. RIGHT_LOUVER - a pot? connected to slave 5 or 20 or somewhere else? does it even matter? since it seems to be the global guy. if trigger pin toggle is flipped, send signal to right louver, the global switch then poll controls clear fcsBitSw poll on slave 5 On Slave 20 4. lstNflrSw - some toggle on sensor panel? check if right louver value changed and if so, poll controls for switches this board clear LST_NFLR_SW poll on slave 20 Did I understand the logic correctly? Questions. 1. onRightLouverChange is anything you made up for a switch state? So I say onAntEGIChange etc? IntegerBuffer rightLouverBuffer(0x54ec, 0xffff, 0, onRightLouverChange); 2. Similarly, rightLouverBuffer is a variable, i can call whateverBuffer? 3. then the values inside 0x54ec, 0xffff, 0, are these fixed? 4. DcsBios::tryToSendDcsBiosMessage("RIGHT_LOUVER", "+3200"); if this is a pot you do a +3200. what does that mean? If i check change for a global button or light or toggle then how do i say tryToSendDcsBiosMessage (?,?) i'm amazed how did you know to code all these!

John, thanks so much! I'd get it a try.

I fly the A10C only (for now), which does not have HMD. I also don't have multi-monitor setup. Currently just using a small spare monitor with my cockpit as I fly only VR. Like you said, I suspect KBB does not recognize the resolution of my monitor. Through all the numerous experiments I figured roughly the border of the KB in VR and try to keep it within the limits. The frustration is the changes in position that I make have intermittent and sometimes random result which end up pushing off the relatively large KB outside the limit and it gets truncated. To answer your question, yes I do get a KB displayed, in VR. It's quite big, centered, a bit high so i have to look up. I like it big so it's easier to read the checklists in VR. And being centered is important. I'd live with it being a bit too high as I can't tell how many more times I have to try to get it lower and still centered given the result is so unpredictable. I am thankful for this KBB to let me customize the pages, remove some pages, rearrange the order etc. If it can be made as a pair like in real life, one on the left and one on the right like being strapped to the thighs IRL, that would reduce the flipping of the pages. eg. the list of airports is good and necessary to know their locations, orientation, frequencies etc. but is a long list to flip through. It would be nice to have two KB up in view, one for less used but still needed stuff for reference, eg. on the right side, another which is more frequently used stuff like RWR list, startup, fence etc checklists on the left. That would be ultimate. Technically it should be possible. For now I'd just put those less used stuff to the later pages.

No one has tried those keyboard commands?

Anyone know what these keyboard commands do? I tried them and nothing happens. Explosion X+LShift+LCtrl Levitation H+LAlt Binocular view toggle B+LWin One frame mode Pause+RShift View all mode Delete+RCtrl View enemies mode End+RCtrl+RShift View friends mode Home+RCtrl+RShift

John, I really appreciate your help on this. Your louver seems to be an airflow outlet vent on the F18? That does not seem to be a switch? I am not using the RS485 solution. I have six independent megas. No master and slave setup. Will this still work? That the value of one toggle be made known to the other megas that are not its slave?

When learning to do start up, I realized that there is a 'push to set' input on the Accelerometer to add. The others were added just for fun. :music_whistling:

anyone know what these keyboard commands do? I tried them and nothing happens. Explosion X+LShift+LCtrl Levitation H+LAlt Binocular view toggle B+LWin One frame mode Pause+RShift View all mode Delete+RCtrl View enemies mode End+RCtrl+RShift View friends mode Home+RCtrl+RShift

Captain Orso, Thanks for your input. I did give offsets, but they are positive numbers, not negative. Because the pimax resolution is twice that of oculus, i need to give positive offsets to my monitor resolution to reach the pimax resolution. Anyway, using the profile for a10c in the KBB is still random for changing size or position. Sometimes i shift it and nothing happens. sometimes it does, sometimes it moves in the opposition direction! I can control the size and position half the time. Tried like two dozen times. I think there is a bug somewhere. Now i got it bigger, centered, a bit high but i'd live with it. For something that is unpredictable much luck is required. I love this utility. Don't get me wrong. I got to customize with all the RWR list, start up checklist, ops notes etc. But positioning it is just too random.

toggling on a light is indirect result of pressing something. Flipping on a toggle which is not functional in the sim would be more direct. But i could not figure out how to do that. I could not do digital read or write on dcs switches. it won't compile. if i declare a pin then do a read that's fine. but I have to use a switch in the sim then it will be global. but couldn't figure out to even read the state of a toggle in the cockpit. All this trouble is because for missions that are not starting cold from the ramp, some of my switches are in the wrong position from the intended mission, and the syn changes the switches in the mission to my physical positions, then immediately the warning light come on. It'd be impossible to figure out what switches to change. Don't you guys who do the sync have the same problem? It seems simple to read an non functional toggle as the flag to sync or not, but i can't figure out how.

JLX, thanks for the explanation and the link. What seemed complicated then now makes sense. I managed to get it working! From your link, i found that my throttle is joystick 3 while the stick is #4. I use the throttle's slew hat push button as a modifier, and CMS on stick for the menu nav. CMS left to toggle menu nav on/off, CMS right to select. I set monitorPOV to 4 as the stick is joystick 4. So my ini file is as follow: [POV] MonitorPOV = 4 [buttons] BtnToggle = 4Joy18 BtnItemUp = 4Joy15 BtnItemDn = 4Joy17 BtnSelect = 4Joy16 [Modifiers] BtnMod1 = 3Joy1 Realized i could only see the function keys appear on monitor, while in VR only hear my selection. Reviewing this thread shows that others also can't see it in VR, so i'm not missing some step. Separately, I had to assign another button to trigger the comms start, ie. the \ command. I used the CMS press button with another modifier, the paddle switch. So CMS press button starts the \ comms, then CMS left toggles on the menu nav, then CMS up/down to navigate to the desired F key, then CMS right to select the one I want, all with pressing the modifier. Meanwhile, hearing the navigation in VR and seeing the navigation on the monitor by peeking through the VR headset nose gap. This utility works beautifully. Thanks again!

const int switchPin = 52; // the number of the toggle switch pin int switchState = 0; // variable for reading the toggle switch status void setup() { DcsBios::setup(); pinMode(switchPin, INPUT_PULLUP); // initialize the toggle switch pin as an input } void loop() { DcsBios::loop(); switchState = digitalRead(switchPin); // read the state of the toggle switch value if ( ++g_iInitIntervalCounter == 0 ) { // check if the toggle switch is flipped up. If not, it remains LOW, then poll the controls // If it's not LOW, then it won't poll control therefore the syncing will not happen! if (switchState == LOW) { PollAllControls(); } } } I learned to code a push button, then realized I have to keep pressing it to remain high, so i changed it to a toggle switch. The above works. If I don't flip the switch, it polls the controls, finds the difference and syncs the switches. If I flip the toggle up, it does not poll and therefore does not sync. So for missions that I don't want to sync, like those starting from the ramp, then I flip the switch up. This is great. However, this works only for those panels that are in the same sketch as this new toggle switch. My entire A10C cockpit is covered by 6 Megas. Is there a way to check the status on this new toggle switch on a particular mega, then make it a global value so that all Megas know its status and then decide whether or not to poll the switches on those megas?

I envy people with CNC machines and 3D printers.

Thanks Blue for all these info. I'm learning quite a bit from this. So you say it's dcs bios, is this an unused button? ie. it has not been assigned to any of the switches on any of the a10c panels? for dcs bios i just use Ian's code. I don't know how to use arduino outside dcs bios. What if you have many arduino mega boards connected? how do you tell it to use the D4 on a specific one?

I googled a few places including wikipedia and pimaxvr website, all confirmed each eye 2560x1440. i tried changing the size and X Y positions on the lua file. nothing happened. The values I entered sometimes they get changed back the KBB, sometimes not. As for the KBB itself, the size and position I set will result in very unpredictable result. Sometimes the size and positions that I change on the profile don't make any diff, sometimes a little bit and they changed a lot. It's a lot of trial and error. I've gotten the size i want, and position is still off center a bit, but if i change any more it may just get worse. so i'd live with it. thanks for all the suggestions.

Hi Blue, I used example of 2Joy6 as second joystick detected by game controller control panel, be it a keyboard encoder or what not. Your digitalRead(4) i assume is a button #4. But what is it connected to? Arduino? I know certain arduino boards like the mega or nano can't be used as keyboard encoder. I could use megas for dcs bios. but not directly without dcs bios for function keys and other dcs keyboard commands that are not directly controlling switches.

ok so say i use a push button using a keyboard encoder, how do i code if this button is pressed? assuming if pressed the value is 1? something like this below? void PollAllControls() { if 2Joy6 == 1 { engAntiiceSw.pollInputCurrent(); cabinTemp.pollInputCurrent(); //... } }

Pimax customer service and support teams both suck big time. They make great VR headset, but service is non existent. When I asked customer service when will i get my headset ordered in dec, they said you will get it when you get it! when it finally arrived, i had problem getting it to work. Support team suggested things that i've already tried, ignored my requests to discuss on the phone or video conference, as some others claimed they have done for them. Then one week later they closed my case saying resolved! I gave them a piece of my mind. The FOV is fantastic, the resolution is better than my Rift. i can't go back to the rift. but if you enter problems, you have to rely on forums like reddit etc. instead of support from pimax.

When we start off cold it doesn't matter the positions of the switches since we'd be changing them anyway. But when i start off at the runway, it changes the default settings for that mission to the position of my physical switches, which may be at the wrong positions! I don't know what has changed and how many. How do I know what are the original/correct settings, then go and change all of them? Now this sync seems to introduce a big load of work at the start of a mission, instead of the original plan to sync and reduce the manual flipping of switches to sync with the game. How do you guys deal with this?

you are really good at 3D stuff! :thumbup: