Jump to content


  • Content Count

  • Joined

  • Last visited

  • Medals

Posts posted by Punisher5555

  1. All I know is that with the game in RAM there is no "loading/streaming". At least none that I can tell. Everything is just "there". No texture/LOD popping. No screen loading or anything. No matter I fast my vehicle/airplane is traveling. Everything is just "there".

    Example: When I start a mission as soon as I click the button, boom!, you start. Instant load. Took me by surprise the first time.

    Just think if the game was 64bit and had access to all this RAM naturally.:eek:

  2. Theres probably a better way but I always copied the orignal files to a new backup folder then deleted the ones in the standard Arma/addons.

    I will try that.

    Does it look like I have all the right folders? Am I missing anything?

    My 24.5 GB RAMDISK covers all of Arma2 and my @islands (pretty much every map out there), shacktac hud, CBA.

    Superspeed has a nice "image" option. Takes about to clicks to "restore" the contents of the drive.

  3. 1. Using Steam version. (Launch Arma 2: Combined Operations.)

    2. 32 GB RAM

    3. 24.5 GB RAMDISK using SuperSpeed RamDisk+ (set as F: drive).

    4. Startup params with ALL .pbo's in RAMDRIVE.


    Is this still the proper way to load the .pbo's from RAMDISK now version 1.60 reads the Arma2/BAF/PMC from registry?

    Are those the correct directories to have in the RAMDISK to cover EVERYTHING?

    How do I know if Arma2:OA is using the .pbo's from the RAMDISK first and not the hard drive?

  4. A similar thing could be accomplished without needing to switch to x64 - arma could have it's own built-in implementation of a ram disk with it's configuration set through the UI.

    That would be nice but just make the change and be done with it.

  5. My 2.5GB RAMDISK takes roughly less than 3 minutues to load all the .pbo's I can fit into it, and I have to click some buttons! Just think if they switch to x64, all the data would be loaded into RAM and silently in the background it would pull more into it as needed. Smooth game play all around. If you have never played ArmA2 with a RAMDISK you are missing how the game/engine should work.

  6. It looks like we will have still have to use our RAMDISKs to get any decent performance out of this engine. Too bad. They could have been the industry innovators by going 64bit. I applaud them for at least trying the LAA in ArmA2, but this game screams for loading/streaming the .pbo's from RAM.

    Performance in ArmA2 is like night/day when using a RAMDISK.

  7. Why would anything get dumped into the pagefile by windows if you have a lot of free RAM though?

    You are correct. Turn it off if you have 6+ GB RAM. Only one or two programs require it. I think one is a old Photoshop or something like that from early XP days.

    I wrote a huge post outlining how to setup RAM drive for Arma2/OA/BAF. Search for my posts or PM me.

    Name of the game is:

    1. Have RAM for OS/Steam/Teamspeak. (on my system it is 1.4GB)

    2. Have 4GB RAM free for Arma2/OA/BAF. (otherwise you get out of memory messages due to the LAA).

    3. All the rest set as RAM Drive.

    My all Steam Arma2/OA/BAF with 2.5GB RAM DISK run superfast. I have never had issues. Don't know what people are talking about with the latest or any patch. Everything works great in SP and MP.

    Played FarCry 2 too. With my RAM DISK turned on and never a pagefile. Works perfect. Stutter for people was probably crappy video driver or they overclock something.

  8. can you say OA UAV systems integration with the Kiowa? Sounds cool for an idea relating to a interface system while being the co-pilot/gunner of the Kiowa!

    The Cav is being reorganized.

    The new units make up will be Shadow UAV's and OH-58D's roughly half/half. One or two units will come online sometime in the next year.

    UAV operators will be scouting and then when they see something they will direct the 58D's to the scene.

  9. OH-58 F announced.


    Kiowa enhancements to give aging warrior new life

    Oct 28, 2010

    By Master Sgt. Doug Sample

    WASHINGTON (Army News Service, Oct. 27, 2010) -- The Kiowa Warrior OH-58D, the Army's primary armed reconnaissance scout aircraft in Iraq and Afghanistan, is about to get a makeover that will extend its life well into the future.

    Col. Robert Grigsby, project manager for the Kiowa Warrior Product Management Office, Redstone Arsenal, Ala., told aviation writers during the 2010 Association of the U.S. Army's Annual Meeting and Exhibition Tuesday that a new equipment package planned for the OH-58D includes such items as an upgraded sensor, digital inter-cockpit communications, and software for enhanced situational awareness that will keep the aircraft fighting for years to come.

    "Once the Army determines what the path to the future is for the armed aerial scout, that will determine how long the Kiowa Warrior will be in the inventory," he said. "What we've done is provide the capability to keep this aircraft viable while the Army makes that decision. "

    Several upgrades are slated for the OH-58D, which will be re-designated as the F model, but perhaps the greatest with will be the level-2 Manned-Unmanned teaming. Grigsby said this technology will enable Kiowa aviators to receive and transmit full motion video between other aircraft to include unmanned aerial vehicles. Working with the Army Aviation Applied Technology Directorate at Fort Eustis, Va., the system was successfully tested in July 2009 and recently integrated into the aircraft.

    "This is the first opportunity for the scout aircraft to have the same capability that was put into the Apache fleet and (it will) give them the opportunity to see data in their cockpit that's coming in from UAVs of a potential target area. This gives them situational awareness prior to coming on the scene and (and enables them to) be able to rapidly engage the target."

    Kiowa pilots will now be able to transmit their own sensor data to troops on the ground as well.

    Among several other improvements to the aircraft will be an advanced Nose Mounted Electro Optical Sensor, improved cockpit control hardware, full-color multi-function displays, and digital HELLFIRE missile future upgrades.

    Grigsby said all these changes will make the Kiowa Warrior more effective on the battlefield. "What it will do in my opinion is provide an aircraft that is more suited to the operational environment in which our Soldiers are having to fly in, and allow them to provide better support to the warfighter on the ground."

    For an aircraft the Army has relied on for 39 years and seen its share of combat, the upgrades could not come at a better time. Grigsby noted that since 2001, the Kiowa accounts for nearly 50 percent of reconnaissance and attack missions flown in Iraq and Afghanistan, the highest of all Army aviation assets. He added that while the aircraft is designed to fly about 14 flight hours per month, the operational tempo from supporting two wars has resulted in the OH-58D pulling lots of overtime.

    "We are flying an average 85-90 hours per month on these aircraft because the warfighter wants them flying. They depend on the Kiowa Warrior being there when they need them. "

    Meanwhile, Grigsby said changes to the OH-58 platform will come over time. "It's an incremental approach to how we upgrade the aircraft, to get it where it needs to be and provide the warfighter with this enhanced capability," he added.

    He said upgrades such as the reinforced floor armor is being install now, while the man-ummanned teaming system is scheduled to be installed in 2011. The Army plans for the OH-58F model to begin fielding in the fourth quarter of fiscal year 2015.

    In the meantime, Grigsby said the Army intends to bolster its inventory of the OH58D by continuing to convert older OH-58A models. There are currently 331 Kiowa aircraft on hand after losing 44 of them since 2003 to enemy fire and accidents.

    "We have an authorization to go out and buy wartime replacement aircraft, so what we are doing is taking Alpha model OH58s and converting them into D models. The plan is to eventually convert to new metal production aircraft as we move forward and the supply of OH-58A's dries up."

  10. That does not work, the game doesn't read the localVRAM from the .cfg, it only writes it there. Dwarden confirmed this before, so setting it makes zero difference

    Can we get a "firm" confirmation on this subject? Could help a lot of people.

    From what I have read is that the engine uses those values. It gets those values from the OS. You can see the values it reads from the OS if you do a dxdiag (numbers will match). Changing those values, setting it to read-only prevents the engine re-reading the values from the OS and it goes with what you have in the .cfg.

    Am I wrong? :confused:

  11. We know we should, but unfortunatelly we are probably not able to do it. The basic underlying technology which we are currently missing for this is loading (and unloading) addons on the fly. This is very difficult and it is unlikely it will be ever done for Arma 2.

    This what makes this a great company. They come right and tell you. Good or bad.

    EA/DICE/Activision/etc... would tell you nothing and give you the shaft.

    Keep up the excellent work BIS. :D