Jump to content

Draken35

Members
  • Posts

    862
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Draken35

  1. OB 2.7.11 / SSA 2.3.9 Had just a few minutes to do some testing. AH64, cannon and weapon release feel too soft (at 15),,, Might be subjective... Also, F16C G-Effects not working... Did not had time to test with other jets...
  2. Yes I am... Mostly to keep the Oculus Home in the tray.
  3. My PD in DCS is 1.0 btw.
  4. I think I finally nailed the config: 1) DCS: textures to medium 2) Oculus, refresh rate to 80Mhz 3) Oculus bump resolution to 4864x 2448 The rest of my DCS config was not changed. This gives me sharp cockpits with locked 40fps for the Apache and the other modules (I see lots of spikes of 80fps in the other modules) Perhaps, the folks that are reporting that they are good, should mention their refresh rates for the devices. It was the critical element for me.
  5. Spoke to soon... After doing a sortie with the Viper to test the Oculus Link crashing and confirming performance, I decided to take the AH64 for a ride in my baseline mission. Just me and 5 red armor located in the X airfield... Spent sometime on the ground playing with the MFD (no video or FLIR displayed at anytime) and took off... FPS locked at 45.... Studently, after a 3 minutes in the air, FPS dropped to 18 and none of the usual tricks (ALT+Tab, F10 map...) worked.
  6. I ran a baseline test, sitting at Kuboleti, in parked hot Apache, Viper, Hornet, Warthog, Mosquito and Huey. The Apache was half of the FPS of the other modules and very jerky when moving my head . With the Apache I get 30fps , 60 with the others (120 MHz refresh rate/ Oculus Quest 2) So, I removed all the mods and did a slow repair as suggested by Nineline and repeated the test: no difference. I didn't want to ruin the visual and performance quality in my other modules, so I doublechecked my PC settings, I have 64Gb of RAM and had a page file of 10Gb... On a whim, decided to bump the page file (which is in a SSD) to 64Gb and reduced the refresh rate to 90Mhz in the Q2. Repeated the test and all the modules are pretty much locked at 45fps now. The movement jerkiness is still there but not as bad as before (any ideas on how to fix that are welcome) . Upgraded the Apache to "passable" . During the testing I found another issue: the Oculus Links keeps crashing... Started yesterday and it is not module specific, even happened once in virtual desktop. I believe it is related to a beta update for the Q2 software (bad timing FB bad timing...). I'm in the process of reverting it and retesting.
  7. That is weird... Open Beta 2.7.11? Can you share the mission here?
  8. DCS native JTAC or JTAC script?
  9. Sidekick65 posted a couple of very nice tutorial videos for the script used in this mission:
  10. I don't have any shader mods or anything like that... But I'll retest without any mod after a slow repair to see if changes... My original post updated with SS of my settings
  11. Quest 2 i9-11900F 64Gb RAM RTX3080 DCS binaries & saved games in SSD I get 60 fps in any other module (F16, F18, AV8B, A-10C2, Huey, Ka-50, Yak-52, C-101, Mirage ... ) and 30 fps, including shakiness/lag with the Apache with the same settings... Not willing to sacrifice the quality I have and all the work it took to get there for the Apache . I'll wait for the next update to see if it improves... I do not have any shader mods or anything like that
  12. Well... we keep waiting
  13. Support and maintenance through the lifecycle of the software is often grossly underestimated and often, as well, are the source of difficult decisions. Can't wait for this campaign! Hopefully we will get it in the next patch!
  14. Mission was updated yesterday 03/13/2022 several improvements to the script: - added defaults to allow to display or not the Attack Results and/or Hits per Target after reporting an attack completed - TITS.EnterUnitEvent changed to receive "unitName" as parameter. This allow to call the this method to MANUALLY initialize units - Attack Results report now uses the designated target(if there is anY to determine if the attack was a good hit or not. - "Cancel laser designation" changed to "Cancel target designation" This menu will now turn off laser (if on) and undesignate any target - For WP designation, distance to the mark will be reported in 25ft or 10m/10yd increments - Added " on target!" text to indicate strafing hits on designated target - Added maxDeltaY for weapons position correction - Added ammo count track to calculate total % of rounds of target per pass (ROT) (if ammo is set to unlimited it will not be calculated correctly) - Added callsign to the messages
  15. Did you made any changes to the mission? If so, could you PM it to me? What I find it odd it that the parameters that is reported as nil, comes directly from DCS. I'll do some reading to see how it is supposed to work in MP
  16. @Mad44 Yes, those errors usually happen when the script does not initialize correctly for the slot (usually air start for Single Player using a "player" slot - not your case). Another indication of that issue is not been able to see the F10, range menu... I'm not setup to play multiplayer (and I don't see myself doing it any time soon) nor I have tested it in MP but I don't mind helping you (or others) to make it run in MP. You are my eyes and ears in this troubleshooting That's kind of odd... Questions for you: 1) Do you see the Range Menu ? 2) What were you doing before getting the error? Firing any weapon?
  17. Mission was updated today
  18. Glad it helped. As for intuitive, well, practice will make it intuitive Keep in mind, that somebody might be sharing a point of "interest" with you. before any decision of dropping a warhead in that particular forehead is made ...
  19. Did you box DESG in the EHSD after you got the DMT lock? I just tested it and it works. I'm attaching the track just in case you wanna see it (requires, probably, the vfg476 targets) https://www.476vfightergroup.com/showthread.php?5304-476th-Range-Targets-Package 1.trk
  20. Auto requires you to have a target designated. Otherwise the computer cannot know where do you want to drop Do a LSS with your DMT on your buddy's laser. Once the laser/target is found, that should (IIRC) create the designation and you should be able to use auto on it
  21. That and the residual positive G vibration are the only issues I have. I'm a new user (less than a month), so it might be something I'm doing wrong, perhaps. I've been installing the SSA Beta updates just by running the MSI without uninstalling the prior version, is that the correct procedure or should I uninstall first? In the last case, does that keeps the effects config?
  22. 2.3.4.0 - A-4E still no internal cannon effect
  23. Support thread for the mission. Download in user files Last update: 03/13/2022 03/13/2022 several improvements to the script: - added defaults to allow to display or not the Attack Results and/or Hits per Target after reporting an attack completed - TITS.EnterUnitEvent changed to receive "unitName" as parameter. This allow to call the this method to MANUALLY initialize units - Attack Results report now uses the designated target(if there is anY to determine if the attack was a good hit or not. - "Cancel laser designation" changed to "Cancel target designation" This menu will now turn off laser (if on) and undesignate any target - For WP designation, distance to the mark will be reported in 25ft or 10m/10yd increments - Added " on target!" text to indicate strafing hits on designated target - Added maxDeltaY for weapons position correction - Added ammo count track to calculate total % of rounds of target per pass (ROT) (if ammo is set to unlimited it will not be calculated correctly) - Added callsign to the messages 02/21/2022 - Improved accuracy of impact distance calculation and a few bugs fixed (details on the script) 02/09/2022 - Released Basic Surface Attack - Mariana Islands This is a training/practice mission. It provides a versatile range control script that provides feedback for multiple parameters of the weapon release: Distance to target, angular distance to target, targets hit by the weapon, altitude, attitude and speed of the aircraft at the time of release. Also provides different methods of target designation (laser, wp, coordinates, offset from a reference point). Easily add your own aircraft Two version provided: One with the A4 mod include and another without. Mission Briefing (images in the actual mission) Mariana’s Basic Surface Attack range ==================================== The objective of this mission is to provide an environment where to practice basic surface attacks. It uses a (reusable and portable) script that provides useful feedback on several parameters (distance and position of the impact, targets “hit” by the weapon”, altitude, roll, pitch and yaw angles at the time of release …) . Most of these parameters are optional and can be configured using the settings menu option. Mission flow ==================================== Think of the script as a “range control”. Communications with “range control” will be done via the comms menu (“\”, “F10-Other”). “Range control” has to be informed that ordnance is about to be deployed (using the “rolling in” menu option) in order to start tracking. Once the attack is completed, “range control” has to be asked to provide the results using the “Off - attack completed” menu option. There is an optional parameter in the script configuration that will generate an abort message if ordnance is dropped without the “rolling in” notification. Additionally, “range control” can be asked to provide the coordinates for the targets and to designated them using white phosphorus, laser or an offset designation (range and bearing from a reference point). The Menu ==================================== - Range - Reports - Attack results - List coordinates - Designation - Mark target (WP) - Offset designation - Laser/IR designation - Cancel Laser designation - Repeat last designation message - Settings - Display current settings - Toggle non strafing hits (BDA) report - Toggle display of Release data. - Distance units - Distance: set to meters - Distance: set to feet - Distance: set to yards Altitude units Altitude: set to meters Altitude: set to feet - Speed units - Speed: set to kph - Speed: set to knots - Speed: set to mph - Coordinates format - Coord. format set to MGRS - Coord. format set to DMS - Coord. format set to DM.mm - Rolling in - Off - attack completed The Ranges. ==================================== This mission contains two range areas: 1) Basic Range Easy to spot targets to practice basic techniques. Range control can provide the coordinates for this range and the targets it contain and provide offset designation from an offset marker (image 1) Available targets: - Circle A (image 2) – Offset designation available - Circle B (image 3) – Offset designation available - Strafing Pit (image 4) - Strafing/Bombing Area (image 5): contains 5 targets in a row (tanks and trucks). The white buildings on the sides are NO SHOOT targets. It is suggested to have the non strafing hits (BDA) report option enabled, in order to see the effect of the weapons in these targets. Offset designation available. 2) Tactical Range Multiple targets, some moving, a little more difficult to spot. Used to practice attacks in a more realistic scenario using WP and laser designation. It is suggested to have the non strafing hits (BDA) report option enabled, in order to see the effect of the weapons in this targets. Range control will not provide coordinates for these targets and offset designation is not available. ==================================== – Adding your own aircraft: ==================================== Well, just add them to the mission! The name or type of the aircraft is not important. The “SKILL” however, is important. For user flyable aircraft, DCS accepts 2 different skills: “Player” and “Client”. The mission and script support both. “Client” has no limitations but “Player” does. If the mission contains a single aircraft and its skill is set to “Player”, the aircraft cannot be started in the air because the range control will not work (DCS bug or limitation). A single “Player” aircraft is supported only if it starts on the ground. In this case, the script will start working when the engines are started (if cold & dark) or after take off (if started as a hot aircraft). ==================================== --Author notes: ==================================== The mission and script were designed for my personal use and are provided as I use them. All my ground attack aircraft are include, starting hot from parking (my usual setup for “quick” practice missions). The default unit of measurements can be easily changed on the ME, using the “Override defaults trigger”. The mission is setup with unlimited ammunition and all the aircraft need to be rearmed. When designing the script, I decided not to spend time (neither CPU or mine) doing validations, so, be warned: if you use an unsupported value, something will blow up. Please use the forum thread provided in the download page to contact me. vFG 476 Range Targets Package REQUIRED https://www.476vfightergroup.com/showthread.php?5304-476th-Range-Targets-Package
×
×
  • Create New...