-
Posts
161 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by FriedrichNix
-
Yeah. I asigned ARM, OFF and RESET to a 3-way-switch on my WinWing Takeoff Panel and only positions OFF and RESET work. When I set the (hardware) switch to ARM, ingame nothing happens. In the controller options when I flip the hardware switch all positions are recognized (meaning, the corresponding sections are highlighted, when switching to either of these three positions). I then asigned the ARM function it to another (hardware) switch, just to check, but this also didn't switch the position in game. Clicking on the hook-switch in game with the mouse changes the switch position to ARM as intended.
-
Germany just ordered 60 CH-47F. Exciting!
-
please contact support directly Name Change
FriedrichNix replied to Scoobyon's topic in Forum and Site Issues
Old thread, same problem? Any way to change the display name? -
fixed Mission 2: Smoke does not "cut away"
FriedrichNix replied to FriedrichNix's topic in Bugs and Problems
Thank you for taking the time! -
fixed Mission 8 - no comms with the Ground after landing
FriedrichNix replied to lester's topic in Bugs and Problems
Unfortunately the A-10C cannot land on a carrier. I believe you posted your message in the wrong subbranch. Hier is the "Iron Flag, Part 1" Campaign for the A-10C. You clearly need something for the F-18C. -
Hi, unfortunately Mission 2 didn't work for me atm. I am on Open Beta: 2.8.0.32235 The problem describes as follows: - Start ok - Goto Tanker ok - Refuel ok - Goto WP 4 ok - Get chatter on the way - Reach WP 4 - get chatter and tell SMOKE to cut away - SMOKE tells me he cuts away PROBLEM: SMOKE stays at my side. Literally. SMOKE stays in formation and follows my orbit at WP4. I got a screenshot from VoiceAttack where you can see, that SMOKE tells he cuts away. Also my last Trackfile is here: https://1drv.ms/u/s!ApJ_AlLpIYGt7C9A8VyAMmUTenVV?e=YGaqM7 Maybe it's just a minor glitch Thanks! Griefhard
-
Same here. I fly only VR and maps are gone. Pages and waypoints are shown, but background is missing.
-
fixed Mission 8 - no comms with the Ground after landing
FriedrichNix replied to lester's topic in Bugs and Problems
Yeah - I have the same bug and flew the mission twice now. I did everything to the letter. All worked good - all shooting and stuff. Dialogs happened on the way. At the Truckstop: - Biff went to orbit - I continue, get the message from the tower to report 5 miles out. - I report 5 miles out, Tower tells me to report "gear down". - Gear is down, so I report "gear down" shortly after. - Tower gives me "clear to land 21L" - Touch down and no more messages! I continue to roll out on the runway to the end and then turn left to ALPHA. No message after reporting wheel down from tower, no switching frequencies, no F10 menu option. Then I continue taxiing to the stop, shut down my jet and get a 50 score, which doesn't let me proceed with the next mission (until I press skip, which I haven't yet). Happened to me twice flying the mission on two seperate days. I checked a couple of YouTube vids with this mission and I do nothing different than these guys. One had already gear down when contacting tower, so it's not that either. Please review this mission once more @baltic_dragon, since I really think there is a trigger problem. Thanks for this great campaign! I would hate to skip the mission. Last Track File: https://1drv.ms/u/s!ApJ_AlLpIYGt7C2c1VzljBpKUeKM?e=kQ4zEX -
You need to be on the discord. At the moment it seems to be some custom config steps for it to work. I guess it will be fixes within the next few days. https://discord.gg/GcGy5B4x
-
I still got no functioning Comms menu... Don't know what I do wrong. installed it updated to the leatest version. Functionality still gone... ... it needs some extra steps and files to get it working right now ... (from the Vaicom Pro Community Discord)
-
Is this actually Hollywood??
-
Jester commands keyboard mapping, now VAICOM is dead
FriedrichNix replied to Shiroka's topic in DCS: F-14A & B
Awesome news on the matter! Thank you for reacting so quickly! Great outlook on the matter! Thanks! -
Look ... it was not supposed for Vaicom Pro to die. Something real bad must have happened to Hollywood, since he was super active and always updated his project. And with "real bad" I mean terminal, dead, coma or something else real disastrous. He even cannot check the forums, which he did. So. Vaicom Pro died an unexpected death and we now have to deal with it. One can play DCS without it and it is not the responsibility for the devs to keep an outdated mod running. It's the responsibility of the developer to upgrade. It is very unfortunate, but my guess is, neither will Vaicom Pro receive any updates, nor will the sourcecode be passed on. But maybe there is someone out there, that can make stuff like this happening. As I said, the DCS Bios / Flightpanels guys do something similar to switchboards, but not ATC, yet. But I think it's kinda dumb to make ED responsible for not keeping their code aligned with an outdated mod. And for the Supercarrier ... That's your opinion. Read about it, a lot of people complained for the Supercarrier to be a paid module at all. And I like the addition of moving clouds and rainbows, because it's freaking awesome!
-
An ATC overhaul is much needed and I heard in the making or at least planned. But I don't know anything more about this. With an ATC overhaul though, we might get new options and maybe new functionality. But ED should really think about what to implement and what not. The long called VOIP solution is in, but everyone uses TS and SRS. So development on that part could maybe have been used ... wiser. It might be a first step towards the ATC overhaul, though. Also a real ATC module would be something I would greatly appreciate and instantly buy. Mapping keys with VoiceAttack works quite well. But it's not the same. About Hollywood I guess something bad and unforseen happened to him. Sadly, because he was very active and surely didn't want to abandon his work. But it is this way now.
-
So far I have not found anything similar to Vaicom Pro. Probably someone has to redo the whole thing. The people from DCS Bios and DCS Flightpanels do a similar thing with button/switch input but it's not configured for ATC and I doubt they will start a project like that. It simply has to do with Vaicom Pro. If you don't have it, everything works just fine. If you have it, Comms Menu won't show and the ATC voice commands do nothing. It's got nothing to do with DCS, the jets or VR. All of that runs perfectly fine.
-
Unfoetunately because of a recently mishap with Viacom Pro, I had to restart the mission at the AAR part. If you choose at the beginning of the mission to skip ahead to the AAR with the F10 menu, you start with full tanks when approaching the tanker. Maybe reconsider giving the player like 60% fuel so one can practice staying with the tanker and refueling a bit more, than just a few pounds. ...and the mentioned A/A TACAN which doesn't work that way at the moment, which shouldn't be a campaign issue, but more a DCS design. Whichever is the right way to set up, once decided, it should be represented in the campaign. But I read that some C130 guy mentioned A/A TACAN is used for AAR, ED says it's not used with AAR.
-
If you want to uninstall it completely (it's just a matter of time), you need to: - go to the RESET Page (Vaicom VoiceAttack Panel) - tick all options on the left, then click - MASTER ZERO on the right once done - close voice attack - go to voice attack folder, Apps, delete vaicom folder there once done - go to savegames/dcs/scripts/export.lua and edit the file (notepad++ for example) - delete vaicom line After that: - slow repair I also looked for anything vaicom in saved games/dcs or saved games/dcs.openbeta and deleted that too. After the slow repair you can reinstall you mods (if any - voice mod from echo 19 works, F5E RWR fix works also). Now you completely have purged Vaicom Pro from your system!
-
Thank you for this campaign
FriedrichNix replied to PD919's topic in A-10C Iron Flag Part I Campaign
Wow - that would be great! I would also very much buy this basically instantly. -
Hey, first - great campaign, much fun so far and an awesome addition to really learn the A10C(II). I am really early in the campaign and take my time, but here's a couple of things about mission 5. - I finished with a score of 75 but don't know where I lost 25 points. As it doesn't matter to me, it's ok. A couple of things I have messed up, but I didn't ge ta negative feedback from Biff. - At MOPAR I first didn't know what to do. After takeoff I think it was a message to fly to MOPAR and wait. I would find it great, if another message would come up at MOPAR to anchor and wait for Biff. After circling a bit I continued to fly to the next waypoints. I then got the message that Biff took off and I flew back to MOPAR. - Time HACK. The 5 minute hack was announced quite early and was also mentioned in the documents. So it was easy to get it right. After that there is a 2 minute hack, which I didn't know of. It was like "2 minute hack coming up. 5 - 4 - 3 - 2 - 1 - HACK". I honestly didn't manage to get it input that fast. But since Biff was lead, I guess I didn't have to. Maybe a message "2 minute hack coming up soon" a minute or so before the actual hack starts would be awesome to get everything set up. Other than that, it's much fun to play the campaign and I am already looking forward to Part 2 and what is coming up then!
-
So - any word from Hollywood? Is he still around and is VAICOM still being worked on? This is a great peace of software and really worth every penny. But Hollywood didn't show up since April and I am worried, that maybe something bad happened.
-
Landing light switch only recognises 1 button
FriedrichNix replied to Cowboy10uk's topic in Controller Questions and Bugs
In the Huey there are actually a bunch of these buttons, that have no "coded" positions or do only have a toggle. I know some folks did change things like this on other aircraft, but I don't know how to do this. For the Huey I wish for all buttons/switches to have their states coded, so that you can set it via HOTAS and/or button boxes.