Open GoogleCodeExporter opened 9 years ago
Only the commander aspects of the commo-rose work eg. calling arty (although
arty doesn't work in BF 1.5, it does if you use 1.41), move orders also works.
However squad-level use is impossible eg. calling for a ride, follow orders...
practically everything else in the rose.
Original comment by mydji...@gmail.com
on 4 Apr 2011 at 6:14
OK, cheers :). I'm in the process of documenting exactly what does / does not
work in this UI. For example the arty spotting part works (prev/next target) if
you have already created a spotting target using binoculars. When this is done
I may put in some more fine grained issues.
Original comment by djbar...@djbarney.org
on 4 Apr 2011 at 9:51
Original comment by djbar...@djbarney.org
on 24 Apr 2011 at 10:02
Part of some of the confusion over this (or was it just me that was confused,
anyway) has been that only the Spotting classes (any class with binoculars) can
actually spot anything so that the icon of the spotted asset appears on the
map. This is standard FH behavior, so allowing all classes to spot using the UI
(comma rose) would not be in line with FH behaviour. Single players are
probably not familiar with those parts of the on screen command/spotting
interface that in MP actually vocally calls out spots to soldiers immediately
around you. These do no appear on the map. I'll put in a separate issue for
possibly allowing bots close by to use those spot shouts in some way.
I've looked at the command part of the UI in the python files and it looks
relatively simple to link up the squad functions again.
Original comment by djbar...@djbarney.org
on 7 Feb 2012 at 9:01
Issue 32 has been merged into this issue.
Original comment by djbar...@djbarney.org
on 23 Feb 2012 at 8:02
Original comment by djbar...@djbarney.org
on 23 Feb 2012 at 8:19
Original comment by djbar...@djbarney.org
on 26 Feb 2012 at 9:20
[deleted comment]
Getting BF2 comrose events into python!:
http://www.bfeditor.org/forums/index.php?showtopic=5297
Original comment by djbar...@djbarney.org
on 23 Mar 2012 at 1:43
Original issue reported on code.google.com by
djbar...@djbarney.org
on 2 Apr 2011 at 1:23