RE: Comprehensive Wishlist

RE: Comprehensive Wishlist (Full Version)

All Forums >> [Current Games From Matrix.] >> [World War II] >> Norm Koger's The Operational Art Of War III >> Scenario Design

Message

ColinWright -> RE: Comprehensive Wishlist (4/26/2011 10:18:53 PM)
This has gone on long enough. [image]local://upfiles/18444/5DB3E6D55BDD4F79B274A5F04F06E901.jpg[/image] Where does your matrix say the bridge is, Curtis?

Panama -> RE: Comprehensive Wishlist (4/26/2011 10:45:18 PM)
If that matrix is going to be used will the program do a search to see which case applies? If it does do a search to see which case applies why do you need to have so many places? Couldn't you leave out all of those where the road actually does cross the river? Or maybe leave out those where the road does not cross the river? Do you really need both cases? I guess I don't know how this is going to be looked at by the program. [&:]

Panama -> RE: Comprehensive Wishlist (4/26/2011 10:46:28 PM)
quote: ORIGINAL: ColinWright This has gone on long enough. [image]local://upfiles/18444/5DB3E6D55BDD4F79B274A5F04F06E901.jpg[/image] Where does your matrix say the bridge is, Curtis? According to the current state of things the answer is NOT 42. [:D]

Curtis Lemay -> RE: Comprehensive Wishlist (4/27/2011 1:08:51 AM)
quote: ORIGINAL: ColinWright Happily, your own lat-long program allows an objective means of mapping. Now, pick a list of rivers via some random technique: say all names with seven letters from a list of 'world's thousand longest rivers' or something. Then, map at...10 km per hex, shall we say? Use the largest city on the river as the midpoint of a 21X21 array. Put in only whatever roads are shown at a given height on Google Earth. See where your 'Matrix' puts bridges. Then ascertain where they are along those roads in reality. Time-consuming, but the results should be comic. I've already done multiple examples of this. See CFNA, France 1944, Okinawa 1945, Germany 1945, Soviet Union 1941, and Kaiserschlacht 1918. All done with the LatLong program and all made to exacting standards. And see this "house rule" in France 1944: New house rule: Bridges may only be blown if the bridge (road or rail) graphically crosses the river/canal feature, or the hex has urban terrain. That rule could be applied to most any scenario beneficially. France 1944 would definitely be worse without it. And note that that is exactly what the Matrix will effect. That's why (among other things - like good old common sense), that I know you're full of it.

Curtis Lemay -> RE: Comprehensive Wishlist (4/27/2011 1:12:44 AM)
quote: ORIGINAL: Panama From what I can tell, and it's difficult trying to follow this with so many posts, the problem is all about blowing up non bridge roads/rails because they parallel rivers. Right? This being considered a gamey aspect because if the road doesn't cross the river you shouldn't be allowed to blow it up. At least someone understands the problem. All you have to understand from there is that the Matrix will solve that exact problem. Roads that only parallel rivers and don't visibly cross them will not be blowable. If they do cross them, they will be blowable - at those exact locations. quote: Another thing. Will map makers have to actively do something with this matrix or is it a hidden under the hood kind of thing? It's under the hood. Map makers will simply have to follow the Matrix rules as stated above.

Curtis Lemay -> RE: Comprehensive Wishlist (4/27/2011 1:19:37 AM)
quote: ORIGINAL: sPzAbt653 quote: This is merely an attempt to get some clarity. I dl'd the Matrix.sce and don't get it either. Don't all those combinations need some code to tell the program whether or not there is a bridge in the hex ? Of course. And I went on to create the Matrix, as shown in my post #1515. The Matrix is a 64x64 array of 1s and 0s (note that the 1s and 0s mirror the peak hexes in the scenario). It will be effected in the code as a constant 64x64 array as shown. Then the program just has to reference it as I showed in that same post #1515. quote: Wouldn't the same thing have to be done for minor rivers, canals and major canals ? As I said in post #1522, I've already checked those other terrain types and they require the same matrix as the first. But, I'll attach the test scenarios here if you want to check.

