Willie Nelson

I have noticed the same, I think it used to work but the datalink system was redesigned recently and that seems have broken this training mission. https://au.video.search.yahoo.com/search/video?fr=mcafee&ei=UTF-8&p=DCS+Viper+datalink&type=E210AU309G0#id=2&vid=cac597eb37ddb2495b6a4b327c682144&action=click I am guessing the functionality still is in fact avialable but because it works differntly now, wherby there are "Team members" and contributors which are not the same the demonstration in this lesson does'nt work.

I remember reporting that in this mission the altitude of one of the targets is spuriously set at 18,000 feet. It is still the case I believe.

@WHOGX5 That's really good info, thanks. So much to learn, so little time.

Thanks. It does seem a bit cumbersome.

Perhaps incorrect but not a bug….is that what you’re trying to say?

Thanks very helpful, so it looks like in fact it is as designed to be. I just need to understand the filtering better. That explains why the box was yellow although from memory I was able to TMS right between two yellow boxes. I’ll have to have another look when I get home. Thanks again for the detailed explanation, it certainly is very different from the Hornet.

Thanks for the response, can anyone else confirm this? It’s usually just my misunderstanding of how the thing works…….perhaps not this time.

The heading says it all, I am having trouble doing this. To be clear, I am in CRM TWS mode with several track targets (the larger filled in squares). I am selecting TMS right short (long switches back to RWS) and often, though not always, I cannot get these Track targets to switch to System Targets, although sometimes some do and some don't. Is anybody able to elaborate for me or do I simply need more sweeps of the FCR? Thanks in advance.

Just wondering if any of the fantastic freeware modules might have transitioned at some point to payware moduels. I think some of the freeware modules either upcoming or already in theatre are pretty good and I know that the benchmarks for ED to approve a DLC are pretty high for good reason, surely there has been one or two of these at some point....?

Since the last combined update that included changes to the Viper, it would now appear that the Mac D no longer indicates C for correlate above the weapon station, is this intentional or is this a temporary bug.

I guess that the rationale may be, once you find the vicinity with thenTGP, then you can keep selecting things with the MAV sight. Of course in practice this is ridiculous given the size of images on the MAV display. I’d like to know how the real one works. It does seem odd to have this set up.

Right you are, I should have titled this post with a different heading. I meant to refer to the D model (IR). I use them in a mission to take out tanks and they’ve started working the same way a described above and it would appear that Auto makes no difference, where as before it was a pre requisite to get a correlated lock (“C” above the pylon station displaying on the MAV page.

Not complaiing, just trying to understand the new changes that @Wags discussed in this post. To be clear, it does seem that I can get it working based on the method that Wags explained in this post: However it would appear that this means the "Auto" mode for hand off from the TGP to the Maverick is now redundant, am I understanding that correctly?

Oh ok. Thanks for that. Will do. Cheers.

Both of those observations are true and correct, that said, surely by now we have a more conventional way of turning of the Crystal.

Anybody else having problems with the Pimax Crystal not staying off when powered down whether being worn or not, whether switched off via the app or not. I have been in touch with Pimax and they say a patch will come out but right now I cannot watch any videos on the pancake screen without having to physically disconnect the Crystal. Wondering if anybody else is having the same problem.

So after much grinding and gnashing of teeth, a friend of mine was able to look into this for me and provided me what I needed to ultimately fix the problem. Enforce a 253 Watt power limit and disable multi-core enhancement. He did some searching around and said that some of the 14900 series is susceptible to a low I2 voltage whci can be tweaked at some other point.

Thanks for getting back to me so quickly with some suggestions. I cannot see anything to that effect (boxed or air) in the BIOS menu and I know that the Noctua NH-D15 has been tested and shown to be just as cool as many AIO cooler add ons when fitted correctly of course, which it certainly seems to be. Having said that, I am happy to try anything. In that vein, here is the BIOS menu options shown under the BIOS "Tweaker" menu. I have also attached a picture of the paste that I had on the CPU, I have wiped off the old paste (that was in this picture which shows it was even at least) and reaplied a slightly smaller amount. I then reconnected everything and I turned it all on, ran another session and it crashed again with Core Temp showing that the highest temp had peaked at 96 degrees C. Those temps are representative of what appeared in the crash log attached. I show all this becasue I am not sure which settings Turbo settings you're asking me to change. Perhaps this will help you to determine which way to go. Is there any other app that I could perhaps run on the side to see whether it is indeed the temperatures that are causing DCS to wig out. "CoreTemp" shows me high temps (which at least theoretically should be fine) but anything that might show the cause of the CTD if it is not coming up in the DCS log perhaps. dcs.log dcs.log.old

I have done as you suggested and created a ticket with a link to here. The BIOS is updated to October 23 as F28a for the AORUS Z690Pro

This is perhaps an aside but what's the rationale of dcs.log versus dcs.log.old?

In confirming the BIOS allows me to boot the USB "image" I have UEFI BIOS in my MS Config settings and the following images from my BIOS might show you a little more. When I select USB from the boot menu, the screen momentarily goes black, then instantly comes back to the same boot menu that you can see in the first image below. Withing the FAT USB there is a PDF document with instrucitons and an 'SRC" folder and a "SysLinux folder'

It's a Corsair RM1000e ATX variant. It is purpose built to accommodate the 4090 three conncetion requirement. in theory, it should be fine but there may well be some fault in it causing stability issues. I would like to rule out other lower hanging fruit first possibly , particularly now that I am at home for a few days with manflu. Again, do you have any theories as to why I might not be able to get the Memtext 86 to load from the USB that I have installed it on. It just keeps coming back to the boot menu without running despite me clearly following the installation and loading instructions.

I was fairly confident that in fact I had not overclocked this CPU! I see what you’re looking at, is that not the native setting potentially being displayed? I am informed by somebody that know more that me that there’s not a lot to be gained from OC ing a 14series Intel. With regards to the Memtest 86 do you have any guesses what I might be missing there with my attempts to run the USB image? I’m a bit concerned about setting anything to 115 degrees Celsius. :- 0

Ok, thanks. I’ll keep that figure in mind, I can do some geometry and work out my likely capture range from a given SAM safe altitude with that. Now if only I had some time to confirm your claim and not have to go to work!

Do we have any ideas on how close I need to be before I can reasonably expect that a lased target will be picked up in the event that the TGP is looking within the vicinity of whatever is being lased? I can make it all happen but it sometimes seems that I need to be able to see the whites of their eyes before a lased target will be picked up, perhaps I’m missing something.