vstolmech513

After updating to the latest software (1.8.18), my UFC/HUD controls are not recognized in SimApp Pro and the exports from the game are not working on the physical MIP UFC controller. The game recognizes the controller is there and functions correctly with all of the buttons/knobs, etc., so it is being detected by Windows and DCS, just not in the SAP software. I tried doing the repair lua function and that did not solve the problem. I tried unplugging the USB-C cable to the controller and plugging it back in, but that did not work either. I have the ST throttle, SL joystick, CR and TO panels, and the 3 MFDs connected, and they are all recognized and working correctly in SAP. Anyone else seeing this or know of a way to roll back to the previous version of the SAP software to troubleshoot?

You can always just hit ESC and click on message history, it allows you to see all the messages you have received based on the selections at the top.

I use a modifier on my flight stick to allow me to effectively double the number of buttons. I use the paddle switch and DMS FWD to bring up the kneeboard and then paddle switch and DMS left and right to cycle the kneeboard pages forward and backwards. I also use the paddle switch and TMS FWD and AFT for my zoom in and out slow.

@Wawarare you still having trouble seeing the Compass George menu and it not even showing up on your screenshot? I was having the same issue as you, I could see the menu as the pilot but when I was the CP/G, I couldn't see the compass and it never showed up on my screenshots to even begin to troubleshoot where it was. Then I realized that I had only mapped the George/AI button for the pilot and never mapped it for the CP/G. Doh! Not saying that's your issue, but it was why I could never see it on my screenshots...

@ExoticTroutwhen you say you had no joy of tanking from the S3, did you get cleared to connect, then just not get the "you're taking fuel" bit after plugging? A quick track is always a bonus, but is this a tanker in a mission that you created? Did you ensure that you added an S3B Tanker, not just an S3B? These were things I messed up when I started trying to be super cool and trying to make my own practice missions, not sure how advanced you might be in mission making, not trying to offend.

Chapter 10 should be what you are looking for in the 80T-111, although it doesn't give in-depth procedures, it does show diagrams.

Everything on this airplane has to do with weight. Electrically driven adds weight that has to be sacrificed somewhere else. So you either get less fuel, less ordnance, less avionics, etc. IRL these are a POS and hardly ever get fired. When they do get fired they jam or hardly, if ever, come back empty and I have seen these actually frag themselves (usually due to pilot error, firing too low/too steep or once, and it was a full bird Colonel, swore that two rounds impacted in mid-air and fragged his jet because there is no way he did something wrong...)

It's also worth noting that the DDI that the TPOD is on has to have TDC priority (diamond in top right corner) for it to 'fire' the laser for the Mav to pick it up. Not sure if it is a bug or correct for the TPOD to continue blinking LTD/R when the TDC priority is not on the DDI that the TPOD is on, but it will either not lock at all or it will blink between the X and the square but not actually lock on without TDC priority on the TPOD (or that's the issues I found I was having when I could not get a solid lock on the Mav).

