Jump to content

oldcrusty

Members
  • Posts

    2059
  • Joined

  • Last visited

Everything posted by oldcrusty

  1. Yep, I see the bug now. It can be reproduced on any waypoint already in your NAV database. Select waypoint (doesn't matter if WPT and/or 'SEQ' are 'boxed') Go to HSI-DATA and change waypoint's ELEV from meters to feet. Back to HSI page. Press WPDSG. Everything looks good there. Confirm your target desig. on FLIR. Now, go to DATA again. The designated waypoint numerical value is in meters now but... FT is displayed next to it now. FLIR still shows correct target. If you undesignate and designate again, that's when the trouble starts... Every re-designation, converts the elevation again, so... for now might as well stay in meters.
  2. No. I've just tested a similar setup. All LDDI buttons worked fine, including HARM. As far as WPT ELEV change, there was no error. Well, I didn't do it exactly as you did in your mission. My WPT was set at the target elevation at the start of my mission. I designated it (WPDSG) then undesignated and unboxed the waypoint sequence in order to test the WPT elevation change. Once the change was done, I re-designated the WPT and the new elevation showed correctly on both, WPT DATA page (in feet) and the JSOW mission page (in meters). All done in SP custom mission.
  3. Amraams within NEZ. Just a shooting gallery type of test. Could have been 100% kill ratio if I didn't fire 2 missiles at one target and another one at a target .4nm in front of me (high crossing angle) and... that Amraam came off the cheek station
  4. I was wondering if 'expanding box' or any other way to define the acquisition area would help in this situation: On uncluttered roads, it doesn't really matter. PTRK locks on vehicles w/o any problems:
  5. The lack of 'expanding box' is still a big problem but... the heat imaging in the latest OB is a big step forward. There might be some issues with textures on some vehicles (according to bug reports)... just look at the difference on A/A objects:
  6. Practicing different methods... using our Hornet's crappy FLIR
  7. I don't pay too much attention to DCS LSOs, as far as grading goes, ambiance perhaps. I try to stick to established ways as much as possible and usually I can spot my mistakes and correct or... chew my own butt
  8. Well, there are number of issues with this version of Hornet's A/G radar but there is definitely one fix that could mitigate most of them and make the expanded modes useful. Zoom/resolution of EXP3 and possibly EXP2 (a little). With zoom level doubled in EXP3, I wouldn't care about rotation (as long as it rotates around the designated point) or other error inducing quirks. (when banking, etc.) Designating and refining would be fairly easy. ...just a thought.
  9. You'll notice the difference. I keep the wake turb. off for now. Updraft over the ramp is not too bad but... it took me a few tries before I learned to deal with it. Another thing... I don't know if it's my imagination or what, but after the last 2 updates the power response seems a bit sluggish for some reason. Drag?
  10. Frederf might have some evidence and knowledge related to ground radar, I don't... just basic anecdotal stuff. That's why this is all hazy in my head. I always thought that once the expanded mode was 'locked' around the designation point and was scanning and re-scanning, refining the image as the jet was getting closer. The quality of course depending on distance and offset angle. As far as slewing is concerned yea, I wouldn't try to refine the designation from too far, whatever that distance may be. I also thought that the 'freeze' function was simply a snapshot of the area, rotating to show proper orientation with respect to ownship. Any violent maneuvering shouldn't 'throw it off' as it does currently. And of course, radar is not working 'solo' during this entire process. Perhaps someone can shed some more light on this sooner or later...
  11. What's the optimal distance/angle to minimize errors for our version of APG73? It seems like the cross is always off. I know the target elevation should not be an issue with radar ranging but it almost seemed like my JDAMs were pointing at the proper coordinates shifted down to sea level (?) As far as radar resolution goes, I could only distinguish target shapes (TU160) from around 4nm, that's only at proper offset and bank angle toward the target (?). Also, 'FRZ' function is still effected by radar updates in the background. I hope this is not the final version of this ground radar. In this clip the first target is co-located with WPDSG designation, still the cross on EXP3 page is a little off. The second target was designated using slew function on EXP3. The first hit was dead on, the second short, target partially damaged.
  12. Boring and mundane but still... it won't go well without regular practice.
  13. OK... 3rd time is a charm. I guess what I really wanted to know is whether having a specific program boxed meant automatic download of 'that' set of programs for all stations unless manually changed. Say I have 8 JDAMs again, all stations have TOO1 and TOO2 set. I have TOO2 currently selected. I release QTY of 4. Now, wouldn't this be easier and faster to simply select TOO1 and with the QTY already set... it's just a matter of another pickle instead of stepping through all stations and re-selecting TOO1 on each. If, all of a sudden there was a need to change to the other TOO, I could always do it then by selecting it manually. Anyways, I raised this question since I always try to find a way to do things quick (cutting out few secs. can make a difference). If it was up to me , I'd make this process flow as simple as possible with the flexibility to change programs, if 'really' needed. But... if there is a reason for current mech other then slowing me down, I can live with it. I should be able to get some feedback sometime next week unless someone here beats me to it.
  14. I knew I should have placed captions for every button push I was making... I understood what was going on when I was testing and setting up for QTY releases. My question was about the TOO logic in real jet... I guess I'm gonna have to pry other sources for info. Anyways, I was curious why stepping through all stations with TOO1 program boxed, downloaded immediately but when switched to TOO2 and stepped through stations again didn't follow the same logic. Each station had to be 'confirmed' by boxing TOO2 after each step, that's all.
  15. Regardless whether dropping 8 JDAMs in one pass happens a lot in RW... in DCS, especially in single player ground pounding, it's a nice feature to have. Question: With both, TOO1 and TOO2 programmed for all 8 bombs, when stepping through weapon stations in TOO2 for instance, the target coordinates show all 4 weapon stations on TOO2 (remains boxed through stepping process)... cool. Now, I decided to launch my TOO1 bombs first, so I box TOO1 and step through all stations but TOO1 is not being downloaded automatically. Each time I have to box TOO1 after every station step. Well... it's workable but does it really work like this in real jet? I understand this makes it possible to mix programs in QTY releases but if I have 8 targets that 'just' popped up and I scooped them up with my FLIR pod, I seriously doubt I'd have time to be mixing and matching TOOs for my QTY releases . Here's a short vid showing my fumbling with stations and TOOs but it did work. Does anyone have idea how this worked in RW... circa early 2000s or so?
  16. Oh FFS (no, ff doesn't stand for force feedback... ) It's either your stick setup or what WOPR said: before touching the trim switch, make sure to disengage any autopilot sub mode you might've engaged before the break. Smack the paddle switch just to make sure. Well... first, make sure your paddle switch assignment is correct. When rolling out after the break, you should be slow enough to avoid any horrendous ballooning, just counter with the stick. The FCS model is still being worked on (I hope) and NO... it's not similar to Cessna. With the way things work currently, I prefer to gradually start adding power and trim simultaneously as soon as I see the velocity vector beginning to creep down. You should be in a descent anyway, from 800 to 600 ft. (Of course, talking carrier ops here) Takes a little practice to do it smooth. Other then that... check, double check, triple check your stick setup.
  17. I see this once in a while in the latest OB. On top of that, AZEL might show AWACS feed in the mission but not in the track replay (?)
  18. My burble work-ups: and, finally mustered enough courage for Mode1 + ATC. It actually followed the ball (for the most part) Of course, the 'wake turb. was disabled:
  19. UncleReiben's tip works. Disabling wake turb. is definitely an effective temporary fix for the silly nose wobble. The downdraft is fairly easy to deal with now. The upward bump might be a bit tricky but after some practice flying the ball all the way down is becoming a routine.
  20. Finally today I'll have a chance to burble around again and experiment. On my last attempt (right after posting my above vid.) I was able to fly the ball actually and hit the 4 wire and it seems I can do it consistently. 3 wire... sure but it doesn't look right. I have to either overpower, cut and go to MIL way early to hit 3 wire, with the wrong AOA or... jockey the stick a little as described by couple of people here already. Forcing the stick forward at the ramp should be a big nono. I haven't disabled the 'turbulence' yet and will definitely try it tonight. I wonder if anyone (including RW boat experienced folks) managed to fly a perfect ball through the burble w/o doing 'silly' stuff. On a different note: I added one extra item to my pre-landing checklist. 'Home' waypoint on FPAS page goes to #58 (blank)
  21. This bug has been around for a while: https://forum.dcs.world/topic/297695-ag-gun-after-using-jdam-issue-update/?do=findComment&comment=4936693 The thread above was not the first report on this bug. It's related to using A/G gun after any GPS weapons have been powered up.
  22. It's a start. After a while and bunch of YT vids, you might decide to get deeper and finesse the 'stuff'. Lots of good reading material around the forums.
  23. Son of a... , just had my first exposure to the burble. I'm late to the carrier ops after the latest OB update. I flew 2 case 1 patterns and it seems like I have some work to do, to re-learn flying 'burbled' ball. Unless... ED beets me to it and make it more manageable. There seems to be a downdraft in-close and I could probably learn how to power through it but this nose-up over the ramp (it seems more like a pivot along lateral axis) followed by a nose down wobble, which brings the hook up and makes alpha lower made me bolter twice in a row. The ball needs to be centered or tiddly bit up almost all the way to the wires. Well, I'll try... Thanks for the 'wake turb.' tip UncleReiben. Lets see if that works. Here's how I got burbled on my first case1:
×
×
  • Create New...