Curtis Lemay -> RE: Comprehensive Wishlist (4/27/2011 1:23:28 AM)
quote: ORIGINAL: ColinWright This has gone on long enough. [image]local://upfiles/18444/5DB3E6D55BDD4F79B274A5F04F06E901.jpg[/image] Where does your matrix say the bridge is, Curtis? It says it is in the hex where the road visibly crosses the river. Which, of course, is the only rational place for it to be when the map maker drew it in that fashion. Only an imbecile would draw it that way if the bridge was in any other he... Oh. I'm sorry. Did you intend for it to be in some other hex?

ColinWright -> RE: Comprehensive Wishlist (4/27/2011 2:08:52 AM)
quote: ORIGINAL: Curtis Lemay quote: ORIGINAL: ColinWright Happily, your own lat-long program allows an objective means of mapping. Now, pick a list of rivers via some random technique: say all names with seven letters from a list of 'world's thousand longest rivers' or something. Then, map at...10 km per hex, shall we say? Use the largest city on the river as the midpoint of a 21X21 array. Put in only whatever roads are shown at a given height on Google Earth. See where your 'Matrix' puts bridges. Then ascertain where they are along those roads in reality. Time-consuming, but the results should be comic. I've already done multiple examples of this. See CFNA, France 1944, Okinawa 1945, Germany 1945, Soviet Union 1941, and Kaiserschlacht 1918. All done with the LatLong program and all made to exacting standards. And see this "house rule" in France 1944: New house rule: Bridges may only be blown if the bridge (road or rail) graphically crosses the river/canal feature, or the hex has urban terrain. That rule could be applied to most any scenario beneficially. France 1944 would definitely be worse without it. And note that that is exactly what the Matrix will effect. That's why (among other things - like good old common sense), that I know you're full of it. ? How does this relate to the validity of 'the matrix'? You appear to be asserting that 'the matrix' is somehow already employed in CFNA, France 1944, Okinawa 1945, Germany 1945, Soviet Union 1941, and Kaiserschlacht 1918 -- but I know that can't be what you are claiming. Or is it? Hell, go ahead and claim it. In for a penny, in for a pound. Claim you're the reincarnation of Buckminster Fuller if it suits you. What the hell?

ColinWright -> RE: Comprehensive Wishlist (4/27/2011 2:09:58 AM)
quote: ORIGINAL: Curtis Lemay quote: ORIGINAL: ColinWright This has gone on long enough. [image]local://upfiles/18444/5DB3E6D55BDD4F79B274A5F04F06E901.jpg[/image] Where does your matrix say the bridge is, Curtis? It says it is in the hex where the road visibly crosses the river. Which, of course, is the only rational place for it to be when the map maker drew it in that fashion. Only an imbecile would draw it that way if the bridge was in any other he... Oh. I'm sorry. Did you intend for it to be in some other hex? Mind-numbing. Why couldn't the bridge be in the uppermost hex? A road comes into the same hex as a river, runs north along it for a while, and then crosses it. What's so weird about that? Because the TOAW graphics routines put it in the lowermost? You know, it is just a graphic routine. TOAW will always put the 'bridge' in the bottommost hex in this case. If, on the other hand, the road still comes in from the left at the bottom but exits to the left at the top, it'll put in two 'bridges' -- one at the top and one at the bottom. Conversely, if the road comes in from the right at the bottom and exits to the right at the top, there'll be no 'bridge' at all. Funny, huh? How roads coming from the west always cross the river in this case but roads coming from the east never do? Isn't that weird? What made Norm think such a thing? You know, those of us who aren't Curtis probably think of this as a matter of graphic display. The tiles happen to line up so the road is to the right of the river. If the road comes from one direction, there will appear to be a 'bridge.' From the other, no 'bridge.' It has nothing to do with there actually being a bridge there in particular. That's why the actual game treats any hex containing a road and a river as a 'bridge.' Why do you think that is, Curtis? Because maybe, just maybe, any hex containing a road and a river could have a bridge? Think that's in the cards at all? I suspect you will now announce that designers should route their roads so that roads only intersect rivers in hexes where there is in fact a bridge -- or where your precious 'Matrix' will put one. But you see -- we can already do that. If designers don't want there to be a 'bridge' in a hex, they can indeed move the road -- just as you would insist that they do with your 'matrix.' So what is the point of your matrix?

