Jump to content

Phazon

Members
  • Posts

    17
  • Joined

  • Last visited

Everything posted by Phazon

  1. The sounds are still WIP and not all of them are complete or hooked up yet. The engine simulation itself is also still not 100% complete especially in regards to slow running, which certain sounds would rely on to trigger. Considering they have an original P-51 at their disposal I think this will be one of the best sounding DCS modules yet when its finished. :)
  2. I get it occasionally as well. HD6970 with latest 11.10 drivers. It doesn't happen very often so I just ignore it but wouldn't complain if it was fixed. :D
  3. Same here as well. HD6970 + Windows 7 64-bit.
  4. I like it. The overall level of quality now matches the DCS A-10C module, and various things have definately been tweaked and polished under the hood even if its not immediately noticable.
  5. I noticed that Black Shark 2 like the A-10C module has shipped with a in-built key assignment profile for the TM Warthog, which helps make it easier to get in the game. I cannot however find a picture reference card in the documentation showing what the bindings have been set as? There is one provided for the X-52 but not one for the TM Warthog? Was this just an oversight? Is is possible to get a picture card for the Warthog as well? Thanks.
  6. In-mission briefing will have radio info if mission designer types it in I think.
  7. Ah ok, thanks for the clarification regarding what BDA means. In that case looks like JTAC gives you a BDA after each run automatically, so the Report BDA command seems redundant in that case.
  8. Contact radio command is for confirming targets with JTAC though isn't it? To make sure what you have set as SPI is the intended target? What we are on about is that JTAC does not update you of your target's position as it moves away from the initial area reported in the 9-line. I would imagine in real-life a JTAC would do this if he knew his target was moving away from the target area. Not only that but the Report BDA (bearing, distance altitude?) command doesn't work, so if the pilot specifically requests for an update to his target's location he can't get it. I'm going to report this in the AI bugs section because it wasn't fixed for the 1.1.0.9 patch and I'm not sure if its ever been working at all since the game's release.
  9. Yeah sorry you're right, I normally only use the TAD to designate SPI in combination with a target location given from JTAC so I got confused. GunSlingerAus you will have to set a markpoint by pressing TMS Right Short after placing your TAD cursor on the area you want to set a SPI at, turn the rotary switch below the CDU to Markpoint mode to display markpoints on your TAD and then you can the use TAD to designate a SPI.
  10. Your TAD cursor is "hooking" the waypoint, which means if you create a SPI it will be placed at the set altitude of that waypoint. To set the SPI at the ground you should move the TAD cursor just off the waypoint until it is no longer "hooked" (it won't display coordinate etc locations on the TAD anymore). Edit: Try using the "None" profile on the TAD (its one of the top-right OSB buttons), from memory I think it declutters the TAD screen and hides waypoints so you can freely place your SPI without accidentally hooking something. When you set the SPI it should now be placed on the ground. I've only just recently been using the TAD to set my SPIs and I've gotten it to work fine, as long as I keep the TAD cursor off waypoints so it uses the ground altitude.
  11. Just tried to play a big random-gen mission tonight, got frustrated by JTAC (well actually 2 A-10s setup as AFACs) giving me targets but not updating on their position. The units move quite quickly so by the time they are finished giving their 9-line they have moved away. This is starting to get frustrating now. Report BDA is broken and does not work, and the JTAC are just not dynamic enough to update you with the intel on their own. Combined with the fact I had targets behind trees which does not help. Trees are starting to become more frustrating than they should be, they show up on the FLIR as if they were on fire!:helpsmilie: This sim is great on so many aspects but now I've started using more of its systems I'm starting to find things that just don't work as they should. We are mostly past the bug-fixing stage now in regards to patches, I'd like to see more effort now in polishing the sim some more to really turn it into the ultimate A-10C sim. Having the Report BDA function at least working would be a good start I would think as thats outright broken and is a big hit for using JTAC against a moving target.
  12. I agree 100%. I have turned off all labels and have now only just started using JTAC in my missions and I've quickly found out how useless they can be when attacking anything other than static targets. Technically JTAC is supposed to have a function of updating us of the target's status (Report BDA) but I can't seem to get it to work at all. :( Here's what it says in the manual: Maybe it only works when JTAC is in Type 1 or 2 mode where they are closer to the target I'm not sure but everytime I've used the command I don't get a reply. I would also imagine that a JTAC unit would be smart enough to update the A-10 pilot if the position and heading of his target changed significantly in real-life without him having to request it. Would love to see some improvement here. I also agree that AI wingmen could be way more helpful than they are currently. They should be using the message system and the TAD to send out points of interest and enemy locations ontop of just calling it out. Haven't used it before but I'm guessing the TAD has a function to send locations to wingmen much like how JTAC will send you the target location on your TAD? In regards to the visual side of things, I'd love to see more effects on vehicles such as engine exhausts and so on. This would then stand out in FLIR. Also I think the terrain is not "grey" enough in FLIR that it seems to have too many hot spots. The texture of the terrain shows up too much in FLIR when I would have thought it would all be a dull colour regardless of details of the terrain. This is how I've seen FLIR simulated in other sim games (ArmA 2) and it makes more sense to me. That said I'm getting better at identifying targets as I put more time in the game. The real pilots have an easier time though I'm sure!
  13. Glad to see I'm not the only one who has had trouble with Mk-82AIRs. Much appreciated if Matt could possibly make a short video to explain proper use? :)
×
×
  • Create New...