mdtenor22001

Yup, I just flew it and ADF 380 doesn't work. I had a hard time finding the right ship. But a nice first mission! I'm hoping the rest are great too.

Yes, this one.

It's still happening for me, but if I use the keyboard shortcut it works. I fly in VR. I get really frustrated when I forget and get in the air and have to restart my mission!

I have not sent to ED--mostly because I don't know how... (I know, I should learn...and I'll take this as a nudge to do so.)

Just FYI to anyone who might read this before ED fixes it: I got it to work by fast forwarding time for about 10+ minutes, taxied forward just a little, and then it started working. Mission success. Great campaign, Reflected.

Yes, this happened to me tonight two times. No mods, slow repair.

If anyone reads this thread and has similar problems: I figured out what the problem was. It was SimHaptic's auto-start function; when enabled (and in export.lua), it breaks FFB. When I removed the line from the lua and manually start SimHaptic, everything worked properly.

Re: New Profiles, I'm not sure I've tried that, although part of my troubleshooting was using the VPForce Configurator and I changed the name of the Rhino Joystick Base to see if it would maybe fix things. It created a new "device" that I had to map the axis for, so is that what you're talking about? And yes, DCS "sees" the original Crosswind rudder (because the USB is connected and because the brake pedal axis are controlled by the original rudder) and a separate VPForce controller, which I set the rudder axis to. Re: Turning on the joystick first in Windows, I did think of trying this. I kept the power off and unplugged the USB of the pedals until after Windows was fully booted, hoping that would cause Windows to "see" the joystick first. Unfortunately that didn't help. I also tried the inverse: keeping the VPForce base off and having the pedals powered up first to see if more "recency" would help Windows see the joystick. That didn't help either. Appreciate the thoughts and if anyone else has ideas, I'd appreciate them!

Wanted to let you know that this is truly one of the better single player campaigns, especially for helicopters. Thank you for your hard work. Just finished and wish there was more. I'm looking forward to your next projects!

Hello everyone, First off, huge thanks to Walmis and Hiob for their extensive assistance in troubleshooting this issue on the VPForce discord. I decided to open a thread here to see if anyone else in the DCS community had experienced this issue or has advice on further troubleshooting. In short, I so love my VPForce Rhino that I decided to take the plunge and convert my MFG Crosswind pedals to FFB using the parts Walmis and Kalktori sell. It was a very straightforward installation and setup. However, I've had a major problem that we cannot seem to solve: After a PC reboot and reopening DCS, DCS stops sending FFB data to the Rhino joystick base and instead sends all FFB data to the pedals instead. The easiest illustration of this: when working properly, in the Huey I have a slight spring on the stick axis and no spring + damper on the pedals. When I press the force trim button, the spring on the stick relaxes, as you'd expect (but the pedals stay the same). When it's not working (after every reboot), when I load into the chopper, the stick is totally limp and the pedal axis has spring applied. When I press the trimmer button, nothing changes with the stick, but the spring force is released from the pedals until I release it. So DCS is seeing the pedals as the "primary" FFB device." The only thing that changes this is, after booting into DCS and starting a flight where it doesn't work, is to exit DCS and change the pedals' "USB Device ID" between 2052 and 2054, alternating based on where it was set previously. After I change the Device ID and reset TelemFFB to reflect the new Device ID, when I boot into DCS it works properly. I've tried all sorts of troubleshooting, including completely re-doing my USB setup so the two VPForce devices are directly plugged into my PC rather than via a powered USB hub. Updated all bios and drivers are up to date. The VPForce joystick works perfectly 100% of the time if the pedals are unplugged. I think the problem is, in part, that DCS sees both devices as FFB; my rudimentary understanding, however, is that DCS doesn't send rudder FFB and instead TelemFFB uses telemetry data to apply affects. But I'm not finding a way to stop DCS from "seeing" the pedals as a FFB controller. This is all very frustrating and I don't know where to turn next in trying to fix it. When it works, it is amazing. When I load into a flight and the stick is limp (when it's not supposed to be limp) it is a total bummer! Any input help would be appreciated! How do I make DCS "see" the Rhino joystick base as the primary controller every time?!? Thanks in advance! I should add, this happens regardless of module. I gave the Huey example, but it happens with all my modules. For example, the F-16, which I have set to have a very strong spring and short throw, when it is "malfunctioning" the stick is totally limp and the pedals have the spring force. I've also tested it with nearly all of the other modules (I own a pretty diverse amount of modules as I like to go between rotary, jets, and warbirds--hence, one of the reasons I was attracted to the idea of FFB pedals to ease in the changing feel of the pedals.)

