Muskoka

Same as when I boresight from the pilots seat, nothing to see there. It's simply bugged and needs to be fixed. Sure, you can get it close, but nowhere near close enough. I can boresight dead on in about 10 seconds in the Pilots seat, front seat should be the same, yet it's a mess. And no amount of moving your eye point, viewpoint, fixes it. It's simply broken. No sense discussing it any further, enough people have reported the issue, it just needs addressing. Pilot seat Boresighting is a non issue, works as it should, very accurate, front seat is a totally different story, that isn't fixed by moving your eye/body position, period. The fact it's so easy to do in the Pilot's seat, yet is far off when in the front seat, should tell you something is wrong with the front seat Boresighting mechanics. The fix is a hot start, move to the front seat, and leave the boresight untouched. Then it's as accurate as the pilots seat after manually boresighting.

Works fine hot start, without boresighting. The guns as accurate as when I boresight in the Pilots seat. Anything to do with a cold start, and it's impossible to boresight in that front seat. Moving to the front seat after a hot start, and boresighting after George has done it, is also a no go, you'll never get it lined up again.

I can't hit a barn door 100' straight in front of me with the gun. In the pilots seat I can hit a fly from 1000', no issues at all. I only play in vr, headset is a Quest 2. I'm left eye dominant, and have tried setting HMD Eye Renderer to all three settings with no difference. One issue I do notice is that everything in the front seat is double if I use Both Eyes as Eye Renderer when trying to Boresight, although looking outside the cockpit is fine. I've adjusted the seat position untill I'm blue in the face, also makes no difference. Aim is still way off. How are you guys in vr aligning the Boresight from the front seat, I'm at a loss, and have spnet hours trying to get it sorted. Again, Boresighting in the Pilots seat works great, have no trouble at all hitting stuff with the gun, front seat, forget it. I see this post was moved. I posted this in Bugs and Problems, because something is wrong with front seat Boresighting in vr. Boresighting works perfectly fine from the pilots seat, and not in the front seat, thats a "Bug/Problem". The issue may be vr headset specific, which I'm thinking it is, but even that is a "Problem".

Yes, it is a issue, and should be fixed.

Hey guys. I've downloaded the BS2 Trial, and I'm playing around with the PVI-800, trying to fly to an "Airfield". I've gone through the Training, and all works fine. I'm now using a mission I created in the Nevada map. I've created waypoints in the mission editor, and have no issues flying on autopilot to any waypoint, 1 through 4. Problem is with an "Airfield". I have the proper coordinates for Nellis, and I've entered them in the PVI-800 for Airfield 2, correctly. While enroute to say WP 2, I'm selecting "Airfield" then 2 on the PVI-800, issue is the aircraft is not turning to the chosen "Airfield", it just keeps heading to the current "Waypoint". It's one of the steps in the navigation training and it works fine, I've no idea why it isn't working now, thoughts? I'm sure it's a step I've missed, but I've no idea what it might be. If I call up "Airfield" 2 on the PVI-800, the correct coordinates are displayed, 36 14.1 115 01.9, if that helps. I've also changed the "Units" for lat lon in the PVI-800. Reading the manual it looks like it might be a Mission Editor thing? I have to put a landing airport in the mission editor? To get to Nellis I guess I need to enter it as a waypoint in the PVI-800 , I'm assuming. Ok, still not working. I've entered Nellis as WP5, but the aircraft will not fly there. I see all my other waypoints have a red dot beside the longitude, the ones that were set in the mission editor, but wp5, the one I manually entered does not have the red dot lit up beside the longitude. Must be the problem but I'm unsure how to fix it. Edit: Sorted out. When entering the latitude I need to hit "0+", when entering the longitude I need to hit "1-", that's what I was missing, east west setting. It all works out fine, and the aircraft correctly flies to the manually entered waypoint.

This is my system of course. Find your saved games, and put the folder with the 2 files in the Missions folder. The 2 files are inside Winter_Bridgehead on my system. C:\Users\musko\Saved Games\DCS.openbeta\Missions\Winter_Bridgehead

Your points are also valid, but I disagree with one thing you said. The political weaponization of social media sites "does matter", and needs to end today, especially on Facebook. Everywhere you go on the internet someone is collecting data about you, it's how it's used that matters. It's too late to worry about whether it's being done or not, we're long past being able to do anything about it. But we can sure raise our voices about how that information is used.

Well said, and I agree with everything stated. People need to understand the motives behind this move by Facebook, and what they stand for. If political discussion isn't allowed here, then perhaps you should remove any post where Facebook is mentioned, including this whole thread. Look at the anger, and backlash this move has received. It's not just a general dislike of Facebook, it's a hatred of what they stand for politically.

Thank you.

I've had a few crashes as well in the A10C in simple missions I created. Sent logs in.

All sounds good to me, wallet will be ready.

My control profiles were "changed/different" after this update as well. Didn't notice until I took off of course, but I did have to reassign a bunch of things.