ColinWright -> RE: Comprehensive Wishlist (4/27/2011 4:18:50 AM)
The solution -- Curtis' bizarre tantrums notwithstanding -- is to have designer-designated 'destroyable' roads and rails. Alternatively, do nothing at all. If the road and river coincide there's a bridge -- as from the information on the map, there could well be. If you don't want there to be a bridge, lay your road one hex off the river. As you would have to do with Curtis' 'matrix' anyway. Aside from possibly allowing him to dispense with house rules in his scenarios, I can't see the point to it at all.

ColinWright -> RE: Comprehensive Wishlist (4/27/2011 4:42:24 AM)
quote: ORIGINAL: Curtis Lemay quote: ORIGINAL: Panama From what I can tell, and it's difficult trying to follow this with so many posts, the problem is all about blowing up non bridge roads/rails because they parallel rivers. Right? This being considered a gamey aspect because if the road doesn't cross the river you shouldn't be allowed to blow it up. At least someone understands the problem. All you have to understand from there is that the Matrix will solve that exact problem. Roads that only parallel rivers and don't visibly cross them will not be blowable. If they do cross them, they will be blowable - at those exact locations. At the exact location...where the entirely arbitrary overlay of the TOAW graphics tiles makes there appear to be a bridge. All we have to do is to draw our maps so that the roads only intersect the rivers so that 'bridges' appear at only those points. Sort of like now, right? Roads will still have to be laid off of rivers to avoid bridges where there aren't bridges. The only difference will be that instead of simply staying off the river if you don't want a bridge, you'll have to take good care to veer off of it at the points where Curtis' Matrix would otherwise decide there's a bridge. Conversely, if there's actually a bridge where Curtis' matrix won't put one, you'll have to veer off and then come back on again so as to cause his 'matrix' to see a bridge. What a great idea, Curtis!

ColinWright -> RE: Comprehensive Wishlist (4/27/2011 4:49:02 AM)
quote: ORIGINAL: ColinWright [image]local://upfiles/18444/5DB3E6D55BDD4F79B274A5F04F06E901.jpg[/image] Kind of comic. Let us assume that this map is an accurate representation of where the road and river lie -- they in fact share those three hexes. Now let us assume the river is crossed in the uppermost hex only. Consider the following two alternatives. To draw it so as to avoid any other 'bridges' under the current system, you'd want to move the road off the river for the other two hexes. But with Curtis' 'matrix'... You'd want to move the road off the river for the other two hexes.

ColinWright -> RE: Comprehensive Wishlist (4/27/2011 5:02:59 AM)
Let's compare the two alternatives. What we'd have to do now to get the 'bridge' into the topmost hex under the current system. [image]local://upfiles/18444/C449CF2F7CB64A559E9280503F813F34.jpg[/image]

ColinWright -> RE: Comprehensive Wishlist (4/27/2011 5:04:00 AM)
What we'd have to do if we had Curtis' 'matrix' at our disposal. [image]local://upfiles/18444/D4A2904AEFDA42369F21A78015A44077.jpg[/image]

ColinWright -> RE: Comprehensive Wishlist (4/27/2011 5:05:11 AM)
What an improvement! Congrats, Curtis.

sPzAbt653 -> RE: Comprehensive Wishlist (4/27/2011 7:04:51 AM)
quote: I'll attach the test scenarios here if you want to check. Not really. I knew I shouldn't have said anything in the first place, because I don't have the knowledge that you and Ralph do. quote: The solution ... is to have designer-designated 'destroyable' roads and rails. But I think because we already have destroyable roads that what we need are un-destroyable roads. I think. quote: Roads that only parallel rivers and don't visibly cross them will not be blowable. Un-Destroyable roads !! I think.

