Wangler

Can this be made open source?

I agree with a previous post: can the devs move this mod to github? At a minimum provide a file integrity check hash so we can confirm an unadulterated *.zip? dropbox went down, multiple google drive links. Not sure what is legit and what isn't at this point.

LOL. That's how the other Viper based milsim works. The one with pretty darn good BVR

With no dynamic campaign those totally meaningless targets will be here tomorrow and next year. Just like the were yesterday.

+1 Malwarebytes. Shut it down hard.

Do you have the F-18?

Wags, the other, better option would have been for ED to state, and state clearly, that those items were not included in the Viper at the 10/3 release date. Then folks wouldn't have had a legitimate reason to complain. This lack of communication is a big reason for the complaints, and is quite frankly concerning.

How can they not be encouraged by the hundreds of dollars I have spent on this simulation, pray tell? I fail to understand why people feel the need to treat these developers with kid gloves. Why do I need to encourage them beyond the cold hard cash I pay as a customer? I'm not beholden to them, it's the other way around. We pay them money for a product and it isn't unreasonable to question why features are removed without notice or explanation why.

Scooternutz, thanks! I think I have it working, and yes, having WP0 in use for the loiter orbit doesn't seem to work. Loiter being WP1-2, with tanker track being WP3-4, seems to work. I can send him back and forth between the two. My code is pretty crude, as I am a noob. -- Tanker loiter orbit function tankerLoiter() local _tankerGroup = Group.getByName("US KC-135MPRS Tanker") local MoveLO = { id = 'SwitchWaypoint', params = { fromWaypointIndex = 3, goToWaypointIndex = 1, } } _tankerGroup:getController():setCommand(MoveLO) end -- Tanker Sierra-November orbit function tankerSierraNovember() local _tankerGroup = Group.getByName("US KC-135MPRS Tanker") local MoveSN = { id = 'SwitchWaypoint', params = { fromWaypointIndex = 1, goToWaypointIndex = 3, } } _tankerGroup:getController():setCommand(MoveSN) end -- function tankerWhiskeyEcho() -- trigger.action.pushAITask(_tankerGroup, 1) -- Tanker Whiskey-Echo orbit -- end -- ADD SUB RADIO MENUs local tankerMenu = missionCommands.addSubMenu("Tanker") -- ADD MENU ITEMS missionCommands.addCommand("Request Sierra-November Track", tankerMenu, tankerSierraNovember, {}) -- Tanker Sierra-November Delivery Orbit -- missionCommands.addCommand("Request Whiskey-Echo Track", tankerMenu, tankerWhiskeyEcho, {}) -- Tanker Whiskey-Echo Delivery Orbit missionCommands.addCommand("Return to loiter", tankerMenu, tankerLoiter, {}) -- Tanker Return to Loiter

For the life of me, I cannot get this to work. Any help, please? I think my waypoint triggers are not setup correctly. Thanks!

Havent tried any VR with the R VII yet, I will DCS VR try this weekend perhaps. I will let you know. Keep in mind, I have Lenovo WMR. It works, but it's no Pimax.

Loving my Radeon VII. Working well in my FX-8350 machine while I wait for Ryzen 3. Doubled framerates coming from Fury X. Really like having the 16GB HBM2 and 1TB bandwidth when I see the 17-22GB of VMEM when running the Tomcat in MP. Have yet to hear the fans everyone complains about.

Installed HELIOS 1.4, and and am using CZ latest export.lua with AV-8 calls. However, all my old profiles work, but the BFB AV-8 profile is completely unresponsive. any ideas? I saw someone post that some changes were required to the profile, but I don't think that is my issue.

The quick guide document is confusing. Does the waypoint with the action need to be at the launch point? or at the terminal popup point? If it needs to be at the terminal pop-up point, do we need to estimate the ship position, and launch precisely aiming at that point? I set up a mission with attack waypoint at starting ship point for AI, and at expected ship point for me....they got a hit, my missiles ran dumb. I tried again with their waypoint setup, and missiles ran dumb.

Developer has a nice tutorial, I might at some point try a Viggen computer. If I can manage to get it to work, I will certainly share with developer!

Is this excellent campaign compatible with standalone server yet? We tried a couple of weeks ago, and running from a standalone server would never allow us to get a successful mission.

A radar that actually works!

Here is the best screenshot I have readily available, most are 3rd person views. This is cropped about three pixels small on the width, as I discarded my Helios screen on right.

Yes that resolution does work.

Confirmed that it is a problem unique to Harrier. When Harrier slot is occupied, after approximately 5-10 minutes, no other players or AI are updated when cycling through F2, for any slotted players. When the client flying Harrier logs off, the server is immediately back to normal, as indicated by all other vehicles now being updated when cycling through F2. If anyone experienced this on their server, have you fixed it? If so how? Thanks for the help!

Confirmed, this is in 1.5.8 OB. It appears as if the right wing vortex is actually coming from right canard.

Sicario, nice job on the profile. Can you confirm the monitor resolution that you are using for the Helios screen? You stated 24" before, but can you tell us the resolution? The background image file is a nonstandard size of 2500x1444, and this aspect ratio (1.73) ends up making the image slightly off when Helios Profile Editor stretches to to a more standard 1.78 aspect ratio, like that seen on a 1920x1080 monitor. Again, thanks and nice job on the profile.

Still can't have clients slot into Harriers our our MP server. Any ideas on how to rectify this?

Any news on this issue?

Confirm issue with Harrier, in 1.5 OB and 2.0 OA My little dedicated server has run missions with 8 or so pilots no problem, before Harrier. In either OB or OA, if any player slots into a Harrier, after a few minutes all other players appear frozen, but your own position and status is updated. Have a simple mission with A-10C, Harrier and ASJ-37. When all slot into A-10, no issue. When one slots into Harrier, we have the issue. Thought it might have been data exports, but issue exists when exports are disabled. Would love to find out what the issue is, or if there is some configuration tweak I could try server-side.