Jump to content


  • Posts

  • Joined

  • Last visited

DWG's Achievements

Recruit - 2nd Class

Recruit - 2nd Class (3/13)



  1. In which case, the tailwheel should definitely be on the tail boom, the special warfare tasked MH-60S being a Blackhawk airframe with Seahawk dynamics, see http://www.naval-technology.com/projects/mh_60s/ http://www.news.navy.mil/search/display.as..._id=7447&page=2 and http://www.globalsecurity.org/military/sys.../ch-60-pics.htm Far be it from me to insult the USMC (pale imitation of the real thing though they may be), but anyone who elects to use a less capable platform during a spec-ops insertion deserves insulting. They've certainly used AF aircraft in the past for insertions -- http://media.militaryphotos.net/photos/US_..._in_Liberia/aaj shows a marine (probably FAST rather than FR, but could be either and definitely a marine) in MARPAT in an HH-60 of the 56th Rescue Squadron (the Keflavik-based 56 RQS seems an odd choice to deploy to Liberia, but as I said you choose the best assets available for the job).
  2. What you don't make clear is whether you are using any mods with IGOR. The one time I've seen similar problems there were corrupt files in a mod that I was using. Turn off all mods and see if IGOR will work on just the basic GR files.
  3. Force Recon are a naval special warfare unit, the USMC being a USN asset. How much detail do we really see in-game? Eye-candy is nice, but all we really need is the general effect. It's actually being replaced with the UH-1Y (originally the -1Ns were going to be rebuilt into -1Ys, but it turns out to be cheaper to buy a new -1Y). The main visual differences are a c1m stretch in the cabin area and a four bladed rotor.
  4. IIRC, the SH-60R Seahawk is supposed to pick up the Special Warfare mission for the Navy when it enters service, so a reskin would be fine.
  5. Well spotted. I meant to try deleting different files to pin down the problem, but I'm not sure I'd have thought of music.xml and I didn't have the time anyway. I noticed a couple of music file file names were in upper case rather than lower, but this didn't seem to be the issue. Clear reporting (and better handling) of parser errors would be a nice improvement for future games in the series, there's no need to CTD just because -- for instance -- the kit file has a character in the wrong case. That assumes DWG has any time available himself <g>. I've had time to power up GR about twice in the last month. I fixed some problems in strings.txt early on, mostly formatting, but maybe others as well, I can't remember. I don't really have time to re-install and do a comparison, but it shouldn't be beyond anyone: open up the .GUN file of the weapon you're having problems with and check that the contents of the <NameToken> match character for character, down to case, with one of the left hand entries in strings.txt DWG
  6. DWG

    HK 417

    Something new for the modders: http://www.10-8forums.com/ubbthreads/posti...23-HK417_12.jpg HK's 416 in 7.62x51mm NATO, and the 416 is also getting a 6.8mm Remington version.
  7. Yes, it's a spin-off from the SPR programme, see http://www.thegunzone.com/556faq-nb.html and http://www.thegunzone.com/556faq.html
  8. The strings.txt file is quite simple, each entry consists of a pair of strings enclosed in quotes. The first string is the text found in the <NameToken> tag in the gun file. The entries in .gun and strings.txt must match exactly, including in case. The second string is what should appear on screen. So for example an M203 .gun file might contain: <NameToken>COLT_M203</NameToken> and in strings.txt we would have "COLT_M203" "M203" If you have a problem with a weapon name not appearing, then open up the .gun file and open up the strings.txt and check the entries match, almost certainly they won't. Dealing with Janie42's comments, the system works with all strings.txt files in all active mods, searching them in order of precedence and using the first match found. The number of spaces or tabs between the two strings is not significant. It's unclear what he means by numbers in the strings.txt file.
  9. The most common bullet for US military is 55gr. FMJ. The British use 63gr. I think. I suspect you're quoting the stats for US M193 and NATO SS109, M855 is the US version of SS109 and should have pretty much replaced M193 in the front line.
  10. I think everyone else would be grateful for whatever they could get, it's been rather a dry time for mods recently. SWEBAT was something that looked like it was going to be very good and it would be a shame to let all that effort go to waste.
  11. A fairly unique variant that may interest the modellers out there: the Falkland Islands Defence Force's Steyr Aug with SUSAT: http://www.soldiermagazine.co.uk/mag/feature6.htm
  12. Extremely unlikely. The archive flag is largely insignificant in normal use. '~67' is likely a character code for '_' that isn't being displayed properly, though I'm unsure which character system it's from. I don't see any problems with character names in my install and all .kit, .gun, .qob, .pob and .rsb files can be opened. The file m26frag.prj contains spelling errors in the <DamageThroughWalls> tag, about half the .gun files contain a non-printing character following the end of one or more lines (mostly, but not always, the reticle declarations). The music.xml and effects.xml files do not contain normal line-breaks. Unfortunately, fixing all of these still doesn't stop the CTD. DWG
  13. I spent a little while playing about with things last night and split the mod into three: missions, weapons and characters. Missions depends on the others, so I didn't experiment with that, but weapons (with fixed strings.txt) causes a crash to desk-top, characters doesn't (at least not that I saw). The CTD occurred before I had selected any of the weapons, so it looks like GR does even more pre-loading/parsing of files than I had previously believed. All in all it looks like the problem is with the weapons files rather than the characters. I'll let you know if I find anything more. DWG
  14. One I somehow missed from the list I put up, the Franco-German Eurocopter NH-90 tactical helo, one of those designs that will be used by a lot of people in the reasonably near-term future (off the top of my head: France, Germany, Italy, Spain, Sweden, Norway, Australia, New Zealand, the possibility of US use is receding though, with the Merlin now the firm favourite to replace the Pavehawk).
  15. The BBC's main broadcast TV channel.
  • Create New...