Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location:


  • Location

Recent Profile Visitors

767 profile views

astano's Achievements


Member (2/3)



  1. Hi Gnarly, Glad you enjoyed it and I do really appreciate the feedback. I didn't notice until now that not only comments but also ratings on the Repository are gone, which is a shame as I had got some valuable feedback from those that I didn't record elsewhere. Regarding your thoughts: -It would be possible to create such a "surge" by triggering. Reinforcement spawns cannot be triggered (as I believe they can in ARMA) but you could add reinforcements and cause them to move with a trigger. When I initially made the scenario, I actually considered bringing in a Russian mech platoon or half-platoon around when the Brads came in, but ultimately decided I wanted to keep it pretty "set-piece" with a minimum of surprises - including red reinforcements - for the player. That would also have been another wrinkle in a scenario where the primary goal was just to actually complete, polish, and publish a scenario (instead of leave yet another half-cobbled-together mess on my hard drive). -I saw the same behavior in testing and am not sure what causes it. There is no way for the scenario designer to specify surrender parameters - they are hard-coded into the engine. The only control a designer really has in this regard is the ability to manipulate the AI into not surrendering by adding a bunch of AI "reinforcements" timed to never actually enter the map but I don't think that's the case here (it's been a while since I did anything with this scenario). My guess is that it has to do with the destroyed Russian vehicles on the map, which may be counted by the AI in surrender calculations and having the same effect. In the end I didn't worry about it much because it generally takes/took pretty close to time to secure Chicago anyways, so by the time the AI is to the point of surrendering time is often up anyways. Perhaps I will revisit that though. Thanks again for the feedback.
  2. Are you sure about that? The in-game models of the M110 and the M110 CSASS visually appear to be suppressed, although the squad panel icons for them don't show it. Admittedly, though, whether or not those or any other suppressors' effects are modeled I haven't done any testing to say.
  3. I believe the point of putting suppressors on sniper rifles isn't to make them quiet or stealthy close-in, but to make them more difficult to locate at longer ranges. Even the best suppressors won't make a rifle totally silent, and a high-power rifle round (like .300, .308, or .388 - even .223) will still make a "crack" as it passes, but they do reduce the muzzle report (as opposed to the sound of the bullet itself) and the muzzle flash. Suppressors on sniper rifles therefore aren't so you can kill sentries or something close-in, it's so the guy across the valley can't tell exactly where you are by light and sound. FWIW, my experience with sniper teams in-game is that the Tac AI has got pretty good about having the third man (in the US teams generally armed with an M4 ACOG) only open fire when enemies are close enough that I would want the whole team shooting anyways, or sometimes when given a direct target order. Since the snipers' rifles aren't truly "silent" in the first place, this behavior makes perfect sense to me: everyone fires at targets closer in (where the enemy would likely detect the silenced rifle anyways) than further out (where the guy with the M4 doesn't have the accuracy to make any hits). I find that it's still the case that snipers are most effective when left to their own devices, with at most a cover arc.
  4. Can't really be done, at least not in the way that you can in CMBS. The new QB unit purchase feature started with CMBN. Best alternative I know of is to open up the Editor, pick a QB map, handpick the forces for it (make sure you at least place them in their on-map setup zones, if not in an ideal starting position), and save it as a new scenario. You can increase the fog of war by making several scenarios with the same Blue and different Red forces for each map you do this on, so that hopefully you don't remember exactly what you're facing when you load one of the scenarios.
  5. Curious what you have in mind equipment-wise. The super-tacticool high-speed-low-drag rifles, optics, plate carriers, etc. would seem to me to be almost entirely cosmetic. Obviously if SOF make it into the game those should be modeled, but I'm wondering if there's something beyond essentially visual changes I'm not thinking of? I guess there's also suppressors (also already in-game on at least US marksman rifles) but I don't know how much difference that might make. I don't have enough of an idea to comment on any Ukrainian or Russian elements. I also wonder if anything beyond that can be done. Given that BFC has said that there are no national differences between infantry (e.g. a Ukranian +0/+0/+0/+0 rifle squad is the same as a Russian +0/+0/+0/+0 rifle squad is the same as an American +0/+0/+0/+0 rifle squad) other than their equipment, I'm not sure I'd hold my breath for differentiation within nationalities either, though it's certainly possible that such a capability exists and lack of national differences is strictly based on philosophy. But given that BFC have repeatedly stated that that is their philosophy, I'm not sure why they'd take the time to build an unused capability into the engine. In that case a US mech rifle squad and a US SFOD team might only be capable of performing identically (other than their typical soft factors and whatever might be attributable to their equipment). I'd still also like to see SOF in game anyways, if for nothing else than to add some flavor and more possibilities for smaller infantry-focused scenarios. Their inclusion could also make sense as advisors in the possible future separatists module, since foreign internal defense is a traditional SOF mission.
  6. Thanks very much for the compliment, but I don't know how keen I am on doing a campaign. I barely have the attention span to play a campaign - I think the last one I actually finished was Kunst des Krieges in CMSF (on second thought, that might be the only campaign I've completed) and I haven't even started 2/3 of the CMBS ones - let alone make one. That's a huge amount of work and my hat is really off to anyone who can make one solo. At various points through conceptualizing and designing this scenario, I did consider adding elements of the TF reserve mentioned in the briefing as reinforcements at about the one hour mark, but decided I wanted to keep this scenario pretty tightly focused on the Scout platoon. I may still revisit that idea in the future. I'm pretty new at making complete, finished, and polished scenarios, so I'm trying to limit my scope for now, but I think one day it might be fun to turn what is now this scenario into just the first hour of a long, drag-out company- or battalion-sized battle on an expanded map. We'll see how I feel about that once I have some more experience with bigger scenarios. Glad you liked the scenario and the map, and sorry about your luck. With your limited forces, and especially limited AT assets, it can be very important to have eyes on where the enemy is or might be in order to hold out, and sometimes keeping those eyes alive is the biggest challenge in the scenario. (Also, not sure if what's your driving at, but AFAIK the helicopters won't give you contact icons - the only way to know if they've spotted something is if they shoot at it). Good luck with your next go!
  7. Hope you like it, looking forward to hearing how it goes for you. Nice write-up theforger, and I'm glad you enjoyed the scenario! I'm particularly sympathetic to losing Daily's Bradley, it always hurts when you lose a lynchpin like that.
  8. My second scenario is now available on the Repository. You can download it here. The scenario features a US Scout Section finding itself in the path of a larger Russian mechanized force. I tried to do something a little more experimental with this scenario and give it a bit of a TDG or "in media res" feeling. Contact has already been made and now you, as the player, must develop the situation in accordance with your higher command's objectives and intent (or at least that's the idea). To that end, the briefing intentionally does not discuss the details of your objectives, any point values, reinforcement details, etc. - instead, there is a briefing within the briefing, from which the player is intended to determine what needs to be done. Specific objective and reinforcement details are included in the Designer's Notes tab as a fail-safe. The scenario is pretty small, with the US player eventually receiving the bulk of a mechanized Scout Platoon plus attachments, and plays out on a new 1200 x 800m map featuring four Red AI plans. Although I would recommend real time play, both my testers got on pretty well doing WEGO. It is playable as Blue only; there are no Blue AI plans and it is not balanced for H2H play. Special thanks to knightsabret and bangalor44 who gave me great feedback during testing. From the briefing: At the risk of sounding like I'm blowing my own horn, I really enjoyed this scenario while I was testing it. Even knowing the enemy's possible courses of action, it can turn into a real nail-biter. As I said in my WIP thread, I've had results ranging from a cakewalk, to my CO and a couple Humvee drivers holed up in a church with only a few AT4s to hold off a platoon of Russian armor. Depending on your decisions and the breaks it can be really tough, and Blue cannot afford to throw away a single asset if they want to win. The Red AI plans and number of tactical options available to the player, combined with a relatively short timeframe, should give this scenario some significant replayability - if things don't go your way, another crack at it should be fruitful. Comments from my testers seem to echo the intensity and replayability. As always, any feedback whatsoever is highly appreciated whether by post here, PM, or email to astanocmscens @ gmail . com, and I'm always interested to hear how people do with the scenario.
  9. Glad you liked it. That's just about the difficulty I was shooting for - hard enough to make it interesting, but easy enough that most players should be able to win most of the time; the kind of scenario you can download and beat in an afternoon. Regarding your plan, The first draft of this scenario didn't include the Bradleys - actually, the biggest reason I added them was for the ammunition they carry. In pre-Bradley testing I found that the firepower from the dismounts + Javelins was pretty sufficient, but that they didn't have the ammo or the endurance to take both the hill and the town. I ran the scenario several times that way and would frequently wind up with exhausted infantry squads trying to secure the town with only a couple mags of 5.56 and a few hand grenades left, which put the player in a bit of a bind - save their ammo and risk more casualties taking the earlier objectives, or try to take the final objectives with virtually no ammo. That made the scenario a little more difficult than I was shooting for. I settled on adding the Bradleys because, given the map and circumstances, I didn't think it would be fair to give the player supply trucks, and doctrinally the dismounts aren't intended to operate without their Bradleys for a long period of time anyways. Also,
  10. If anyone's interested and hasn't seen it yet, my first scenario, referred to above, is now available on the Repository (link in sig / forum thread). I also have another scenario that is now ready for public testing. I currently have one tester lined up but I'm always looking for more feedback. The scenario revolves around a US Scout Section (+) making contact with Russian mechanized forces, and needing to act accordingly. There are four different Red AI plans. I've tried to give it a sort of Tactical Decision Game feeling, and dropped the player in the middle of the action with unclear objectives and a briefing that may or may not directly address the situation - the idea being that the player needs to assess the situation and act in accordance with the objectives and intent of their chain of command. From the briefing: My testing so far indicates that this mission can be really easy or really hard, depending on some of the decisions you make and the breaks you do (or don't) get. You're up against a fair amount of Russian AFVs with limited but very effective NATO AT assets, so if you can keep everyone alive the Russians might have a rough time; conversely, if you lose even a couple AT weapons, it can be quite a nail-biter. I've had results in testing ranging from zero NATO casualties, to chasing T72s off the objective with Humvee drivers armed with AT4s because that's all I had left. If anyone would like to give it a couple play-throughs and report back I'd really welcome more feedback. Feel free to post here or PM if you're interested. Otherwise, I expect to have it up on the Repository in the next couple weeks.
  11. Hi Wolfseven, Really glad you enjoyed the scenario! However, I'm not sure I follow your last remark. If you're referring to the contact icons at the start of the battle, the spotted units are due to pre-battle intelligence preparation of the battlefield (in this scenario, the earlier UAV overflights), not enemy forces your troops presently have eyes on. As the icons fade and disappear during the mission, it's because your troops have never spotted them to begin with - the contacts are from before the battle and, just like contacts spotted during the game, will eventually fade as they age. You need to spot these enemy forces with your "own" assets (your troops or UAV) in order for them to "reappear." Hope that helps... if not, could you elaborate on the issue?
  12. My new (and first) scenario is now available from the Repository. You can get it here. The scenario is built on a new 800 x 800m map and features a US Bradley platoon (+) attempting to destroy a small Russian rearguard. From the briefing: I'd love to hear how anyone who gives it a try does, and any feedback would be appreciated.
  13. Just submitted my first scenario to the Repository. Thanks again to all the testers who provided feedback. Not sure when it will actually be available, but since there are currently no automatic Repository notification threads I guess I'll be making my own when it posts. In the meantime, I plan to maintain this thread for all my WIP scenarios, of which I currently have three. One is reasonably far along in testing so if anyone is interested in having a look at it feel free to post or PM. The other two are still in map-making (they actually cover some of the same geographic area, so about half of the smaller one, currently on 3D work, will make up probably a quarter of the larger).
  14. To clarify, what I would really like to see is the same asymmetric setting of CMSF with the updated TO&E and gear for NATO as CMBS. This is in no small part because I think it's easier to go backwards than forwards with the gear and have much greater scenario flexibility with the 2017 CMBS TO&E than with the 2008 CMSF TO&E - for example, in CMBS for US rifle squads you can get the XM25 (which has been in Afghanistan since 2010) and the M110 at squad level (which I believe has also been the case for some Afghanistan-deployed units for some time, but I'm not positive), with options to replace each with older gear (XM25 for M320, M110 for M4 ACOG). So while you can use the CMBS TO&Es for older scenarios, to me it's harder to do the other way around - an M203 is not as good a stand-in for an XM25 as an M320 is for an M203. Therefore I think it would be easier to do a 2003/4/5/whatever scenario with CMBS infantry gear than it would be to do 2010/11/12/future scenarios with CMSF equipment. I remember in fooling with the editor in CMSF to make 2008/2009/2010 era scenarios that I was even then running into issues with getting the correct equipment. A lot of this could already be mollified with the cherry-picking and team attachments of CMx2 versions 2 and up, but even though upgraded equipment might not sound like that big an issue, when you're trying to design a scenario that has no more than a squad and some attachments even slight firepower differences become much more apparent. (Edit to add: I'm not certain, but am fairly confident that the same would be the case with armor and other vehicles. I keep harping on infantry because those are my preferred CM scenarios, and thus I am less familiar with the kit and TO&Es as far as tanks and IFVs go in CMSF vs CMBS, but my sense is that just using the non-APS equipped vehicle variants in the CMBS TO&E would give you substantially the same organization and equipment as was available in CMSF). That said it's a matter of priorities for me. I will happily go back to the original CMSF forces and TO&Es with the newest engine if that's the trade-off for the original asymmetric force mixes to be combined with new features, but in absolute terms it's not my number one preference. Conversely I don't think CMBS in a desert setting is enough to get me excited about a new game because I'm just much less into the armor-heavy, symmetric fights characteristic of CMBS (even though I'd probably buy it anyways). Who knows, maybe BFC will surprise us all and (1) move ahead with CMSF2 in the first place - they haven't said anything about it in a while, so I'm not holding my breath - and (2) give us options for both 2008 and 2017 flavors of TO&E.
  15. Update: I've received responses now from all four players that contacted me to test the scenario and got some pretty useful feedback. Remarks were generally positive, especially regarding the map, and pending a few changes I'm pretty happy with the scenario overall, so some comments I'll be incorporating now, and some I'll be keeping in mind for other things I'm working on. I plan to thank my testers by forum name in the release version briefing (unless requested otherwise by PM), but thanks again to all of you for taking the time to play through and get thoughts back to me.
  • Create New...