Oberst_Klink -> RE: Comprehensive Wishlist (4/27/2011 7:56:40 AM)
I wasn't aware what a can of 'Sand Kings' see Twilight Zone TV pilot and not just worms I have opened. I am not a programmer but maybe the easiest solution, if possible, might be: A function/flag in the drop down menu in the editor simply where one can mark/flag those parallel road hexes (kinda like the possession 'thingie') as 'treat road/hex as bridge (Y/N)' Just my 2p. kLiNk, Oberst

ColinWright -> RE: Comprehensive Wishlist (4/27/2011 10:06:09 AM)
quote: ORIGINAL: Oberst_Klink I wasn't aware what a can of 'Sand Kings' see Twilight Zone TV pilot and not just worms I have opened. I am not a programmer but maybe the easiest solution, if possible, might be: A function/flag in the drop down menu in the editor simply where one can mark/flag those parallel road hexes (kinda like the possession 'thingie') as 'treat road/hex as bridge (Y/N)' Just my 2p. kLiNk, Oberst It seems to me that all this -- and more -- can be accomplished if we make it possible to mark roads/rails 'destroyable' rather than 'undestroyable.' A road/rail cannot be destroyed unless the appropriate tile has been selected. From a programming point of view, all that is necessary is that there be two additional tile slots that the current destroy/repair bridges routines can point to. Then we can not only avoid bridges where we don't want them -- but we can also make any non-river hex we see as subject to serious blockage 'destroyable.' Those who feel such a thing shouldn't happen can refrain from putting such hexes in their scenarios.

Panama -> RE: Comprehensive Wishlist (4/27/2011 1:25:27 PM)
Destroyable, undestroyable, matrix, flags, tile sets. Whatever. What's there now isn't really very good. The world is adrift in roads that follow rivers. Maybe we can get highway engineers to move them back from the rivers 100km. That would solve the problem for any future scenario designers but you would still have the ones that were there in the past. I suppose we could use Mr. Peabody's Wayback Machine. [:'(] We want to see something that works 100% of the time. Roads/rails that cross rivers can be blowed up. Roads/rails that parallel rivers are not bridges, never were intended to be bridges and no amount of obfuscation can make them bridges so don't allow them to be destroyed. Believe it or not, I think Norm actually thought people would be smart enough to know when a bridge is a bridge. [sm=terms.gif]

Curtis Lemay -> RE: Comprehensive Wishlist (4/28/2011 2:14:31 AM)
quote: ORIGINAL: ColinWright quote: ORIGINAL: Curtis Lemay I've already done multiple examples of this. See CFNA, France 1944, Okinawa 1945, Germany 1945, Soviet Union 1941, and Kaiserschlacht 1918. All done with the LatLong program and all made to exacting standards. And see this "house rule" in France 1944: New house rule: Bridges may only be blown if the bridge (road or rail) graphically crosses the river/canal feature, or the hex has urban terrain. That rule could be applied to most any scenario beneficially. France 1944 would definitely be worse without it. And note that that is exactly what the Matrix will effect. That's why (among other things - like good old common sense), that I know you're full of it. ? How does this relate to the validity of 'the matrix'? You appear to be asserting that 'the matrix' is somehow already employed in CFNA, France 1944, Okinawa 1945, Germany 1945, Soviet Union 1941, and Kaiserschlacht 1918 -- but I know that can't be what you are claiming. I am claiming that the house rule in use in France 1944 - and can probably be beneficially used in almost all other scenarios, is just what the Matrix will officially enforce.

