NightstalkerNOR

Hi. I've been having some problems with the Maverick. 1: If I have both the E and F versions with me, I can only use one of the types. Firing one, makes the other version unavailable - cannot select it in the stores page. It's still in the stores page, but nothing happens when I click it. 2: The image on the F version sometimes only shows a blank IR image. I can still adjust range, and slew the target indicator, but the image doesn't change. This happens even after the cooldown period is out. Any similar experiences/advice on fix?

aaah. Alright, thanks :)

Hi. I'm having issues using the mk20 ret clusterbombs. I've used both CCIP and AUTO and the bomblets always hit way off target. Any tips in using these types of bombs? Thanks

Rgr. Will see what I can do.

DCS reinstall did not work

Campaign reinstall did not work Will try DCS repair...

I am not using Icontrol DCS. I've tried a reinstall of the campaign, and will get back to you when I've tried the refueling mission for the 10th time. I'm starting to get the hang of aerial refueling with all this "free" practice :)

When I touch down at Kobuleti I get a notice from the examiner that I should take the first right, then the first free revetement to the left. I do this, and after that I do not hear from the examiner again. I shut down completely with all systems disengaged, and battery off.

Hi. I'm having problems with completing the AFT02 - Night refueling. I keep completing the 3, 10 second refueling tasks, and landing safely at Kobuleti. However I do not get a feedback of my flight (neither did I on the AFT01), and I also get disqualified. I've been taking off on time, and reaching all waypoints on time. After landing at Kobuleti, I run down to end of runway 07, take a right and then left as adviced by the examiner. Any advice on how to proceed to AFT03?

Update to this problem: I think I now have figured out the issue with this. With the TGP on, and the TAD on normal 160 range (?) everything is normal. However, when adjusting the TAD to look more forward, with 240 range, the TGP image suddenly slews down, as if the TAD image is "pushing" the TGP image out of the MFD frame. The attached images demonstrates this. Please check both left and right MFDs. Any ideas?

After some testing, it seems the problem only exists when loading a premade mission. If I start on the ground or in the air, and I made the mission myself the issue is not there.

The repair did not work, I'm afraid. Still have the pointer in the TGP floating above ground level, and the limited, cut, view.

This is not the issue with my case. I am flying within the attack angle of the TGP. The issue is as stated above, limited view in the MFD and the TGP not focusing on ground level. Thanks Scratchy, I will check it out

Faelwolf: How do I repair a module?

I'm having a couple of issues with the A10' TGP in DCS 2.0. First, the view in the MFD when selecting the TGP is restricted due to the corners beeing greyed out. It the same as in this thread: http://forums.eagle.ru/showthread.php?t=154233 Second, when I have found a target, the TGP does not lock on in point mode. It seems that the focus point is focused a bit above the target itself, as if I've slewed the TGP to a waypoint that is not in ground altitude, but maybe at 100 feet above the target. This also means that when circling around the target, it loses the target in the MFD picture due to the focus point....not focusing. I hope you have any suggestions for me. PS: I see that there is a dedicated forum for bug reporting. If admins could move the thread to it, that would be great.

My computer is not doing to good at the moment and even starting at safe mode seems to be impossible. I managed to access the desktop in safe mode once, but the file was not to be found. There are several issues popping up every now and then so I see no other easier solution to this than to format the drives and start from the beginning. Hopefully that will reveal the cause of my problems, if it's hardware or software. I will let you know how it goes. Thanks for your ideas so far!

Now I´ve encountered a problem with the graphic card driver. I am unable to see anything on the screen as soon as it enters the loginpage after restart. Therefore I am unable to share the minidump file......