It just depicts the stations from left to right (as you're looking straight ahead out of the cockpit) as top to bottom. It's like the jet is in a right-hand bank.

Multi-Monitor works in CA I was having the same issues as well as being unable to use the bino view with my muti-monitor setup. I am running three 27" monitors with a 24" below them for MFD exports. I added the below to the bottom of my monitor setup lua and it has been working perfectly for me. UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center I used to define my GUI and just had my UIMainView as my GUI. I deleted all of that and added the above at the end of my export definitions and it worked.

Multi-Monitor works in CA Talk about a necro... but, I have been messing around not willing to accept that you need such workarounds when the stock 3cameras lua works with CA and allows a centered bino view and gunner's view. I always defined my GUI in my monitor lua and after copying and pasting what the stock 3Cameras lua had, I finally got it to work with 4 screens, 3 wide and one below it where I export my MFDs. My overall resolution is 7680/1080 This was how I defined my GUI and MainView before: GUI = { x = 1920; y = 0; width = 1920; height = 1080; } UIMainView = GUI Here is what the stock 3Cameras lua has, which is what I copied and pasted into my custom lua after deleting the GUI definition: UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center I don't know if this is something that has changed recently but I haven't tried messing with this in years, only to find out I never tried the stock 3Cameras lua to see if it would work. Works well in both SP and MP (tested in current OB) as you can see in the below screenshots (only complaint is that in bino view the rest of the view is not blacked out):

Are you using a single monitor or multiple monitors?

SINS Cable Connects Not sure what your issue is, worked last night just fine in OB:

That's some strange happenings there Swift. It doesn't blink on me when I replayed the track and taking control it doesn't blink either. I know it's probably a stupid question but did you try a repair? I had an issue where I couldn't dim the indexer at night and it was washing out my NVGs. I ran a repair and for whatever reason it fixed it. I wonder if there is some sort of log file that says what file was changed or fixed during a repair? Anyways, just my .02

I searched as much as I could and did not find any other bug reports regarding the issue that I, and others in my group, are seeing. When you slew the TDC cursor over the azimuth scan setting in RWS, the scan numbers disappear and remain missing until you slew the TDC cursor over the number again. You can sometimes get the TDC depress to change the setting while it is gone, but not every time. If you switch to TWS everything works as advertised, and even in RWS the radar range options work perfectly using the TDC cursor. I tried a repair and removed all mods to ensure it wasn't something interfering with the files. Track attached. I was using the Instant Action Free Flight mission on the Nevada Map. F-18C Azimuth TDC Bug.trk

Technically there is SMDC (Shielded Mild Detonating Cord) all the way around the base of the canopy, so there shouldn't be any plexiglass left on the canopy at all. It would be even cooler if the emergency canopy fracturing handle would work on the ground to do that for when the pilot is stuck in the canopy and can't eject (mostly ground emergencies such as crash landing and can't open the canopy due to the canopy step being jammed/stuck.) It's a metal cable that's connected to the black and yellow D-handle and is about 10-15 inches long. It gives just enough slack to crouch down and then a good tug blows the canopy, assuming the safety pin is pulled out just behind the seat checklist on the port side canopy rail.

Swift, do say that thinking they followed the density gross weight reading along the curved line rather than dropping vertically? I don't see how else they could have gotten the roll distance that far off.

This has seemed like it was backwards to me since I first started doing the training missions almost 7 years ago. Does anyone else feel that the emergency flap retraction is supposed to bring the flaps back up and not deploy them? The emergency speed brake retraction closes the speed brakes when they are open, however the emergency flap retraction extends them to the full down position.

No, pressing designate makes the selected waypoint the target. It should change from a circle to a diamond and the TGP slews and should lock in place. I have this happen all the time and the only way to get it to stay is to TDC depress. Seems like the TGP is not recognizing the designate as a type of TDC depress maybe?

Just curious, how come you have an aspect ratio on your exports? Seems like that makes them a viewport in and of themselves and not just a display that is exported to an alternate location? I'm genuinely curious as I have not seen that anywhere else. I've attached my monitor config (3 27" 1080 monitors with a 4th 24" 1080 monitor for MPCD/MFD/DDI/AMPCD exports). Ricks 3cameras_MFCDs_Right.lua

@Scooternutz, that's a nice patch in your sig... my fav was our Friday patch

Like Harker said, you don't tune a frequency to MIDS, it's an encrypted 'channel' that you select to talk to your flight or anyone else on the same 'channel' So say you're a flight of 2 Hornets for a SEAD tasking and a 2 ship for CAP. You can all have MIDS A on channel 1, then the SEAD flight can have MIDS B on channel 2 and the CAP flight can have MIDS B on channel 3. All of the Hornets can communicate on MIDS A and each separate package can have their own comms on MIDS B. That then leaves you to have COMM 1 tuned to say AWACS, and COMM 2 to common strike package. Now you essentially have four conversations on-going. All you have to do is turn your D/L ON, select the OSB next to VOC A or VOC B, press the channel you want to assign it and press enter. Ensure you have MIDS A/B assigned a control in DCS and SRS, if you use that, and you should be GTG.

Do you have a triple monitor setup? I do and am unable to see anything but black screens. Everyone else with single monitor setups are able to see the PLAT cam, AFAIK. Knowing your setup and in-game resolution might assist in trouble shooting.

This good enough?

If you're looking for realism, there is no such thing as a rolling landing on a LHD. VLs are the only authorized landing aboard ship. Unfortunately, even IRL, people try stuff like that. We had a VMA-311 jet crash trying to do a RVL (Rolling Vertical Landing), which is completely against NATOPS. They actually did it twice, the first time they got lucky and landed it, the second time the mains caught the back of the ship as it pitched up and it skidded to a stop near the island. All pilots involved were immediately removed from the deployment including the pilot of the crashed jet, the LSO, the flight lead and the Officer In Charge (OIC) of the Harrier Det. Not 100% positive but I'm almost certain none of them ever flew again.