Curtis Lemay -> RE: Comprehensive Wishlist (4/28/2011 2:23:19 AM)
quote: ORIGINAL: ColinWright quote: ORIGINAL: Curtis Lemay quote: ORIGINAL: ColinWright This has gone on long enough. [image]local://upfiles/18444/5DB3E6D55BDD4F79B274A5F04F06E901.jpg[/image] Where does your matrix say the bridge is, Curtis? It says it is in the hex where the road visibly crosses the river. Which, of course, is the only rational place for it to be when the map maker drew it in that fashion. Only an imbecile would draw it that way if the bridge was in any other he... Oh. I'm sorry. Did you intend for it to be in some other hex? Mind-numbing. Why couldn't the bridge be in the uppermost hex? A road comes into the same hex as a river, runs north along it for a while, and then crosses it. What's so weird about that? Because map designers aren't mindless. They are conscious beings. They can see what their maps look like as they draw them. They can see where the bridge is located by the graphics, and if it was supposed to be in the upper hex, they won't draw it that way. They'll draw it so that it crosses the river at the upper hex. But, even if they didn't, the matrix improves the game because it limits the number of bridges to one. As things stand, there would be three. Number of bridges is more important than their exact location. It's the difference between having to repair one bridge and having to repair three. That impacts the game more than having the bridge be off by a hex or two. It also improves the game by giving the players a natural visual as to where the bridges are. They're where the road graphically crosses the river.

Curtis Lemay -> RE: Comprehensive Wishlist (4/28/2011 2:27:22 AM)
quote: ORIGINAL: Panama We want to see something that works 100% of the time. Roads/rails that cross rivers can be blowed up. Roads/rails that parallel rivers are not bridges, never were intended to be bridges and no amount of obfuscation can make them bridges so don't allow them to be destroyed. And, again, that is exactly what the Matrix will do. Colin is still trying to convince you that road/rails that parallel rivers are bridges and should be treated as bridges. Don't buy his Kool-aid.

Curtis Lemay -> RE: Comprehensive Wishlist (4/28/2011 2:38:52 AM)
quote: ORIGINAL: ColinWright At the exact location...where the entirely arbitrary overlay of the TOAW graphics tiles makes there appear to be a bridge. Since it was drawn by a conscious being, there's nothing arbitrary about it at all. quote: All we have to do is to draw our maps so that the roads only intersect the rivers so that 'bridges' appear at only those points. Sort of like now, right? No. Roads that parallel rivers will no longer be treated as bridges. quote: Roads will still have to be laid off of rivers to avoid bridges where there aren't bridges. Only on the southwest side. Roads on the northeast side can join and then run along the river. And note that TOAW can't show a road running parallel to a river on the SW side. Why would anyone want to draw their map so that a road running on the SW side of a river looks like it is running on the NE side? quote: Conversely, if there's actually a bridge where Curtis' matrix won't put one, you'll have to veer off and then come back on again so as to cause his 'matrix' to see a bridge. Or put a stub tributary there. No game effect - same as a "blowable" tile - except it has the advantage of giving players a visceral notice that there is a bridge in the hex.

Panama -> RE: Comprehensive Wishlist (4/28/2011 5:40:10 PM)
When can people expect to see any changes take effect? If I had my druthers I'd rather see bridge tiles. [:D]

ColinWright -> RE: Comprehensive Wishlist (4/28/2011 6:33:07 PM)
quote: ORIGINAL: Curtis Lemay quote: ORIGINAL: ColinWright quote: ORIGINAL: Curtis Lemay I've already done multiple examples of this. See CFNA, France 1944, Okinawa 1945, Germany 1945, Soviet Union 1941, and Kaiserschlacht 1918. All done with the LatLong program and all made to exacting standards. And see this "house rule" in France 1944: New house rule: Bridges may only be blown if the bridge (road or rail) graphically crosses the river/canal feature, or the hex has urban terrain. That rule could be applied to most any scenario beneficially. France 1944 would definitely be worse without it. And note that that is exactly what the Matrix will effect. That's why (among other things - like good old common sense), that I know you're full of it. ? How does this relate to the validity of 'the matrix'? You appear to be asserting that 'the matrix' is somehow already employed in CFNA, France 1944, Okinawa 1945, Germany 1945, Soviet Union 1941, and Kaiserschlacht 1918 -- but I know that can't be what you are claiming. I am claiming that the house rule in use in France 1944 - and can probably be beneficially used in almost all other scenarios, is just what the Matrix will officially enforce. So the purpose of the engine is now to enforce your house rules? Funny -- how many other people use these house rules? I think that gives us a good count on the general utility of this change.

