Jump to content


  • Posts

  • Joined

  • Last visited

Rangoon's Achievements


Member (2/3)



  1. An updated CMA would be outstanding! I keep wanting to fire it up again, but since CMSF2 released, it's just not going to happen. I would definitely purchase an updated CMA.
  2. If no one is recognizing this as a bug, is this normal behavior? It doesn't line up with what the tutorial is saying, but perhaps this has changed from when the tutorial was written? Has there been an increase in the time it takes for this kind of information to propagate up/down the chain?
  3. In the third mission, the tutorial in the PDF manual tells you to expect the armor contacts from A Company HQ to be shared with 1st Platoon 1st Squad. After three turns of just sitting on top of OP 1, no armor contacts have been shared. Contacts from 1st squad are being shared with the Syrian infantry next to them, as expected. As far as I can tell, there is a broken link in the chain. 1st Squad has radio and PDA link with 1st Platoon, but it seems there is no 1st Platoon. Nothing happens when I click on its link in 1st Squad's unit info. Similarly, clicking on 1st Platoon in A Company HQ's formation list does nothing. Is this a bug and is that why no contacts are being shared down the chain of command? Edit: I also now see that the Alt-Z feature shows no link between A Company HQ and 1st Squad, though it does show links with its other subordinates. So I assume this is the reason the tutorial is broken. But is it simply because there is supposed to be a 1st Platoon HQ somewhere and it's just missing from the mission? Or is there something else going on here?
  4. I'd also love to see CMA updated, and I'd buy it all over again.
  5. I completed the mission, this time before the timer hit 0:00. SPOILERS in white text: I think the difference was that this time I spread out a bit and prevented the enemy from ever reaching the bridge itself. As soon as the enemy began a withrawal from the bridge area, basically, they surrendered.
  6. Thanks agusto. I'm playing through it again (it's an oddly fun mission...well, maybe not even oddly) and will just go ahead past 0:00. I assumed at that point last time I'd done something wrong.
  7. I just thought I finished the mission "Night Watch" from the campaign "Afghanistan 1980 - The Invasion". I figured the mission would end when the clock reached 0:00, since I was holding back the enemy. The briefing just says to dig in and prepare for the assault, and that I need to hold my defensive perimeter. I've done that. I do have maybe two enemy infantry stragglers still alive on the bridge itself, but the workers aren't there and the briefing doesn't say anything about occupying the bridge, or killing all enemy. How is this mission supposed to end?
  8. Hey Vherid, why am I not surprised to see you here, in one of the true havens of quality PC combat simulation? Couldn't agree more. I myself just stumbled on waclaw's HQS for CMBN etc. Good stuff.
  9. Sorry I didn't see the PM right away (just changed my User CP to email on PM). I sent a reply. Thank you so much for this mammoth undertaking, waclaw! I really enjoy what HQS brings to the experience. And that you so kindly added the CMA content/compatibility as well is really appreciated. Going to go download the final version now and sit down to savor a (slow and methodical) morning of Combat Mission with HQS.
  10. Waclaw, I had a chance to look at what you sent. This "vehicle loop move medium track" file is interesting, and I'm not sure exactly what to say about it. So the flames first... The flames individual tracks are all fine as is, and then when combined you do get some clipping throughout, but that track is textured in a way (percussive) so that I don't really hear it (I only see it). If you were to normalize the loudest track (1.wav) below zero db at least, then I would think you wouldn't be hitting the limit. Again, that said, that was just a good example file to look at and see what was going on, but I don't think it needs fixing because you don't hear the clipping in that texture. The "vehicle loop move medium track" file is quite perplexing. I see that you literally just took those three files and mixed them. And when I listen to the engine track individually, I hear between about 1.7 seconds in through about 3 seconds in, during the roar of the engine, some distortion, but now that I hear it by itself, I have a few thoughts. 1. I think now that it's more of the extreme compression I'm hearing and not actual clipping. It sounds distorted, but what I can see about it is that the file is significantly compressed. Maybe that's the nature of the noise I hear. 2. I think it actually sounds good ("true" for the most part; obviously it's accurate because it's the real thing) except in a couple short regions like I mentioned above. 3. nothing can be done because it's in there inherently 4. I think the combination of those textures mislead my ears a bit during those more compressed bits, with the overall mix sounding clipped but it's not. So in the end, without looking at other specific cases, I think I just wish the source files weren't compressed so much. You couldn't fix these by normalizing the engine lower by a few db and remixing, because it was already compressed and normalized below zero db to facilitate the mixing! I have heard tanks (at shows, not on a battlefield), and of course they are loud, impressive, and huge sounding, but they don't sound compressed like that in open air. In this case, you couldn't have done a better job with the sources you have. So I think that considering this recorded format, I just need to shut up and enjoy the sound for what it is. There is no doubt you've done an excellent job with the files. Again, maybe some files could be fixed in the way that flames.wav could be (though flames.wav doesn't need to be), in a way that would help. But this medium track file that you sent can't be unless you change the source. And maybe the recording is fine and that's just how you record tank engines (I've never tried to record tanks) - with huge amounts of compression. I'm more than happy to look at any other files, but now that I see what you're working with, you've only improved them with the excellent mixing with other textures (earth, tracks, wheels, etc.). Really nice work on those. Sorry if I misidentified what I was hearing, and thanks for sending those files to investigate. Other files where I hear this same phenomenon at work: "vehicle loop move abrams.wav" "vehicle loop move wheeled heavy.wav" "vehicle loop move bradley.wav" "vehicle loop move challenger2.wav" "vehicle loop move heavy track.wav "vehicle loop move leo2.wav "vehicle loop move warrior.wav"
  11. Sure. If you can send them today (I'm Central Daylight Time in the US) I will work on them for sure tomorrow. Let's start with: flames.wav (is this from just one source file? Or multiple? Either way I will see what you see before the final mastering) vehicle loop move heavy track.wav vehicle loop move medium track.wav These are files in which I not only hear the distortion but also I see it in the waveform (flat/clipped peaks & valleys).
  12. This is great to have a version for both CMSF and CMA, thanks Waclaw! Just out of curiosity, I did open up your file "vehicle loop move heavy track.wav" as an example of a file that sounds much too hot. You can see clearly in the waveform (just expand the first second or so out to whatever level of detail) that the amplitude flattens out at the tops and bottoms for large stretches. So you get that clipping. Without knowing the source files you're using, I can't suggest where along the process it's happening. But even if I normalize the file where peaks are less than zero db, it won't help because the clipping is already in the file. It would just clip more quietly. Are you mixing multiple files into one? It seems to me that the engine/trasmission source is either inherently clipped like this or it's being normalized too hot and then mixed too hot with the other files. I would think you could get the same, heavy, huge sound but without the distortion, unless the original source is already tarnished. There are some cleaning plug-ins that I haven't used in years which can help a file like that, but to do it by hand would be way too much work. Well, then again, maybe not...if it had to be done the files aren't that long. It depends on how pervasive the original file's problem is. To touch up flat peaks dozens of times per second would take a long time, obviously. I would be glad to help with an effort like this if you want. Just let me know. The only thing is that I have a very busy summer work season which is just about to start ramping up even more. It should have intensified by now, in fact, so I shouldn't even be able to sit here and write this post, but here I am. It could start Monday, or not for another week. As long as I have a little time still, I would be glad to help. That said, if I am the only one listening to this level of detail, and the only one hearing this in the files while I play the game with this mod, then of course leave well enough alone. I don't want to encourage work where work isn't needed. In my humble opinion, it would be worth it, though. EDIT: I also see it in flames.wav - this extensive clipping throughout the file. EDIT: and really nice work on the new background files for Afghanistan. They needed to be different from the CMSF ones, of course, and I think what you did is perfect. More sparse, more appropriate reports, etc. Very nice.
  13. When I play Steel Beasts, for example, I sometimes shut down my Tank and PC engines in order to vastly reduce my noise signature, but also to cut noise pollution so I can listen for enemy vehicles. Will there ever be a way to do this in Combat Mission. I understand with older WWII vehicles that were harder/more complicated to start, you might be less likely to want to shut them down (though I think it would be reasonable for a commander to at least be able to weigh the trade-off for noise vs. immediate mobility and have the option). But for the more modern vehicles, don't they have a much shorter and more reliable startup sequence? I had hoped that "hiding" would cut engines, or that there would be a command for this, but there isn't to my knowledge. Any word on whether this will be coming? Or is the lack of this as a feature a deliberate design choice which won't likely be changing (presumably for some well-thought-out, good reason)? EDIT: even after "bailing out" the engines are still running. Obviously in PvP humans can hear the other player's vehicles and vice versa, but does AI "hear" vehicles? Isn't that part of the "question mark" contact reports; that they hear something like a rifle report or see something vague? I can move the camera about the battlefield to listen for vehicles above my own vehicle's engines, but that's a bit of a stretch. Does it simulate shutting down engines while I listen? Or is that just gaming the sim?
  • Create New...