Leaderboard

YOU stole my idea , my 'alter me's' are GGTharos ,Pilotasso and BritGliderPilot.:D

Hi folks, I have mentioned it allready in my A-10 Fueltank threat. Now, after I have fixed in the last few days alot of problems on the so far built model, I want to show you some of my official projectpics. I have decided, that it might be lovely to have such a bird as flyable plane, that has its own 3D cockpit. As far the arguments for the cockpit are read out and luckily the SR71 Blackbird has an analog cockpit, so it should be possible to built a nice and smoth one. I hope you like it so far and when somebody has any suggestions, please feel free to comment. :-) http://www.spongedpics.com/upload/WB1186883406W46be674ece60c-SR7110.jpg http://www.spongedpics.com/upload/WV1186884074W46be69ea0d6cf-SR719.jpg

16 September 2007 I’m afraid that there is not much to report since my previous one. The Ka-50 is just about done at this point and we’re mostly focused on testing and bug-fixing its systems. The big item in work in the mission editor (about 80% complete, the campaign builder interface, new pilot log book, and other various GUI screens. Once we get a testable mission editor, I’ll post a little overview of functionality. ---------------------------- 10 August 2007 Currently the team is testing build 33 which added a new airfield to the simulation world and increased the height field and texture resolution of large portions of the map (most evident in the mountainous areas). The Mineralnye Vody area has a particularly detailed height field. We’re also been adjusting the world shaders for a more contrasted image. Personally, I think it looks better. We’ve also incorporated the tree edits by our newest test team member, TekaTeka. The mission editor is progressing nicely and I had a chance to take a look at a test build this past week. The new map technology and scripting ability will be a pretty dramatic change from previous Eagle products. Since coming to work with Eagle since my Jane’s F/A-18 days, I’ve wanted to have much better mission scripting tools. This ME is a huge step in that direction. Hopefully within the next couple of weeks the ME will be available to the test team to start banging on. It looks like we’re nearing the homestretch for the Ka-50 modeling. A few items with the fire suppression system, auto-pilot modes and caution/warning system remain, but on the whole things are starting to look pretty solid. The flight model will probably continue to be tweaked but right now it feels very tight. Given the nature of helicopter combat, a great deal of time has been spent working on the helicopter and ground vehicle AI. This work continues, particularly because the AI helicopters now use a much more advanced flight model and this needs to be accounted for by the AI. That’s it for now; I’ll try to do another update in a few weeks after ME and campaign system has been integrated into to the code base. ---------------------------- 24 July 2007 At this time, the beta team is busy testing the 6 DOF cockpit, avionics, flight dynamics, damage model, AI, weapon systems and terrain. Additionally, much of the manual has been written and is in edit now (the bane of my existence the last few weeks). Items currently being working on by Eagle include: 1- Finishing on the Ka-50’s INS and INS alignment system 2- Finishing the caution detection and alert system of the Ka-50 3- Debugging some of the Shkval functions 4- Completing the new Mission Editor system 5- Completing the new campaign system 6- Tuning AI aircraft flight dynamics 7- Tuning AI aircraft and ground vehicle AI 8- Need to complete several new AI vehicles like the UH-60 and Mi-17 9- Complete modeling of new and existing terrain with higher resolution elevation matrix and terrain textures—needed for low altitude flight detail. 10- Adjusting network play to work with new Mission Editor functionality Once the mission editor and campaign system have been integrated and finalized, there will be the large task of creating and debugging all the missions and campaigns. As to when the above will be completed, integrated together, fully debugged and available for purchase… it is still impossible to attach an exact date. However, rest assured that the team wants to complete the project even more than any of you. However, we don’t want to rush it out the door in an incomplete state just to have it available sooner rather than later. Regarding the release of all the new Black Shark ground vehicle and helicopter screen shots, most of these vehicles are being done by contracted 3rd party. As such, they have virtually no impact on other product features. Release details will be provided later, but we have every intention to release the product both on-line and through retail (boxed) versions. The method of copy protection has not been determined and is something we are still investigating. The Black Shark project is solely focused on the Ka-50; as such, it will have no impact on the Lock On and FC flyable aircraft. While we still wish to do a final FC patch that will focus on air-to-air systems, we can only do so when the internal resources are freed up to do so. I’m afraid that I just cannot give you an estimate as to when or if this will happen – too many other things influence this. All in all, Black Shark is marching ahead and I believe it will be well worth the wait. ----------------------------------- 31 May 2007 I realize that many of you wish to learn more about the product (happy to see that level of interest), but we're just not at the point yet to discuss the product in detail. There are many features still in development, and until they are actually in the game, we do not want to announce them. Things you announce before they are done have a nasty habit of not getting done (remember the planned dynamic campaign for Lock On?) Unlike years past, we do not have the marketing arm of a large publisher breathing down our necks, so, we're going to hold off on saying more than we already have until the product is essentially feature complete. Probably sometime in July, we'll be making some pretty big announcements with lots of new information. Until then, please sit tight and enjoy the quiet of the next month. It's going to get very loud come July. ------------------------------------ 05 March 2007 Regarding a release date for Black Shark, the original dates have been moved back due to two primary reasons: 1- While in years past TFC/Eagle has been primarily focused on the entertainment market, this has changed over the past year. Much of our work now is also focused on supporting military simulation contracts. Some of you may have heard about the A-10C PE Desk Top Simulation (DTS) for the U.S. ANG that we're just finishing up. Due to the demands of this project and others, the bulk of our engineering resources had to be shifted away from Black Shark this year. Thankfully, these resources are now being shifted back. As other projects come up and we have to reprioritize resources, it's possible that Black Shark resources will once again need to be shifted, we just don't know right now. Because of this dynamic nature, trying to pin down the actual release date is problematic and could turn out to be grossly inaccurate. As such, we find it best to keep the release date very loose at this time until the project is close enough to completion that we can accurately predict its ship date. 2- Although the original plan for the Ka-50 project was to just add the Ka-50, it has grown substantially greater than this. Be it a new mission editor system, advances in ground unit and helo unit AI, new AI units, etc., all of these have contributed to the time and resource budget necessary to complete the project given a constant-size staff. So, although this has pushed dates back, you will get a much more feature-rich product in the end. Regarding feature details of the project... I realize that many of you wish for a lot more information and I can promise you that it is indeed coming. However, we have a specific publishing plan that will release many details, videos, developer logs at the proper time prior to the projected release (at no charge). Looking back at the experience of Lock On, we do not wish to start this process to soon and be accused of over-hyping the product and promising features before they are in fact in and working in the code. We’ve already been down that road and it was a bumpy one. Much of the team is now working on Ka-50 again and a 2007 release still looks likely. Beyond that we will have to ask for your patience as we move forward. As I get new information regarding the status of the project I will be posting it. ----------------------------

Do you have plans for release one Demo of BlackShark when it is done??:music_whistling:

Black Sea Showdown Firstly, I’d like to thank the 159th Squadron, everyone else involved and especially Fudd for showing that organised operations with the Lock On Community can be a resounding success. Here is the 169th contribution for a similar (but different) exercise. On the last Saturday of every month at 2100Z (Greenwich Mean Time), We will host a closed (password) session on the 169th dedicated server via IP only. It will be a “Grand Finale” to the mission that has been hosted on the server for that month. It will run for 4 hours exactly. Any aircraft that have not landed at an airfield at the close will be considered as dead. The exact scoring system is still being finalised but Aircraft losses will be severe as will be Team Kills. Priority targets such as Ships will score highly. The 169th Statistics Board which now supports Air to Ground statistics will be the scorer and a separate database will be created specifically for this encounter. We also recommend everyone record their track so as they have evidence of any possible discrepancy. 169th members will be separated between both sides so as not to give the impression of a 169th verses the world. How to sign up. Register to our Forums and in the “Black Sea Showdown” Forum Category sign up in the Sign Up Thread and also request which side you wish to join. You will then be given access the appropriate section where mission planning for your team can take place. When registering, please use your regular callsign as per HyperLobby. This is to minimise the chance of dual registrations or spies. All participants will be required to use Teamspeak during the match. There are some real benefits in this format. One being the ability to run events more frequently. Less pressure on planning and the ability to practice your sorties in an environment with human opposition at any time. Rules: The 169th Dedicated Server Rules must be adhered to as well as the Online Etiquitte. Up to 64 players can register plus reserves. That’s 32 per side. You will be allowed to respawn. You will be allowed to change aircraft. If by chance the Red Team lose their Kuznetsov carrier then the Su-33’s that took off from it must change to another group. Any players in Su33’s that spawn over Bulls Eye (Nav 1) will immediately be removed from the server. As this is the first round of hopefully many this post will most likely see some changes so check it regularly. 169th Members whom have Admin rights to our forums are NOT to get involved in any planning. Namely, Ice, PoleCat, ManaWar, Helix. Finally I’d like to see all squadrons put aside their differences and participate in this exercise with the same energy as they have in Red Flag. Our community is small and needs all the help it can get. No doubt there will be some that do not approve of this idea. However I ask that you refrain from posting negative replies and just not get involved. Good Hunting!

I'm a bit curious on how the forum.lockon.ru rep system works. Do you need something like 5-10 rep sent to you to get one extra below your avatar? Perhaps it requires a few reps sent for one post? //Yoda :)

Подтверждаю, видел со стороны этот момент :) Никакого принтскрина не было. Собственно я и предупредил Ульриха, ну а потом просто сблизился с врагом и дальше дело техники...