So, if there was a update available, and the utility wasn't updating, then asking a question as to why dcs wasn't updating using this utility isn't appropriate? Give me a break. Where would you propose I ask the question then, if not in the thread for the utility that does the updating? Surely you can understand why the question was raised in the first place? This site shows an update dated Aug 18, if it's not available, then don't post it. There was no need to "question" the validity of the question, it was most certainly pertaining to this app. If the update isn't available yet, then fine, I have no need to question whether the app is working properly at my end, or not. It's as simple as that. But when this site shows an update, and my update utility isn't updating my current version, I'm most certainly going to ask the question, in the update utilities thread. Is it really that hard to understand? And yes, the post is from today, but it's dated as available yesterday, even more reason for my original question. Here, in case you haven't seen it, the first few lines, dated Aug 18th. "DCS 2.5.6.53756 Open Beta 2020-08-18 https://www.digitalcombatsimulator.c...a/2.5.6.53756/ Introduced the new DCS: Syria Map by Ugra Media. Introduced two new campaigns: DCS: F/A-18C Raven One Сampaign by Baltic Dragon DCS: Mi-8MTV2 Crew Part 1 Campaign by Stone Sky"

And if the app wasn't updating to the latest open beta version that was dated Aug 18th, then the question is more that appropriate in this utilities thread. Give it a rest.

Ya, same as every other time I've updated, but it's saying the latest is DCS 2.5.6.52437 Open Beta, that's not the latest according to the updated list from yesterday. Why would they list a new version as being available yesterday, if it's not available. No need to answer, just seems pretty stupid to me.

Because I'm using this utility to manage my dcs install?

Guys, how do I update to the latest beta build from yesterday, DCS 2.5.6.53756 Open Beta 2020-08-18, it's not showing when I try to update? I'd like to use the Syria map I purchased.

Disregard, didn't see the post below. May as well ask the question. Mid August and still no news, when is the A10C grip going to be available? No interest in the F/A 18 grip, or Facebook, so if there's update info on Facebook I'll never see it.

Mines the same as Max above, no issues at all. Sorry, not much help.

Thanks, missed that on page 17. The manual step "Finish" is not working at my end. When I push "Finish" nothing is being sent to the windows clipboard. Once, out of maybe 10 tries it did, but only when I pasted the contents to Notepad++. Never when I try to do the manual step "Finish" from page 36 of the manual. Actually it's worked once, but I got a warning about "Large number of dynamic commands created" said it's going to create 20631 dynamic commands? Can you please also comment on "some" commands not working (mentioned in my first post). I'm doing my own jtac training in the A10C, and I'd like the ability to ask for the brief again. It say's in the manual, page 48, you can give the command "Repeat Brief", which doesn't exit as a command phrase, but I did try "Repeat", which does exist, but nothing happens in Dcs. The command is recognized as a good command in the va window. Should add, I have reset everything, except my keys.

The test does nothing, tried multiple times. I did reset everything except my keys, so debugging was back on. Didn't see anything that looked odd.

Hi Max, that's what I've been doing. Once out of maybe 10 attempts did the paste work, and that was in notepad ++, but never in the box where it should be in vaicom. I do run as admin all the time, just thought I'd try once without to see if there was a difference.

Thought I'd try the VSPX processing. When selected it gives these instructions. The paste function is simply not working. Multipart commands are consolidated, I delete the existing string of commands from the box, cursor is still in the box, try to paste but nothing is there. Even if you right click with the mouse in the box, the paste function is grayed out. Also, pressing the test button in the editor does nothing. It sits for minutes on end with no update in the va window, it's not doing anything. While I'm at it, I'm finding some commands don't work. For instance the jtac command, from the manual page 48, " In addition to these there are additional commands for JTAC, such as Repeat Brief, " that command returns nothing, although it's recognized in the va window. The brief is not repeated. I've found others, but I'll start with that, as it may be due to the keywords not updating when switching to VSPX? Tried with va run as administrator, and not, no difference. I have the Vaicom Pro license, with chatter.

Thank you guys for the answers. What I'm trying to achieve seems to be working fine. As long as TAD is the SOI when I hit TMS down long, the TGP is "locking on" to the target. I can see the camera view change immediately when I hit TMS down long. After takeoff, and getting closer to the target destination, I can see the intended target on the TGP display, at least very close to it, within feet I'd say. That's all I was trying to do, get the TGP display to lock on to the target before even leaving the ground. It seems to work. I can then fine tune through the TGP as I get closer, but I was trying to find out how to lock that view on the TGP to the target prior to takeoff, and like I said it seems to be working.

Trying to learn the A10C, been at it a few days. All is going pretty well, able to hit targets with bombs in CCRP. I've just been picking targets in the Tgp. Question is about using a predefined way point in the mission editor, which would also be my intended target, and thus it's my Spi. Lets say I create a mission with a single way point, that is also the intended target. This would be done in the briefing room before I ever get in the aircraft. I know this is going to confuse you, I'm confused. I've read that China hat back long will move all sensors to the current way point, which is also my intended target, therefore I want it to be Spi. If CHBL moves all sensors to the current way point, does it them become "the target", Spi. I don't think it's working that way, at least to my eyes. If the single way point / intended target I create in the mission editor is 75 miles away, CHBL sets all sensors to that way point, how do I target it when it's 75 miles away? I can't seem to wrap my head around how to do this. I've watched a ton of videos, but can't seem to figure out something that seems pretty simple. In my mind I should just be able to "mark" the way point on the Tad page to make it Spi, while sitting on the ramp prior to takeoff, but I don't think this is how it works? There must be some way to mark your intended target before getting in the air, regardless of how far away it is? Found this thread, looks like what I need to do? https://forums.eagle.ru/showthread.php?t=159074 Once in the air everything is working fine, no problems hitting targets. Still have to hunt for the targets in the tgp though, was hoping for a different method than trying to scan a tv image for the target. Still learning....