Jump to content

TheBiggerBass

Members
  • Posts

    553
  • Joined

  • Last visited

Everything posted by TheBiggerBass

  1. Ich habe mir vor 2 Tagen das Early Access Modul F-4E zugelegt und wühle mich gerade durch die Trainings. Die Phantom wollte ich immer schon mal fliegen. Mein DCS Setup ist so eingerichtet, dass ich auf einem Samsung 57" curved Monitor als Primary bzw. Center Display fliege und die MFCDs auf einem zweiten 32" Monitor darstelle. Dafür habe ich MonitorSetup files entsprechend modifiziert. ich versuche nun auch das DSCG auf dem zweiten Monitor darzustellen. Leider funktionieren die gängigen unit type IDs wie DSCG, RADAR_SCOPE, LEFT/CENTER/RIGHT_MFCD etc. alle nicht. Im F-4E Manual von Head Blur finde ich auch nichts. Kann da jemand weiterhelfen? Vielen Dank schon mal.
  2. Is someone else flying the F-4E and managed to display the DSCG on a 2nd screen? (Alt+F1 view) I need the unit type ID (LEFT/CENTER/RIGHT_MFCD, RADAR_SCOPE, DSCG does not work).
  3. That's correct. I'd like to limit that to Alt-F1 HUD view. I don't use my PC for gaming only and use the secondary display for other purposes while gaming on primary display. In this case I'd like to keep all displays on primary screen when in normal cockpit view. However, as one of my previous lives was writing code for larger projects I still would like to understand how to control the MFCD display properties, so count me interested
  4. I looked there 1st of course but unti name F-15 does only list LEFT_MFCD, CENTER_MFCD, RIGHT_MFCD, UFC and OUTER_LEFT_MFCD, LEFT_MFCD, RIGHT_MFCD, OUTER_RIGHT_MFCD,. I tried all of them but just LEFT_MFCD seems to work for MPCD. What do you mean with patching?
  5. Ok, now I am working on the F-15. There are Multi-Purpose Color Display (MPCD), Vertical Situation Display (VSD) and TEWS display. MPCD seems to be LEFT_MFCD but I need to know the identifier names for VSD and TEWS. The identifiers RIGHT_MFCD or CENTER_MFCD didn't capture them. Can somebody help which MFCD export names access VSD and TEWS?
  6. For me yes, at least I didn't notice them any more. I had black screen issues with previous driver release. Disappeared after 572.70 installation (knock on wood)
  7. Just another stupid rookie question: will already purchased modules and terrains be updated automatically?
  8. Find my actual monitor setup file attached. It's intended for use with two monitors: primary display (57" 32:9 curved Samsung Odyssey neo G95) set to 7680x2160px and secondary display (32" 16:9 BenQ UW3270) set to 3840x2160px. The secondary display is virtually located right from the primary display (x=7680, y=0) which results in a total graphics area of 11520x2160px. All MFCDs are set to be displayed on the secondary display. As I only used absolute pixel coordinates and sizes DCS does not care whether the second monitor is active. In case the secondary monitor is off the MFCDs are simply not visible any more. The reconfigure_for_unit() function (line 18ff.) specifies location and size of the MFCDs depending upon aircraft type. Default (the else part in line 71ff. of the if statement) are LEFT_MFCD and RIGHT_MFCD placed equal sized on the secondary display. In case of one MFCD (line 55ff.) the RIGHT_MFCD is placed in the center of the secondary display. In case of aircrafts with three MFCDs (line 23ff.), LEFT_MFCD and RIGHT_MFCD are placed lower left corner and lower right corner of secondary display. CENTER_MFCD is placed a bit smaller at the top side center with a bit of overlapping to LEFT_MFCD and RIGHT_MFCD. In HUD only view (Alt+F1) all MFCDs are displayed on secondary display only now, whether it's active or not. That's what I wanted. WW Special (8k).lua
  9. Same issue here. As DCS still works offline - just wait for next update or urge for action?
  10. I am working on a monitor setup .lua file for automatic MFCD placement depending upon the selected aircraft/unit. While testing it seems that some aircraft unit names might have changed in the past 4 years. I would like to custom place all MFCDs on a 2nd monitor and would like to check if I have covered all MFCDs. Currently I am just using LEFT_MFCD, CENTER_MFCD and RIGHT_MFCD. I would like to catch all other custom MFCDs too. I am not looking for a specific aircraft but for a comprehensive list with all aircrafts and their associated MFCDs.
  11. Is there any (updated) list of MFCD export names per (aircraft) unit type?
  12. Ok, my issue is solved now. Inspired by this very helpful tutorial (and many try-and-errors) I rewrote a custom monitor and viewports setup lua file, which allows to relocate and resize all MFCDs anywhere on the screen(s), even to non-visible or overlapping areas. Maybe the next rookie could save some time with this info
  13. Is there any recent lua editor with syntax highlighting?
  14. Habe ich gemacht. DCS sagt mir aber beim Start, dass die Autorisierung für das RedK0d Modul fehlt. Vielleicht liegt's ja auch daran, dass ich FC 4 statt FC 3 installiert habe. Ist aber auch nicht ganz so wichtig, weil ich die wichtigen Funktionen sowieso alle auf meinen Throttle bzw. Stick gemappt habe.
  15. I would not rely on a "smart" software solution when it's safety relevant. This is a safety issue and the graohic cards has to avoid this by appropriate hardware and layout design. This is just a weak and dangerous product design and not ready for market. Sorry NVIDIA, reengineering required.
  16. You should really start to become sceptical if a single 12V unit consumes 600W or more. That's a 50A+(!) max current. This would equal a 5,5kW consumption at 110V or a 11,5kW consumption at 230V. That's more current than your kitchen hotplate needs.
  17. This excessive power consumption - and price tag - are the main reasons why I don't want a 5090 or even 4090 in my system. My 4070 ti super already sinks about 300W. That has to be enough.
  18. Ok. 4) this is a tough one. I already had DCS installed on my SSD only before but only the startup was faster, nothing else. That requires everything to be reinstalled. I leave that for later. 5) Don't know how to do that. 6) check. 7) check. There is no NV_Cache folder in my NVIDIA Corporation folder 9) Don't know how to do that.
  19. Ok, I did a test run for the last two hours. Unfotunately the issue does not seem to disapear completely. However it's now much less severe with HAGS disabled. I also didn't notice any lower performance with HAGS disabled.
  20. It's already enabled as you suggested, just 3) was enabled for harware acceleration. After disabling and restating all seems fine now, at least I haven't seen any issue during the last hour. I guess it's fixed now, thanks! Any idea why hardware acceleration causes this?
  21. I run DCS my workstation (see below for details) which I am also using for work and other purposes too. Sometimes I switch DCS to the background to finish some other tasks on my PC: When switching DCS back to full screen after 15mins DCS runs so stuttering and slow that need to restart. This behaviour is reproduceable. I don't know whether this can be considered as a bug or not. Just want to share my observations.
  22. I'd like Cologne please to land with a heli in front of the dome
  23. ... and another VelocityOne Flight Desk miracle - at least to me Got my VelocityOne Flight Desk setup now, both stick and throttle with latest firmware installed, all buttons, sliders and axes have 100% functionality, as checked with the latest Flight Hangar. Everything works fine with DCS. Almost. Altough the hardware is confirmed and tested 100% functional DCS does not seem to recognize analogue axis Rz, D and Z (throttle). The same applies to S axis on stick. I cross checked that with MSFS2024 and got the same issue. The hardware is definetly working. What's wrong ? Any fix available?
×
×
  • Create New...