Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Fred00

  1. I'm trying to make an SKU fix type 1 but I can't get it to work. I'm in SPA master mode, press LS/SKU button, radar trigger to T1, cross hair over target and hit TV, and nothing happens. No S1 is saved when I press "1" on the keypad. On the other hand, MÅL mode works as intended. After I've made the target fix, M1 is saved at position one and I can transform it to S1 by double clicking LS/SKU button and then proceed to make the second fix after 3 minutes. Have I misunderstood? Shouldn't it be possible to make an S1 point directly without first making an M1 point and having to transfer it to the SKU layer?
  2. First, after pressing L/Mål and hitting T1 the crosshair on the radarstick works as I have configured it in the control settings. Then, after converting my M1 to S1, I hit T1 again to take the second fix. Now the Y-axis on the radarstick is inverted, so if I previously pressed up to make the crosshair go up, I now must press down to make it go up. That has to be a bug right? @IronMike
  3. I mentioned this several years ago but coming back to the Viggen recently I noticed that it is not fixed yet. Such a simple thing to fix, yet so annoying when flying the module. 1) The weapon selector dials rotate left with a right click while the TILS selector rotates the opposite way. 2) The two radio knobs rotate in the opposite direction to each other. To make things easy I think all dials and knobs should rotate in the same direction. Preferably they should rotate right with a right click and left with a left click. Please fix this with the next patch! @IronMike
  4. I’ve been there and I have crawled through there too. The thing is, it is not big enough to walk, you’ll need to crawl (or at least squat). Either way, it’s quite cool.
  5. I'm trying to get a grip of the offset feature of the TGP. I'm running the instant action mission "GRound attack practice" for the Syria map. I slew the TGP cross hair over a target, go into ATRK (confirmed by display), hit TDC depress, and nothing happens. The little movable cross does not show. If I'm doing the same on point track mode it works like a charm. The cross appears and can be slewed around. Anybody else have this problem? Also, I'm wondering what's actual point of these functions are in DCS? Why not just use "normal" mode where you can slew around? ATRK mode, where the TGP is not slewable seems uttlerly pointless (unless I'm missing something).
  6. Thanks for the replies guys. Will have to work around this until it's solved.
  7. I'm learning JDAMS and I have two JDAMS loaded on the same station. There are two slots TOO1 and TOO2. First I use WPDSG to load the coordinates for target one into the TOO1 slot. I then switch to TOO2, change waypoint and press WPDSG again. When I go back to TOO1 the coordinates are erased from that slot. Only TOO2 now has coordinates. Why are there two TOO slots if they can't be programmed for different targets?
  8. Yes, but if I fire a Maverick, can I get the next one to slew directly to where the HUD TD box is pointing (ie where the previous Maverick was first ground stablized)?
  9. So I'm in Visual mode and I have designated a point with the HUD TD box, I press TMS up to ground stabilize. I slew the Maverick onto the target, lock it and fire. How do I get the next Maverick to slew directly to where the HUD TD box is? If I press TMS aft the TD box is boresighted and I have to start over again. If I'm having several targets in the same spot it would be handy to be able to slew consecutive Mavericks to the same spot.
  10. You are correct. I just tested again. Two TMS presses are indeed required to lock the target. Also, as you point out, after the first press nothing actually show that the target is now a system target, apart from A2 and 3 bars. This means that it is not practical (or even possible?) to mark several system targets when datalink is involved, because you will not be able to tell which are system targets anyway. It's nice that this behavior is confirmed, although the difference in meaning when it comes to hollow/solid tracks depending on whether datalink is used or not is a bit confusing. Yes, this is correct. Thanks for the clarification. This behavior is not very clear in the manual I think. Or am I not reading it good enough? Maybe the radar will be discussed more thoroughly when the manual is finished for release state.
  11. When using datalink a hollow symbol will just indicate that the target is only seen through datalink and not with your own radar. A solid symbol indicates that your own radar has also picked up the target. Solid vs hollow seem to have no connection to track vs system file.
  12. I will test again when the kids have gone to bed. I'm using the instant action mission "Fighter intercept" to test this btw. Okay, but how is it shown that the target is made a system target after the first press? For non-datalink correlated targets you get an hollow symbol, but clearly that's not the case for datalink correlated targets. Just wondering what I should look for?
  13. The problem is that right now there is actually a difference in the locking procedure. Non-datalink correlated contacts are turned into system tracks with the first press on the TMS. On the second press they are locked. However, datalink correlated targets are locked directly with the first press on the TMS. This indicates that either the "system track level" is skipped for those contacts, or that all datalink correlated targets are per definition already system targets. In the case of the latter, why are the datalink correlated targets not switchable by TMS right? No, I understand all that. See problem description just above this quote.
  14. Yes, you're correct. I saw the bug report after a little bit of searching. Thanks.
  15. Okay, so then it's a question whether datalink targets are shown as track files or system files. It seems to me that datalink contacts are shown as track files only, and TMS up is immediately bugging the target, skipping the system file completely. If datalink contacts were actually system files we should be able to cycle between them like we can with regular system files (not using datalink). That is what's confusing, and it's not explained in the manual. Should we just accept that the concept of system files are not used with datalink supported radar contacts? It would be great to have it confirmed.
  16. Then we get the following problem of symbology: When NOT using datalink: TWS track files have solid symbols. System files have hollow symbols. When using datalink: Targets that are only from datalink have hollow symbols. Targets that are also painted by own radar have solid symbols. Accounting for the above, it's clear that system files must have a separate symbol/designation when datalink is involved, since the hollow symbols are already used for another purpose.
  17. I have noticed that I can increase brightness on one page, only to switch page and see it going back to dim. Is this a bug? It seems like uneccessary work to set brightness on several pages separately. I can understand regarding the TGP, but the other pages should have a "global" setting right?
  18. I have just recently started learning the F-16C, and one thing I don't get. If I have non-datalink targets on my radar, I can enter TWS and choose system targets (all, or pick those I want). However, if I'm having datalink targets which are also painted by my own radar (solid red triangle targets) I can not assign system targets. If I TMS up with the cursor over a target it is immediately bugged. If I TMS right, the closest target is bugged, but further presses do not cycle targets. Is this correct behavior? That is, targets can only be assigned as system targets if only my own radar sees them.
  19. I've been having the exact same "problem". The F/A-18 is no doubt the sensible choice, given the current state of the modules. For me, who is more geared towards A-G than A-A, the Hornet is probably also the better choice. However, I'm not crazy about the way the Hornet flies. I can't really put my finger on it, but I feel the F-16 is just more fun to fly and generally feels better in the air. I'm also not very fond of the HOTAS integration in the Hornet and the UFC/MFD integration which feels a bit clunky. I think rational arguments are only a part of the decision. How the plane feels and how you like the cockpit and plane itself is probably just as important.
  20. The console lights seem to be way too dim. The problem is that even in daylight the shadows in the cockpit seem too dark (a problem shared with many other modules, for example M-2000C) and turning on the console light does next to nothing. I have a hard time believing that they are this weak in real life. It should be a very simple task to allow us to turn up the lights higher.
  21. I've noticed (coming from the Hornet) that the A-10C MFCDS are alot fuzzier when reading text. The Hornet with the same gfx settings is alot more readable and sharp. Is this a feature or is it something that should be looked into? Even if the real A-10C has fuzzy text maybe it would be better to sharpen them up in game, to make them easier to read.
  22. Works perfectly. I have to say though that the old cockpit didn't look as good as I remembered, even after turning on Ricardos HD textures. Back to the new one and it just has a better look to it, hard to put my finger on why it looks better. The new weathered cockpit will be very exciting to take a look at when it arrives!
  23. Yes, I own all of them and have not noticed the same problem with any of them. Maybe the A-10C is modelled to a higher fidelity? I have to say though that it is annoying when the aircraft starts to bank just seconds after having started in the air. One would think that it could at least be trimmed out when starting.
  24. So I've seen some people (for example NineLine) talk about the "retail" version of the A-10C. How will that work? Will it be a completely new module that those of us who already own the A-10C can buy at a discount? Will it feature a nicely weathered cockpit like the Hornet? Any other upgrades? When will we get some more info? :)
  • Create New...