raus

@MicMic I am currently reviewing a potential bug with the commcard, so I'll double check. However: - Do not pay attention to the frequencies appearing at start, only when you select a flight from the .miz will it be populated with the retrieved frequencies - UHF/VHF is a viper thing, other planes have two (or more) UHF-capable radios. Therefore, it is not enforced in the .miz for the second radio to contain only VHF frequencies - The moment you export the commcard (if the tick is marked on the top left corner), it will overwrite the .miz with the frequencies selected. It is not evident until you reload the .miz, so selecting another flight might lead to confusion... I am trying to rework that part. BR raus

Yes, I think I explained in the video, as I create a Common Commcard... but maybe I missed it: - When you have a Comm card created, and you export it, it will overwrite all Human flights with those frequencies. Therefore it is a good idea to fill in all carriers/airfields involved in the mission, so everybody has their frequencies stored. Regarding the Tomcat is more a limitation on the way we usually operate: the pilot will select the interflight frequency in his radio, and the RIO will manage changing between Tower, AWACS, Tanker... on his. Therefore, we needed a frequency reachable in the front cockpit radio.

Hi @iantron Let me answer... 1. You are right. I will look into an option to "lock" the commcard. However, as workaround, if you export the commcard, it will overwrite the values for every human flight with what is present there... Now, what I am not sure is if this is reloaded, or you would need to re-open the .miz. As I just said, I will look into it and improve it for next version 2. This is due to our GV5Js standard, where we use 138 and subsequent frequencies for inter-flight, but 265 for Tomcats due to radio limitations. I will however check, as it currently supports a single Tomcat flight.

I've never seen that happening, but I would recommend you to uninstall, and then install from scratch with the latest link (first post), although it will take you to update again... Just check your .NET Framework installation (4.7 required, minimum, although should get triggered by the installer if you do not have it), and do NOT launch it as admin (experienced some issues in the past, and it is not required). Let me know if there are any other details/messages, and I will meanwhile try to replicate the issue.

I can confirm that. Yesterday we flew a MP sortie and one of the flight members did not have the liveries we were using, so he might have selected something different I did not have... and I was seeing him exactly like the picture posted.

Hey, @BIGNEWY I appreciate the action. It is always good to have confirmation in either way, as much as we hate to hear some news, even though I understand they might be needed for business continuity. However, even when those weren't the exact words or phrasing, I clearly remember that was the spirit, and I think mostly everybody would agree to that. Not trying to be nitpicky, but if we were to go by what was exactly said, we could also argue that: Which clearly is not the case, as the Hornet has not yet left EA. That being said, I understand it would do nobody good to leave the developers in the Hornet, and leave other modules unattended. I could even accept (I know many people wouldn't) Hornet already leaving EA, as it is, when there was a firm promise of a roadmap being completed later on (with a given list of features). I, anyway, have other modules to employ my time into, and enjoy them... but we should also think in people that purchased the Hornet based on some assumptions, when there was no viper, no Apache... and now are left aside... No hard feelings, and I'm not trying to pick on you. As I said, I appreciate the effort, and if you come back after checking with Wags to share some bit of "official" info, it will be more than welcome

@BIGNEWY this is honestly disheartening. IIRC, when @Wags announced some viper HARM features, he was saying this level of simulation would be later coming to the Hornet. Also, I think we all understood the whole concept about things developed in the Hornet would make viper progress faster, would be a 2-way road, where eventually the Hornet would also benefit from viper development. Don't get me wrong: I have no problem with the EA scheme. I do have patience and understand things take time. But falling short on well known and documented features, that are even made available for another module feels wrong. Id have absolutely no issue if you were saying "I can't tell when will this feature come to the Hornet" or "It will still be a long way until we can put manpower back into Hornet to bring these kind of updates"... but just telling it will simply not happen, as it is no longer planned... well, bummer I know the CM take flak whatever they announce, and that is impossible to keep everybody happy, but it feels that we do not get any update on what is yet to be expected for the Hornet, and neither on when could we expect anything. And, when we get an update, it is just to communicate things that won't be done...

Ok, after some days polishing the new features, I've managed to create a tutorial video (english version... although there's a spanish twin of this tutorial in the channel, as well), explaining the use of the application. To use as an example, I created a multiplayer mission with DCS Liberation, and created the datacards for the Package with the Datacard Generator... feel free to visit and comment in YT, if you have any doubts/suggestions (of course, any like/subscribe is very much welcome!). Enjoy!

@King39 I am sorry to read that. Actually, I have not been able to replicate the behavior of your system, but still looking into it. I have made a couple additional modifications that coul maybe mitigate it. As far as I can guess, it looks like the program is not actually minimized, but rather set to a wrong location, outside visible area of your monitor. It could be due to being closed last time with a different monitor arrangement (the program remembers its last position and size, and tries to open again in the same location... which could lead to it being out of bounds, if you have less monitors than last time). I would suggest you to give a try to this last version, where I've been working on a different layout. It is also worth mentioning that this could be recurrent when you update, as the settings of size/location of the winfow are not carried over between versions, sorry (hint to myself for future improvements) Aside from that, I was opening this message to mention that I've updated the program to v1.5.0, with the possibility of having two tabs on screen at the same time, as well as using it with Red Coalition missions. The link and -to some extent- feature summary on the first post have been updated. But you can always update via the program, directly. One (maybe more) english language tutorial videos will appear on Youtube shortly. I will drop a message here when able to edit them. PS: If anyone experiences the issue with the program appearing minimized, but not able to bring it up, I suggest to try the following: hover the mouse over the Task bar icon, so the mini-preview appears. Click on the minipreview to ensure the app has focus. Then, press Win+arrow left/right, several times, until the app comes to viewable area. And of course, let me know, so I can have a look into it. The hardest bugs to fix are those you're not aware of