What I did was, registered myself 4 times and repped myself out as much as I could :)

I have seen many of these wars. I would think even in real life the A10 could out manuever an Su-25T, it just looks like it should be able to. But, for anyone who thinks the Su25T is too hard to fly, just dont know how to fly it. I rarely blow tires on landing or taxi. I have no problem getting lined up well before 40km. No problems flying low, getting to target area. Only problem I have is being real accurate with the cannon, and thats not just the 25T. Key to the 25T... AoA gauge. Watch it, and dont go red. If you do, she will want to roll over on you.

А чего, собственно, "ждем-с"? Ссылка на первоисточник нарисована, перевод дан.. что еще нужно? Не надо пытаться искать скрытый смысл там, где его нет. Можете не верить - но на аглоязычном форуме многие убеждены в том, что команда ED в первую очередь разговаривает с русской частью форума, отвечает на их вопросы, а "англичан" игнорирует.

:bounce: ждёмс... Хоть кто-то говорит что-то определённое. Англоязычная часть руководства проекта имеет приоритет в озвучивании текущего состояния? Боссы говорят по-английски?

good question, now you deserved to get rep :D

I have a question too, why does Yoda not talk like Yoda should? :chair:

Нельзя ли зделать для ночного времени суток ночные карты, а для дневного времении - дневные карты? Реализъм:smartass:

Hrmmm i see it too... there appears to be large red arrows pointing at nothing in particular in F2 view...odd Just kidding... yeh I haven't seen this either... I would try the above then reinstall

Players calling othe players noobs for playing just ONE plane is silly. Its like saying you dont like a dish that you have never tasted. I flown both and I can tell while the A-10 is easier to fly it has downgraded weapons compared to the ultra long range weaponry of the 25T and its even slower wich makes missions an exercise of greater patience.

Yoda Inbound Rep Is......:pilotfly:

Прошу не пинать если такое пожелание уже высказывалось. Хотелось бы наличие сценария отказов после повреждения, так сказать влияние работающих или вышедших из строя систем на функционирование систем в общем. Например, поврежденный генератор или преобразователь напряжения через Х мин выключает Y блок (абрис, ИЛС и т.д.) Причем статистику отказов лучше представить в виде отдельного, закрытого алгоритма, а не задовать время начала, продолжительности, окончания отказа, как сейчас. Откуда я знаю когда мне выбъют генераторы, чтобы у меня оключился, например, абрис. А вообще, говорилось же про разработку системы ЭКРАН. Я так понимаю будет не просто информирование (индикация) отказа, но и процедуры (команды) его устранения?

i dunno these days all your is Harry Potter's invisibility cloak which is impervious to all detection spells

lol, this is the most creative way of asking for AFM for more aircrafts that I've seen :lol:

Thanks for the info! I did not start this thread to beg for rep points, but I will not refuse them if you feel like you have to hand some over :music_whistling:. I just wanted to know how it works. EDIT: Man now everyone will make fun of me with rep messages xD. Guys ....I honestly mean I did NOT start this thread to ask for points, I appreciate getting them , but this was just meant as a question.

You can give people positive rep or negative rep depending on their post. Once a lot of people give you rep, that turns into 1 green square under your avatar. I don't know how many it takes to get you one though. Also, once you past a certain amount of post, you could also get one extra green box. For now, i'll give you a rep and you can check it under your user CP on the top left corner of the forum,

Send me rep ten times and I'll tell you what happens!! :music_whistling::smilewink:

Ah thats what you ment. Well I didn't put any scale on the radar to avoid this problem but it seems that i failed anyway. ;) I'll try to keep that in mind for the next movie including an AWACS radar. ;)

Did you realize that the T-80 was not a real picture but a rendering? Here another one, copyrighted awarded rendered image by LOFT © 2007:

Ok we first off I am getting sick of other players getting upset with the 169th because they think we are a bunch of bullies or a stuck up group that thinks our Sh@# don't stink. We pay for this server so YOU have some place to fly. WE admin it and put rules on it to make it FAIR for all. As long as I have been in the 169th we have tried to increase the popularity of the Lock On community. With comments from people such as you kuky it is easy to see why so many new players simply snuff Lock On off as a bad game. We try to give everyone a great time and it is not EASY. Making the world happy is impossible. However we do have more people that like the server than not. If you have bad comments please keep them out of threads that are trying to be informative. You have a problem with a 169th pilot let that pilot know in a PM. Slinging crap talk and crying that someone thinks they are better than someone is just killing the community. I personally tend to ALL the hardware for the 169th server. I am the main network and system engineer. You have questions or a concern about the server hit me up in HL or on our site. I will be happy to answer questions. Keep in mind YOU do not PAY for this server nor do you admin it. We enjoy HELPFUL comments on what you think can make it better. You say u get low FPS try and get me a track of it so I can check times and logs on the server. If it is indeed a server issue then it can be fixed. However I rarely hear of anyone having issues. All this BS has got to stop it is a waste of time and gives the entire Community a giant black eye. I have friends that will no longer play for the fact that people piss and moan too much. Take this how you want and flame me all you want. I will however disregard anyone that is trying to pick a fight or just is simply being an A#! I am a nice guy and willing to help where I can when I can. Not saying I am the best out there or that I know everything. But I am very capable of doing my Job in the 169th.

Не уверен, что все верно и точно, но в целом, вроде, так. :)

A small update from my side :) Some time ago I made a small circuit which we will use in the base of our stick, based on MJoy. A few days ago my gameport broke down, so I couldn't use my Suncom HOTAS anymore. Right now, I'm modding the MJoy circuit into the Suncom HOTAS, so I can connect the whole lot to a USB port. In order to keep the Suncoms programmable buttons, I decided to rewire only the potmeters, and leave the buttons wired to the original circuits. This is how it will eventually be connected: The console I put in the schematic will contain all buttons from the MJoy. I entered "16 BTN", because the easiest way to get things going is to use a piece of UTP, which has 8 wires. With those wires I can make a 4x4 matrix, supporting 16 buttons, which is enough for the first tests. The rest (12 more buttons and two potmeters) will be added later on. This evening I modified the original MJoy circuit to support the potmeters which are in the Suncom (I'm not replacing them... yet). In this picture you can see the wires running off to the throttle (left) and the stick (right) The three buttons are there from an earlier test, they will move to the console later on. I plan to rewire the potmeters tomorrow evening. When that is done, it's time to connect it to the PC, and run the first reallife test with our custom stick (the electronics at least) If all this works, I will have a total of 134 functions, of which 106 are programmable :) I will also have two more analog axes, which will also eventually be connected to the console. Another test I have also planned for this setup is to replace the original pots in the Suncom with Hall sensors. If my guesses are correct, this should be no problem at all, but I'd rather test it now, before we build a Flanker stick with sensors that won't work.

No not really, I'm very busy with my daytime job at the moment, lots of overtime :(

ohh, I would love the F5