New to the Hercules 6.8.2 mod. I tried adding the four files found at the v1.01 hotfix shown in the Way app (and linked above). DCS crashes now when I load into the Herc. When I remove the four files and restore to previous state, everything is fine. Am I doing something wrong with installation of the hotfix? The four files just go into the "Cockpit/Scripts" folder, right?

Sorry, just catching up to this thread again (I'm only an intermittent Tomcat flier). Is the "fix" just choosing to re-fly the mission after spawning in? Like literally spawn, exit mission, re-fly? And this only happens in single player missions, right? I haven't flown multiplayer yet, but I plan on it.

That is an interesting thought. Since I've never played around with a dedicated server, I never thought about the processing power offloaded by the server as distinguished from the single player experience. I don't have access to a server of my own, but I'll see if I can convince one of the groups I fly with to throw it onto a server for testing.

One other point of comparison I'd like to share: When I was flying around last night in the Huey, overall I was feeling like the performance was pretty "stuttery" in a lot of places, especially at low level around the farps when I was trying to sight-see. Using the built-in FPS monitor, I was seeing oscillation between ~38-60fps. And this was after I dropped several of my DCS graphics settings below what I typically run on non-Marianas maps. Just to see if it was the mission or the Marianas map, I decided to load up the last mission in Reflected's Paradise Lost campaign, which is a pretty object and AI-heavy remake of the famous Apocalypse Now helo assault--with the same settings I had just been using--just to compare if the lack of smoothness was comparable and attributable to the lack of optimization of Marianas. To my surprise, the Reflected mission was noticeably smoother with higher average FPS but also less variability in FPS (like during the flight over a heavily populated Andersen or during an attack run with rockets and explosions going off all around). It seemed like the "green line" on the FPS counter was less jagged. Apologies if that doesn't make sense because I don't really know what I'm looking at, but I know that if the green line is spiked or jaggy, things are not smooth, whereas if it is relatively flat, performance in VR seems good. So, even though Marianas runs the worst of all maps on my system, there appears to be something else going on that is affecting the smoothness, and maybe CPU utilization, of the ITJ mission. I wish I had more experience or skill to give more detailed feedback, but I wanted to share that anecdotal experience purely from a single-player (for now) perspective.

Hi team! I've been away from DCS for a bit and just am now catching up with this thread. I downloaded v.006. Took a Huey out for a spin and noticed that overall the performance seemed better than my prior times. However, when my door gunners would attack certain groups, I would still get the slow down to single digit frame rates (was previously getting 60fps). It was less severe and less long lasting than v.002. I didn't have a chance to fly around Andersen to see how my FPS held. I'm on a pretty high-end system, FWIW. I'd be happy to test a copy of the unit-reduced miz--or just wait and monitor this thread. Again, thank you guys for doing what you're doing and working to improve this for all of us! I'm looking forward to flying this with friends.

So, a bit more testing tonight. I'm not sure it has to do with the density of the enemy groups. Instead, I was observing that the slowdown only occurs when attacking the first group of enemies you encounter, the first time--regardless of how dense they are. I turned on markers so I could see and picked more and less dense unit placements. On the first attack (I only tried two modules, the A4 and the OV-10), the slow down would happen whether or not I used rockets or guns. But then, after the frames caught up (about 30 seconds), every subsequent run was just fine until I was out of weapons. And this was true in groups of 3-4 enemies or groups of over a dozen all together. I have no basis for thinking this, but could it be one of the scripts? Like the splash damage script initializing? I recreated it 4x. If I landed and rearmed and went back for another attack, it wouldn't slow down again. It appears to just be the first time. Also, this probably isn't a question for you, but I couldn't find an answer in my immediate searching: the Comm radio doesn't work in the OV-10 while you're in the air, right? I can't figure out how to get to the F-10 map while flying and the "/" key didn't work unless the canopy was open on the ground. I presume that's just an unfinished part of the mod? Does that mean that SRS also doesn't work with the Bronco?

So great! Can't wait to keep testing.

First off, amazing work! I've been following you on YouTube for a while and just downloaded this today to try it out! I installed all the mods and was testing today for the first time as a single player mission. Everything looks gorgeous and I love the fog. It was running really smoothly for me. However, my first flight out was in the A4-E with the default loadout, including Zuni rockets. I came in for a rocket run and when I fired the rockets, everything reduced to a slide show. Like single frames per second. Before and after firing rockets, locked in at 72 FPS. Note, I have a high-end system (4090, 64GB ram, NVME drives). OG Pimax crystal. Marianas normally runs fine (ish) with my system and the mission did before and after the rocket run. I'll try with some other aircraft, but I wanted to flag this. Thank you for bringing this to the DCS community!

The weird thing is that it only happens in certain missions,and I can't figure out a pattern. I've been playing through Reflected's Speed and Angels campaign and the video hasn't worked at all. But random single player missions and online multiplayer it has worked. Surprised to see it has been such a long standing bug.

Is this really still bugged? Just back to flying the Tomcat campaigns in VR. I can't see anything on the screen in the front seat either from the built in camera or the LANTIRN pod. Jester can see, and the symbology is there...just nothing but green (or black) screen.

Anyone flown the "Saboteur" mission recently? (Mission 11, I think). I flew it tonight and did the low level ingress well, and got all the triggered dialog. Dropped off the passengers at the designated place, orbited south until I got the call to return pickup. Returned, picked up the guys in the clearing, got the message that they were in...and then, nothing. Nothing telling me to take off, heading to turn, or anything (unlike all the other turn points). I found my way onto course, and flew the rest of the way home. No more dialog, no voice overs or instructions at all. I have a feeling something was supposed to happen after I picked up Angus, but nothing happened...and I followed the flight plan perfectly and the guys got back into the helicopter at the pickup point. Also, when I landed back at my starting point, no mission success or anything. So, is this mission broken too? I didn't see any other bug reports about this mission.

I've been scratching my head trying to figure this out too. Flying helicopters low and fast in this map is so weird and distracting, with the shrubbery just "growing" right before your eyes. It seems like a basic thing to fix and I see threads on this going back to 2022. Sigh. If anyone learns of a fix, please share.

Thank you!

Florence, thank you for an ambitious campaign. There are aspect of it that are great. But I'm having the same problem with Mission 2, completing all objectives, getting prompts, landing, getting a score, and then it isn't recorded. I know you say it is a "core DCS problem", but none of my other single player campaigns have this problem. Even the ones with lots of other bugs. I know that ED manages to introduce bugs often. But somehow some of the campaign developers seem to deal and give us less buggy campaigns. I'm only on the third mission now, but I'm just concerned that maybe I should hold off until some future campaign patches? Also, what's your discord so we can follow the progress of your bug fixes? All the discord links I've seen in these threads are expired.

No, I didn't delete anything (and the only step I took to get the updated one was access the Google Drive link above, which was empty). I think the Community A-4e and OH-6a mods plus voiceattack are the only mods I have installed. I'll give it another shot. Just so I'm clear: land at hidden farp with blue smoke, take off, head back to original farp area (south of takeoff farp), get fired on by AKs in the woods, circle a bit and shoot back, go land at original farp near where the other Huey has landed, dialog, and then mission trigger, right? Thanks for checking it out for me. I'll let you know if I have continued problems...worst case, I just skip that mission and move along. Enjoying the campaign (although I do agree that it would be nice to have the option to read some of the dialog because I'm occasionally having a hard time understanding it all, or understanding who's talking). But I appreciate your development work and look forward to trying your other projects.