granola1861

An idea that would be most helpful for WW2 aircraft that don't have all the lights to tell you something is wrong. But could still be useful for any aircraft Under ground crew, add a command to have the crew chief perform a maintenance once over. If there is any damage he could report it including the severity. Then the pilot makes the decision to repair. I've had hard landings where I can't tell but my gear was tweaked and didn't want to do a repair (but should have) and didn't discover the issue until I took off and the gear wouldn't go up. -Climber

So where in the heck is that clarification of bomb on target? That is the garbage we are talking about. The manual should say that. It's nice to have these cutesy hyperlinks and all but it misses readability! I appreciate the help but help us all by making a clear manual. Sorry to sound so ticked off but we've been looking for answers and been told,"it's not the game it's you" over and over.

Alright here is the first of my 2 track files. Tshark will be posting his from his side as well. I was the WSO for both. The Mk82 test I entered the variables into the bomb computer and added all the output info into the WRCS computer (I guess that isn't correct). The first pass was way short. The second run all I set was the drag coefficient and the advance according to the computer (still entered the other variables but ignored the other outputs. We shacked the target! The Mk 20's were a different story. I've read that DCS physics with cluster bombs is goofy so I used the same DT setup as the second Mk 82 pass that had hits. Tshark set his aim center target and around 3-4 miles I grabbed the radar lock (same as I always do). These were short by a couple of thousand feet. So we decided to offset our targeting to be long for the second pass and surprise our bombs hit long (right where Tshark had the hud on as I locked the radar. Befuddled to say the least!!! I will post my second file next in thread due to file size. Bomb test Mk82.trk File #2 See above post. It seems that lots of confusion still exists. We have several people all trying (with some former pilots and some pretty smart folks too) and we are getting inconsistent results. Please take a look at our tracks and help us out. Best, Climber Bomb test Mk 20.trk

Would love a more step by step manual... Tutorials are all over the place with workarounds having to be used to get results. For an aircraft that was touted as multiplayer ready, it seems that Jester gets the attention. Please help out with these requests. We've tried multiple techniques and a lot of variations have been attempted on different computers, different missions, after DCS repairs, etc. We love flying the Phantom and look forward to the potential it offers. It's a great module but some better guidance is warranted. Thanks in advance, -Climber (WSO to the OP)

I have the virpil apache collective and love it. Works like a charm.

If I were to have a FFB cyclic then we would be in a pickle (BTW I'm Tsharks pilot). Currently, I just don't hit the trim button before setting attitude or rad alt hold like I would previously. Like Tshark said I have a springless stick that will hold position so we have a built-in workaround. I had been having serious issues holding a trimmed (attitude and alt hold) hover. Haven't tried since the latest patch that talks of SAS fixes but can't help but wonder if the FFB stick in front may be effecting the trim holds. I find that these holds accrue trim over time since resetting trim I notice an immediate flight attitude change. I'm hoping this was an unrelated bug that was just fixed. The fact is like previously stated, ED needs to address this. -Climber

So we were hoping that this was fixed with the latest patch. So many other things have been resolved and I REALLY want to love the Phantom but still having this issue. Attaching the server track for the latest "WSO feeling left behind" issue. We switched out server hosts with the same mission and it ran fine. I'm not considering that a fix since this issue doesn't occur every time. Post patch everything worked well. For disclosure both myself and Tshark ran a slow repair of DCS prior to the latest attempt (attached file). I'd really appreciate a Dev looking at both my tracks and Tshark's tracks to see if there is anything abnormal. Best, -Climberserver-20241214-195914.trk

I'm also having issues with the thrust grip radio hat switch. I'm seeing it move (on the actual trust grip) when I push my mapped button but nothing changes on the mfd. What am I missing? With so many current module bugs it's difficult to determine what is a bug vs what is a feature. But hey everything is in stable release and no more open beta! That last sentence is sarcasm BTW...

Track attached from this happening tonight. This track is from the host side of the server. server-20241026-200638.trk

Seems like it was taken out of the oven WAY too soon...

Bueller? I guess everyone is just using Jester or it's not a problem It sucks getting left behind in the hangar...

I've taken to learning the WSO job seriously and have found that if I have ME created way points I will write WP's 3 and up on the canopy. WP 1 and 2 can get set while the pilot gets me to the runway. As I work through the points I'll erase them. It's really easy to do once you get a system. Having the BE set to Target 1 is a great idea, just flick the dial for a BULLs reference then back on track! I like it! -Climber

Am I right in thinking that the AWACS should have a donor dot? I guess that's my big question. I will replace the AWACS and re-save. This is one of those missions that I've added and subtracted client aircraft over time and made other small changes along the way. I'd say it's probably a few year old by now. I may even need to start another mission similar from scratch, but it's such a good mission.... Thanks for the reply Raven. -Climber

That was my understanding but the videos only glossed over it and there hasn't been a manual update for some time that shows the DL implementation.

Ok folks quick question. I may have a corrupted mission but have a DL and AWACS question. I remember Wags stating that AWACS are automatically set as donors and should show on the HSD with a donors dot but my mission it isn't, and therefore doesn't need placed in the donors column in the ME. Is this correct or should I set the AWACS as a donor in the ME? I'm getting contacts from Overlord but no dot. Is this correct? Thanks in advance. -Climber