I encountered a problem yesterday. My DCS causes total computer shutdown (I guess it's called Bluescreen) when ingame, and this is happening everytime I start a flight. When in cockpit, it takes maybe a minute or so (will try to identify when and under what circumstances the crashes happen) for the computer to freeze, screen turn black, sound stutter and then the crash. The crash report look like this: Problemsignatur(e): Navn på problemhendelse (Name of incident): BlueScreen OS-versjon (version): 6.1.7601.2.1.0.768.3 ID for nasjonal innstilling (ID for national settings): 1044 Tilleggsinformasjon om problemet (additional info on the issue): BCCode: 116 BCP1: FFFFFA800A054010 BCP2: FFFFF8800FD1D630 BCP3: FFFFFFFFC000009A BCP4: 0000000000000004 OS Version: 6_1_7601 Service Pack: 1_0 Product: 768_1 Filer som bidrar til å beskrive problemet (files to help describe the problem): C:\Windows\Minidump\011513-12043-01.dmp C:\Users\Vetle\AppData\Local\Temp\WER-13650-0.sysdata.xml I've read up on previous, similar issues, but I can't find anyone with the exact issue, but several are saying this might be a hardware problem

Yes it did. works perfectly. I have activated the "easy communications" in options as well, but this was activated before also, so just reinstall and see if that works for you. Should be noted that all "DCS World" compatible addons should be removed together with DCS World itself, just to be certain that all files are reset. It took me the download time of all install files + 3-4 minutes to get up and running again (considering you have saved the keyboard/joystick settings), so for you FSX flyers out there "scared" of reinstalling and using almost a week to get back in business, this is not an issue here.

Reinstalling the game seems to have solved all and more issues that didn't even know where there. The other issues were such things as Cloud coverage, Missing TAD MAP, MAP Coordinates (both the L/L and MGRS coordinates were somehow set to be way off from from the Georgia/Russia area) and more. I do however not have any clue on how this might have happened, so it remains a mystery, but atleast it has been solved for now... Thanks for all fix suggestions on this issue.

oh well, I guess using the "swedish solution" on this issue -reinstalling the game- is the next action I will take. I will let you know how that goes. thanks for the help anyway

1. I can't see where this issue would be of use so I think that this must be a bug of some sort. It is the most problematic issue of all three since it makes the engaging of targets harder being forced to use eyeballs, and also tricked into believeing the target is somewhere else that what it really is. 2. The weird thing as that this was working perfectly before, no problems whatsoever, but suddenly without warning it desides to not work... 3.What I have done to test this issue is to both try the Bactria mission and also flying in the mission editor, typing in coordinates that I find through using the F10 Map. It works with inserting coordinates when flying a self-produced mission through mission editor, but the Bactria mission this approach doesn't work. I see your point that there might be some problems with the coordinates that you recieve during the mission, that this might be a mission fault, BUT with my brother also flying the A10C, has not experienced the same. With him this works. We've also tried a MP mission other than the Bactria, and also here the coordinates are wrong. We ensured that both the 38T (or whatever it was) was correct, and that it was input correctly with alle numbers and letters the way they should be, but nothing showed.

Hey and thanks for your responses. 1. See if these images work. This situation is as it should be. I have not yet assigned the target as SPI so that I can drop CBU, guided or unguided bombs onto the target, but I have identified the target with the TGP and are ready to assign it as SPI. Here you can see the where the TGP is looking with the Diamond indicator slightly down to the left from the middle of the HUD. The waypoint "box" is slightly up right from the middle of the HUD. The target through the TGP is assigned as SPI. The TGP Diamond then quickly repositions itself to where the Waypoint box was previously located. The TGP is still looking at its target, but the TGP Diamond now indicates that the TGP is looking somewhere else. If this was first engagement of the target, meaning I would not know their geographical placement and no smoke from destroyed vehicles, I would now believe that the target is placed to the right of me, leading to a right turn. You can still see that the TGP is looking at its target, but that the Diamond in the HUD indicates that the TGP viewpoint is to my right. When reaching the point where the Diamond reveals the location of the target in the HUD, the diamond disappears, and jumps over to the left, now indicating that the target is to my left. Turning left towards the diamond indicator results in the same as above that the target is supposed to be revealed but instead it jumps to the right, indicating the target is to my right. . 2. I've tried checking my COMMS controls through the settings, and they are recognized, however they do not work within the sim itself. 3. What you describe with the L/L and MGRS was also my first thought. Also the 37T /36T/38T have been checked. They are both as they should be, and I have followed an example video on youtube to the letter. The video describes the exact same situation on the mission OP Bactria, with ground forces giving coordinates that start with MN and 10 digits, so it is fairly easy to check and double check my own and the instructors inputs in the CDU. The thing is that it worked for me previously, but now I end up as explained in the original post, with the waypoint beeing indicated to be over 1000 nm away, and not able to find anything near MN in the F10 map, only XY, ZX EZ and so on.

Hey, I seek help in trying to solve some issues with the A10C Simulator. I have tried to explan them as best as I can, but I might have come with too much info. Please do ask if something is unclear. My configurations with HOTAS, and Keyboard settings within the sim have not been changed in a while (around a month), and the issues occurred, without me making any, just in the last two or three days. It was working perfectly before. 1. When finding a target with the TGP, and assigning it as SPI with the TGP as SOI, the TGP "diamond" in the HUD moves over to the position of the waypoint in the HUD. However, if flying straight towards the SPI assigned TGP so that it should show in the HUD, the TGP "diamond" disappears, leaving no clue in the HUD to where the TGP is looking. Imagine a situation where you have assigned a target as SPI through the TGP, you steer towards it, but as soon as the TGP diamond is supposed to show in the HUD revealing the target infront of you, it disappears and then leads to using the "Mk1. eyeball" to recover the location of the target The funny thing here is that the TGP is still looking at the same target in the MFCD, but there is no way to know where, since the TGP diamond is gone. It is possible to reset the situation by setting the TGP in standby mode, or make it look forward without being locked to a target. Notice that the red circle shows TGP Diamond, Blue circle shows the waypoint, Orange box shows target in Right MFCD Notice here that the TGP Diamond (RED) has replaced the Waypoint box (Blue), but that the TGP is still looking at the same target. 2. The second issue I would like to bring up is the comms menu. Same as the previous issue, this was working perfectly before two or three days ago. Suddenly the comms menu will not show, not through the keyboard, nor the joystick. I have tried to make all assignments go through HOTAS, and also reassigning the keyboard settings, but no response, making the use of JTAC, wingmen or similar impossible. 3. When flying some missions, for example OP Bactria or similar ( excellent mission! ), you will recieve coordinates underway which you have to add into the CDU. The MGRS coordinates may look like this: MN 68779 19146. However, when typing this into the CDU I get no waypoints showing in the TAD, but the HSI indicates that the WP is over 999 miles away, meaning that the WP has been entered into the CDU, but is not within the map itself. The problem is as mentioned that the coordinates are entered properly, and this worked earlier, and still work with others that I know, but now they are way off with me, and do not show in the TAD and I do not know why. I checked the map and the MGRS coordinates around the whole map using F10, and I found no such coordinates beginning with "MN". The strange this is that this worked before, but not now...