ColinWright -> RE: Comprehensive Wishlist (4/28/2011 6:36:10 PM)
quote: ORIGINAL: Curtis Lemay quote: ORIGINAL: Panama We want to see something that works 100% of the time. Roads/rails that cross rivers can be blowed up. Roads/rails that parallel rivers are not bridges, never were intended to be bridges and no amount of obfuscation can make them bridges so don't allow them to be destroyed. And, again, that is exactly what the Matrix will do. Colin is still trying to convince you that road/rails that parallel rivers are bridges and should be treated as bridges. Don't buy his Kool-aid. As I've demonstrated by referring to three completely different rivers flowing through completely different types of terrain, a road that appears to be 'paralleling' the river is as likely to contain the bridge as any other hex containing the river and the road. This is up there (or down there) with your 'wadis are trenches' claim. Worse, this time you are asserting that you're actually going to impose your nonsense on the rest of us.

ColinWright -> RE: Comprehensive Wishlist (4/28/2011 6:37:15 PM)
quote: ORIGINAL: Panama When can people expect to see any changes take effect? If I had my druthers I'd rather see bridge tiles. [:D] We don't get our druthers, apparently. We get what will allow Curtis to dispense with house rules for his scenarios.

ColinWright -> RE: Comprehensive Wishlist (4/28/2011 6:47:24 PM)
quote: ORIGINAL: Curtis Lemay Why would anyone want to draw their map so that a road running on the SW side of a river looks like it is running on the NE side? Ummm... Because the available graphics give them no choice? Because in fact the road is in that hex? Because moving it, aside from being inaccurate geographically, will create worse problems? It seems to me that road winds up in that hex for about the same reasons anything winds up in any hex. You want to substitute a routine that will declare some hexes bridges and others not without reference to the reality on the ground for a routine that at least has the virtue of simplicity and clarity. Currently, you put a road into a river hex, you know you're going to get a bridge. With your change, one will have to go -- 'oh this makes it a bridge. Now, how can I route things so that it's not a bridge?' What's the point of that? Aside from helping you to clean up your scenarios, that is? Everyone else who is participating in this discussion either wants (a) hexes that can be designated as bridges without constraint, or (b) hex-side rivers. For good reason. Those are the alternatives to the current system that actually accomplish something. See the examples posted above. Your 'matrix' does nothing. It's the worst idea since the concrete zeppelin. Worse, it would appear that somehow you've acquired the ability to impose this idea on the rest of us.

Panama -> RE: Comprehensive Wishlist (4/28/2011 7:44:26 PM)
quote: ORIGINAL: ColinWright Everyone else who is participating in this discussion either wants (a) hexes that can be designated as bridges without constraint, or (b) hex-side rivers. For good reason. Those are the alternatives to the current system that actually accomplish something. See the examples posted above. Your 'matrix' does nothing. It's the worst idea since the concrete zeppelin. Worse, it would appear that somehow you've acquired the ability to impose this idea on the rest of us. As long as we're shooting for the Moon here, when can we have a bigger unit database? And the ability to flush weapon systems out of a units TO&E so we can do away with the lame transition process we're stuck with now?

ColinWright -> RE: Comprehensive Wishlist (4/28/2011 7:54:06 PM)
quote: ORIGINAL: Panama quote: ORIGINAL: ColinWright Everyone else who is participating in this discussion either wants (a) hexes that can be designated as bridges without constraint, or (b) hex-side rivers. For good reason. Those are the alternatives to the current system that actually accomplish something. See the examples posted above. Your 'matrix' does nothing. It's the worst idea since the concrete zeppelin. Worse, it would appear that somehow you've acquired the ability to impose this idea on the rest of us. As long as we're shooting for the Moon here, when can we have a bigger unit database? And the ability to flush weapon systems out of a units TO&E so we can do away with the lame transition process we're stuck with now? 1. What do you mean by a 'bigger unit database'? 2. As to weapons transitions, I've advocated introducing an absolute cap on on how many weapons can be in a unit. That would have addressed many of the problems without excessive complication -- but as I recall, the idea ran into Blocking Detachment LeMay. The discussion is somewhere...

Page: << < prev 50 51 [52] 53 54 next > >>

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

1.078125