Jump to content

MYSE1234

ED Closed Beta Testers Team
  • Posts

    716
  • Joined

  • Last visited

Everything posted by MYSE1234

  1. Yes, is bullshid. It's for the doppler
  2. You absolutely want to not use the cockpit textures, and probably also the EP08 one. The rest I think can stay if you want.
  3. The visible area The visible area moves when you move your head, and also with seat height, and with the glass position. The symbology is only 20x10 degrees, so the 30 deg total is plenty. You can install this to get a better idea of what it more should look like. https://forum.dcs.world/topic/287165-realistic-hud-mod/?do=findComment&comment=4886842
  4. It is the camera position. Here's an image that show what the pilot would roughly see, from few pages after the image you posted. One circle for each eye. IMO the current HUD is quite generous in what you see. There will be some further changes to the placement of some elements though.
  5. 09. For example the black part of the Datapanel decal was illuminated with the night lighting. That stuff was removed. 28. The horizon is separated from the rest of the ball, and do not rotate when you change course. You can see one of the "seams" as slight shading on the black part a bit below the horizon here. 30. This part of the rope was moved around a little to look more natural. 34. These switches 46. This switch 54. These ones 61. The indicator's default/ off position is corrected to be around the left side of the M (instead of the 150km/h mark), it also starts to move at the correct-ish speed now. Before it started to move as soon as the aircraft started moving. Now you need 120km/h-ish before it starts to move. Additional corrections to the PDF: 31. This is the panel that was basically remade 36. The dimming (which is currently not implemented in code) is for these two panels. 40. Is for the light shining light on the cockpit; It now changes color when you change the pol. filter, which it did not previously. Not wrong, but.. 49. This decals was added 50. Left one is the radar test one, the right one is the temperature selector. Both received text.
  6. Soon. It's in progress.. What can be seen now anyway, some of the stuff are no longer visible due to it being fixed
  7. It's actually the switches on the ends of both of the panels in question. The left one is next to the KB switch, and the right one is on the same place but on the opposite side of the cockpit. The imperial unit stuff was added by accident to the changelog,and was not meant to be there. Maybe in the future..
  8. Sure it on youtube here. It's shown a few times, but here's a time stamped link for the first one. The colors seems pretty accurate to me in it, but it being an issue capturing a phosphorous display accurately is a fair point.
  9. There is only one light on the left side as opposed the two on the right side. Where the one on the left is located and shining I'm not sure, but made a guess it would light the front of the panel. I didn't find any reference for it so if you, or anyone else do, I'd be happy to change it. It's due to this reference. Now I'm aware that it's from a (AJ)SH37, but I have a hard time thinking they'd be that different color wise. Maybe they were though, but I'm working on very limited data here. Real radar from video on the left, old DCS top right, and new DCS lower right. The "white" circle marker can just about be seen at the very top of the left image for reference. (Old images on the right) null It has incorrectly been "white" previously. It should be black, like it now is. The taxi light is something I definitely am going to improve. They are black/grey IRL and thus are not very visible. Especially so at night. Subjective as you say, but using a sensible brightness level for the current time of day should make it look better than in that image. Going full blast IRL I would think wouldn't look very great either. The wear on those old ones look more out of place than the new panels IMO. To get the amount of "black" on those I think you'd need crew chief painting them with black paint. Here's some real panels that are quite old at the point of taking the photos. Just because it's old doesn't mean it's completely destroyed.
  10. It would be an optional thing. It wouldn't be forced on anyone. Same as with the current mod
  11. Correct, it will not be needed anymore. I'll see what can be done with the altimeter if it's something that's actually used.
  12. @Raphomet Have you tried deleting your DCS_AJS37 folder inside Saved Games, or deleting all files inside it? Some times you get a bad cartridge file in there that causes a crash. The mission itself funs fine for me. And you there's tonnes of weird DTC stuff in the log, so I'd start with removing the cartridge files. @TOViper
  13. Yes, it's because of a problem in the cockpit model itself that causes some stuff to not illuminate.
  14. It's a known thing that happens with rockets in the (imaginary) single fire mode: For some reason the rockets will land long every time.
  15. I noticed this too earlier today. I've put the bug in the tracker for a future fix.
  16. Thank you very much! Yes, that is correct and they are simulated. You have a CW signal and a HPRF (>5 kHz) signal. Both of which should be fairly common to hear, specially the HPRF one. Here you can listen to both of them: CW CW.mp3 HPRF.mp3 HPRF HPRF.mp3 Not all units use signals that would use these two signals, so it's not like all locks will have the same one signal, and that all launches will have THAT one. It depends on the system.
  17. It does the same thing there as what I've written above. It just takes the distance to the waypoint and places the far and close border accordingly. The side borders are always 20 degrees each side of the centre line. It's similar to the last image, just the waypoint is behind you, but the aircraft does not take that into account. It just does what it always does.
  18. I think you have the wrong idea for how the system works. The times where it did not show anything on the scope is when you have terrain between you and the area that the B-scope is showing. So by having the displayed area in radar shadow you get a blank image, as the scope is only every going to show you the area (in distance) around the waypoint. In azimuth it's showing +- 20 deg each side at all times, no matter what, meaning you have to point the aircraft at the waypoint to actually see that area. I did a "quick" little illustration from the begin of your track, showing B1. The two images on top are straight from the radar scope, showing both A1 and A2 modes. The bottom left image is overlaid with the area that A2 will show, and on the on the bottom right you have that same area copied over and distorted to fit the square B-scope image. The "B-scope area" has it's borders as such: Far border: Distance to waypoint + 4 km Close border: Distance to waypoint - 6 km Left/right border: 20 degrees from the centre line Comparing the two right images show that they are practically identical with regards top the area that show returns. The gain is higher in the A1 image, but... Here's one that show that you're seeing pretty much, when you have terrain in front of you and what it does when you're not pointing the aircraft at the waypoint selected. The area inside the marked area does not have any returns and will thus not show anything on the scope in A2. In the A-A mode and the TA mode it does not do this however, which is why you say "...B-scope draws the terrain correctly" when you use those, it just shows the 1 -11 km area in front of the aircraft in those, and the same 20 deg sideways. No weird SAAB stuff going on.
  19. I'm not quite sure I follow what you mean I'm afraid. A2 works at long ranges too for me, just need to make sure you have the appropriate range setting/antenna elevation, along with proper gain. Here's a ship at ~78 km (7,8 mil for the cool kids) distance. And a closer one. ~50km closer than the first one Between the two waypoints/ships. If you have a track showing the issue you're seeing I'll happily have a look at it.
  20. What part of it? It being "centred" (it's really -6 km to +4 km around the WP being shown) on the waypoint is how it should be. The only issue here that I can see is that the pilot did not define any waypoints in the computer, something I very much doubt would be done IRL. And also that LS is not really selectable as a waypoint, but A2 is still working as it should. It's weird, but it is correct.
  21. You wouldn't see the discrepancy then as they were near identical back when OB dropped. Only with 2.9 would you see a real difference as the AIM-9 family received new values with that patch.
  22. This is not correct, Viggen uses the same AIM-9 missiles as any other aircraft in DCS does since 2.9. And I'm pretty sure the AIM-9B above is with updated values while the RB24 above uses the old ones still (not that they are in use tho). They used to have the same values, except for the proxy fuse which ED has incorrectly set to 7m, instead of 9m. From the changelog: New implementation of A2A missiles (by ED) for MiG-21 and AJS-37: R-3S, R-3R, R-13, R-13M1, Rb-24/24J, and Rb-74. Fixed inaccuracies in several versions of the AIM-9.
  23. Since you asked. Available for download in the OP. null
×
×
  • Create New...