@Tripack I hope both issues have been fixed. An update is available already

I have already fixed the frequency. Whenever there is a change it is hard to realize and keep track of all frequencies…feel free to drop a message here when you find a wrong one. regarding the WPs I just noticed the same. As a workaround, make sure all WPs have a name. I will try to fix it real quick and push an update.

Glad to hear that!! At the moment, the checklists are hard-coded, although I might include an option to parse a given folder for checklists in an upcoming version, good idea!! Anyway, I I am trying to get some time to expand the checklists section,and next in the queue are A-10 and M-2000. If you have some specific checklist in mind, feel free to point me in that direction, so I can make sure that content is included when I put it in the app format (I like all the pages generated to be consistent regarding formatting)

Just updated to v1.4.0, with the following changes: v1.4.0 Changelog: [Feature]: Added automatic trimming of Waypoint/Airfield names if overlap with next field is detected (when name is highlighted orange, there might be overlap) [Feature]: Added a 6th Inter-flight field in the commcard, with flight selectable in the General tab [Feature]: Added another row in the Package section of the Mission Data Card, raising the count to up to 5 flights [Feature]: Added a selection field, to use GV5Js standard RAMROD words [Fix]: if MGRS coordinates selected, export WP info to Notes1 not working [Change]: Marked option "Use std GV5Js frequencies as default [Change]: Changed default Coordinate system to DD°MM'SS.SS" [Change]: Increased size of Joker/Bingo texts [Change]: Aesthetic changes to the app. Eliminated non-selectable branding in the exports and maximized cards area, streamlining card design [Change]: Harmonized file export names [Change]: Cleanup of app resources, to improve efficiency If you cannot upload through the app itself (very old versions only), the link in the first post has been updated

@King39 I've met another occurrence of your issue. In this case, the user had, somehow, managed to get the app closed out of the screen area (maybe 2nd monitor? Some VR glasses create several virtual monitors, that could lead to this behavior). When this happens, the app will remember the last position where it got closed, next time you open it, so it might be a orblem. 2 potential solutions: 1.- Right click on the taskbar icon and select "maximize" 2.- Try this (after selecting the window on the taskbar, to make sure it has the focus): Move Windows Using The Keyboard Shortcut Method If you want to move a window to a display located to the left of your current display, press Windows + Shift + Left Arrow. If you want to move a window to a display located to the right of your current display, press Windows + Shift + Right Arrow.

Well, I am not quite sure what's going on there. Might be due to .NET Framework? Please just check you have .NET Framework 4.7 (IIRC, will check later when at home) properly installed. I will also check some debug capabilities and come back - hopefully - with some ideas.

@Steel Jaw : Had no issues with autoupdate here... however, link is updated now

Thanks for the clarification. All RW first hand testimonies I could gather were for the old (even if updated) APG-65... Anyway I had doubts that APG-73 would have been a step backwards

Did I (please say yes!!!) miss some update? Even though I concur on the aforementioned issues, I still find the most annoying one to be the ease with which tracks are lost when slightly beaming. I just cannot think loosing a tanker 15-20nm off your nose, at the same altitude or even higher (so no ground clutter against which to blend) is normal. It geta on my nerves when CAPping hostiles come and go so easily… but if that’s the way it is IRL, I am happy to stand corrected

Hi guys!Just starting my journey with VRK and a brand new Intuos S tablet... I am really enjoying it so far!!! However, I have 2 questions, and I guess this has been answered already, although I could not find it: 1.- It seems VRK misses some strokes, even though other apps with my tablet don't... what might I be missing? 2.-I am using a G2 VR headset and I need to look very much down to focus the kneeboard... any option to move the reference point, so that I don't need to break my neck?

Yes, I had two different targets on STA8 and STA3 PP1, and another set of two in STA8/STA3 PP2. The problem is that all of them went away

Hi guys, a couple days ago, we flew a MP mission, where a flight of 4 Hornets was doing an attack with GBU-38 in Pre-planned mode. Each of us had 2 targets, plus backed up 2 of another flight member. We carried 4 GBU-38 each. During startup, we carefully entered the coordinates. We used PP1 for our own tgt, and PP2 for the backup. Long story short, there was a lot of oposition and we could not commit directly to the target site. I went refueling at a nearby field and, after refueling took off again and headed for the target, just to discover all my PP coordinates were empty!! (Worth noting that in my previous attack attempt I had target symbology and everything was OK). I thought there was maybe a byproduct of landing and refueling/rearming, but later on checked and other flight members had also lost their PP coordinates, without landing. I don‘t want to file a bug because I do not have a valid short track (over 1.5h of MP flight), and I was not sure if this is already reported. I could not find it using the search function, though. So my question is: is this a known behavior/bug? Is there anything I am overlooking? Thanks!!!

Such a pity...

Does this mean that we should be able - maybe through the DTC- to: Draw lines (FLOT) Draw exclusion (No-fly) zones ... This would be really helpful, from my point of view. The possibility of having images of DPTCs, would be the cherry on top