ORIGINAL: AlphaSierra
Translation: yeah so the stores not open.
If you are interested in purchasing Command-PE and are representing a company or organization, please contact us through the address provided on the Command PE page. Thanks.
Moderator: MOD_Command
ORIGINAL: AlphaSierra
Translation: yeah so the stores not open.
ORIGINAL: Sunburn
ORIGINAL: AlphaSierra
Translation: yeah so the stores not open.
If you are interested in purchasing Command-PE and are representing a company or organization, please contact us through the address provided on the Command PE page. Thanks.
ORIGINAL: Grazyn
You think you want editable database, but you don't.
As far as realism is concerned, you won't find more reliable public-access data about units than what is already in the game, and developers keep the database up to date when new stuff is released. So there isn't really an issue of being unable to give a unit its "true" performance, because it's already there. And if you have better data, you're likely some government or military-industrial complex insider who can buy the pro version anyway.
So this only leaves your ability to tweak a unit's features as you like, usually in some unrealistic way... but this would turn into a nightmare for the dev team. Tech support already has to deal with bug reports, fake bugs, scenario bugs, lua bugs, features that are taken as bugs, simple misunderstandings and so on, all stuff that is to be expected with a game so complex... and on top of that, they would have to take into account user ability to edit the database, which would obviously introduce a whole new swathe of user-made bugs. "Yes hello I have to report this bug, my script is not working as intended and there's something odd with unit behaviour... oh did I mention that I edited that frigate to run at the speed of light and that f-35 to fly underwater at -3000 ft? What do you mean you can't help me because I edited them? Then why have the feature in the first place? I paid good money for this game etc. etc. etc."
ORIGINAL: Zaslon
I do not understand the answers in this thread.
You cannot tell any other user what he want or what he need. That's called Freedom. [X(]
This kind of attitudes are commonly used in communist countries, where other people (Nomenklatura) decides where you must work, what do you need and of course, tell you what you must think.
If someone has the money...Why not sell it the Pro version?
That's called Capitalism. [:)] Have the money? go ahead!
With the fall of the Soviet Union, we forget some important terms and we are losing by the way important rights.
P.S. Of course WarfareSims has the choice to sell or not to sell. But I don't understant why you are telling Ilias what he need and what not. THat's simple. If he has the money...Use it if you want.
Currently available functionality exclusive to Command PE:
◾NEW in v1.12! Integrated script-less communications jamming (ties with the new comms disruption feature)
◾NEW in v1.12! Directed tactical-EMP weapons (e.g. CHAMP)
◾NEW in v1.12! Hypersonic Glide Vehicles
◾NEW in v1.12! TCP/IP socket access to Lua API (ie. any external application can manipulate the running simulation via Lua calls)
◾Full database editing
◾Ability to use on-demand commercial imagery – MS Bing Maps
◾Monte-Carlo analysis
◾Import external data in XML format
◾Export event notifications to files/databases or external data consumers
◾Ability to override Command’s internal mechanics (use your own custom models)
◾Ability to export to Tacview for 3D visualization
◾Source code licensing
Planned features:
◾Integrated asynchronous-WEGO multiplayer mode with optional Umpire and Observer modes
◾Extended costing
◾DIS/HLA integration
◾Ability to use on-demand commercial imagery – Other providers such as Google Maps
Thanks for great spot,ORIGINAL: HalfLifeExpert
From the Developer's website:Currently available functionality exclusive to Command PE:
◾NEW in v1.12! Integrated script-less communications jamming (ties with the new comms disruption feature)
◾NEW in v1.12! Directed tactical-EMP weapons (e.g. CHAMP)
◾NEW in v1.12! Hypersonic Glide Vehicles
◾NEW in v1.12! TCP/IP socket access to Lua API (ie. any external application can manipulate the running simulation via Lua calls)
◾Full database editing
◾Ability to use on-demand commercial imagery – MS Bing Maps
◾Monte-Carlo analysis
◾Import external data in XML format
◾Export event notifications to files/databases or external data consumers
◾Ability to override Command’s internal mechanics (use your own custom models)
◾Ability to export to Tacview for 3D visualization
◾Source code licensing
Planned features:
◾Integrated asynchronous-WEGO multiplayer mode with optional Umpire and Observer modes
◾Extended costing
◾DIS/HLA integration
◾Ability to use on-demand commercial imagery – Other providers such as Google Maps
You, guys, are talking like there are no errors in the DB. There are. Lots of units are inaccurately represented. Here is an example: su35 in the lattest patches got reduced RCS due to RAM coating and other work in this direction, but for 2-3 years su35 had almost the same RCS as su27 despite wiki clear statement that reduced RCS of su35 was one of the requirements of Russian MOD. There are lots of such ill-represented units.ORIGINAL: HalfLifeExpert
Indeed, and if by some chance you do have better and more accurate data on a modern system, and are not in a Nation's defense forces and/or industry, I must ask how you got classified information, and can only hope the proper authorities can catch you. If someone gave me a packet of the real full specs on the F-22 Raptor's true capabilities, I would throw it back in their face and contact the authorities ASAP. There are some things we are just not meant to know, at least not yet. Perhaps we can learn the true Raptor capabilities in 15 years or so.
ORIGINAL: thewood1
but nothing on the RCS issue.
Soo., shouldn't you do that then ?ORIGINAL: User2That's what I was talking about. Nobody reported it.ORIGINAL: thewood1
but nothing on the RCS issue.
Same as mig35 rcs and other issues.
To get the reason I did not report su-35 rcs issue you should get pre patch DB3k 466 database, where su-35 rcs is not fixed, then look at su-35 rcs (both against high and low freq), then look at another russian 4++ plane - mig-35, then look at rcs of western 4++ planes (f/a-18 super hornet, jas 39 gripen, eurofighter). It was already discussed in db3000 thread with lots of examples: db is biased. I actually do not want to raise that question again here.Soo., shouldn't you do that then ?
Technically ASBMs like DF-21D are HGVs. And they do not require Pro version to use.ORIGINAL: DrRansom
On the topic of hypersonic glide weapons, there should be more than enough open source knowledge to build a decent model of them. The only thing which is missing would be kinetic effects, but that could be approximated to a reasonable extent.
Childish move to start a flame. Su35 issue was just an example. Do you know what is example, right?your pet
Find me a post where somebody reported that issue. I personally did not report it. It seems nobody did.Hold on...There was one comment, an off handed one, about the SU-35 and then the RCS was adjusted. So did you point out the issue after that?
ORIGINAL: User2
You, guys, are talking like there are no errors in the DB. There are. Lots of units are inaccurately represented. Here is an example: su35 in the lattest patches got reduced RCS due to RAM coating and other work in this direction, but for 2-3 years su35 had almost the same RCS as su27 despite wiki clear statement that reduced RCS of su35 was one of the requirements of Russian MOD. There are lots of such ill-represented units.ORIGINAL: HalfLifeExpert
Indeed, and if by some chance you do have better and more accurate data on a modern system, and are not in a Nation's defense forces and/or industry, I must ask how you got classified information, and can only hope the proper authorities can catch you. If someone gave me a packet of the real full specs on the F-22 Raptor's true capabilities, I would throw it back in their face and contact the authorities ASAP. There are some things we are just not meant to know, at least not yet. Perhaps we can learn the true Raptor capabilities in 15 years or so.
Do not get me wrong. The scale of DB is VERY large. Thousands of units. Dev team is small. I do not expect them to quickly polish the DB. What really disappointing is that players do not bother reporting such issues. It seems nobody cared about reporting su35 rcs issue. Am I the only one who visits wiki while playing the game? Almost every scenerio, I find at least one unit whose characteristics contradict wiki.
So I think it is not a bad idea to select 3-4 reliable fans of the game, give them an ability to modify DB, create new thread where people will post there requests in the form of SQL commands and let those fans verify incoming requests and modify DB. SQL form of requests will allow those volunteers to quickly modify DB using official sqlite tools (https://sqlite.org/cli.html). User modifies DB, uses sqldiff tool to create a txt file with a set of sql commands needed to modify original DB, posts that file in the thread, writes a brief description. Selected volunteer checks the request, uses sqlite3 tool with that file to make changes to the original DB, posts the modified DB on the forum. Now users use this new DB for their next requests. Time to time devs merge that user DB with the official DB and add it to the base game.
Well, it will not allow to add new units due to the problems with RCS estimating and submarine noise level estimating. But will quickly eliminate small errors in the DB unit parameters like speed, cruise level, max distance, armor level, missing flags, typo, etc.
You are mixing two different points. I made a proposition to allow some fans to help devs. It is win-win situation for everyone in my opinion. I'm sure there are people who are willing and have spare time to help at polishing DB. I DO report some small issues in the DB and propose time to time new units to add to DB. I do not report rcs issues because some questions someone asked in the db3k thread about rcs remained unanswered (for example, about the source of information used for tomahawk and kalibr cruise missiles - they have similar dimensions but different rcs). I just do not see a point reporting it.I don't understand, you want editable database because you think it's not accurate, people tell you that you can just report any accurate data you have in the thread, but your answer is that you don't report stuff anyway because you think devs are biased against non-western units?
Yep. Wiki is a good starting point, but it should be verified ofcouse. For example, english Mi-24 wiki page states that the helo hull is armored. But other sources state that it is not. Only cockpit and some engine parts have armor plates. The game's DB it seems uses english wiki data - mi-24 hull in the game is armored, while engine - not.So saying "despite wiki clear statement" is not a strong argument here.
That can make sense, but if issue exist report it for highest good regardless of existence of situation in past where it was unresponded [:)]ORIGINAL: User2
..I do not report rcs issues because some questions someone asked in the db3k thread about rcs remained unanswered..
+1 (didn't deeply looked into DB, so can't say alot about, but agree what its important to keep right)ORIGINAL: User2
..biased against any side DB. I hope it will not happen.
Grazyn, descriptions, similar as image packs, is community project. Descriptions are taken by various users from different sources (also from the wiki) and serve for better understanding of specific units. They have nothing to do with the unit data source. Unit data are directly managed by developers.ORIGINAL: Grazyn
If they don't consider wiki a reliable source, then why are most unit descriptions copypasted from wikipedia? [:D]