Ragtop

Following the CMSP eagerly if you're happy to release a price. Authentic switches would be of no concern to me. If anything, just some info on the electronics used would be a great help!

Nice to see another Brit! Cool pit, looks very comfortable for long flights!

Great job man! Glad you got it sorted. I think the AHCP is next up for my project, alongside the fuel panel. Money is definitely my issue aswell! Look forward to seeing a video!

Again, my apologies. I feel like I've dragged you through hell and back! It's only when people comment on the progress you've made after seeing it in its early stages that you can really put the work you've done into perspective! I'm actually going down to 1.1.0.9 at the minute, the frame rate hit outweighs the new features and fixes right now! However, the monitor process remains the same so don't let that affect your decision on which build to choose. My pit has taken a rest for this month, unfortunately I needed a new graphics card for BF3, and that cost me a month of cockpit building funds! However it's only a week until payday, and then work will resume, AHCP and Fuel panel are on the cards, so I'll need another Leo Bodnar board! I'll post an update as soon as I get back to work. Looking forward to seeing your photos!

Ah. I had no idea you were on 1.1.0.8. I've never explored this on 1.1.0.8 because I only built my pit after 0.9 Chances are this is why it is not working, because I know there were some changes in the code. If you are using 0.8 then I believe Icemakers Easy Monitor Configurator will be fine, but be aware this will break the 1.1.0.9 install, so you'll have to use the method we've been using in this thread in any builds after 0.8 Can I ask why you've not updated? EDIT: Reading back now you did say earlier, forgive my ignorance. FWIW, I recommend you back up the Init file, and your monitor config, do a total uninstall of 1.1.0.8, a full install of 1.1.1.0 and put the files into place. This was my method and it worked perfectly.

Really odd. Its normal that the in cockpit RWR would stop displaying, this is an FPS saving feature. It can be stopped by changing something to do with the "render purpose" lines in the Init file, but honestly I'm not sure what. But of course thats something to tackle after we get it working! I don't know if this will make it work or not, but I didn't see it in your monitor config file. At the very end, add UIMainView = Viewports.Center

Very silly question, and not to insult your intelligence, but you are turning the RWR on? :P Just incase!

Ok thats great, your monitor layout is exactly the same as mine! SO. Your monitor file is great, but try the position coords of X:900 Y:1180 The file I uploaded, make sure it is in the directory *install*/Scripts/Aircrafts/A-10C/Cockpit/AN ALR69V/Indicator. It should replace the original AN_ALR69V_init.lua file. Once this is done, go to the game and the options page. Set your game resolution to 1920x1980. Let the Aspect complete itself. Make sure fullscreen is turned off! I think I may have forgotten to mention this, if I did, I cannot apologise enough for any undue stress, but it is vital!

Correct me if I am wrong, but from the photo's of your pit, you use two displays, one for your world view, and one in the cockpit which displays the gauges and MFCD's? What is the resolution of the screen you use for world display? (Outside the cockpit) This needs to be taken into account aswell, tell me the resolution and I'll give you some specific numbers to input.

Hmm, your AN ALR file looks a little different to mine! I'll upload mine, let me know if it works! Also your positioning in the monitor config is a little odd, I'd place it at a value which is beyond that of your first display, imagine the values counting X (Right) and Y (Down) from the top left corner of your topmost, and left most monitor. With your resolution of 1920x1080, your position of X 680 and Y 550 would place it on your primary screen. Assuming the screen you want the RWR on is directly below this, try something like X 500 Y 1200. This would place the RWR screen 600px from the top of your lower screen, and 550 from the Left. AN_ALR69V_init.lua

Basically with the release of 1.1.1.0, there is another way of doing the job, however the way I showed you, from 1.1.0.9 will still work. There seems to be no downside to doing it the old way, but someone who understands the coding better than I may chime in!

Ah, very interesting point Airdog, I simply backed up my old files and replaced the new ones, seems to be fine. Whether this could lead to other conflicts I honestly don't know, but my layout is very similar to Pcalverts as you may have seen in my thread, and I've had no problems with the files in their current state. Back up the originals is of course common sense, so if it did go wrong then you can simply go back to the vanilla layout.

You're correct, it's referred to as the AN ALR-69. I'm finally home with some time to spare for a night and for tomorrow! SO. First download the necessary file from the link I put in my earlier post. Replace the file of the same name in the (Install/Scripts/Aircraft/A-10C/AN ALR-69) directory. This enables the indicator to be exported as a viewport. Take note of the name (in caps) at this line of text "vp = env.RWR_SCREEN" This is what your RWR will be referred to when creating your monitor configuration file. Now, go to the (Install/Config/Monitor Setup) directory, and duplicate the default config file. Call it anything you like. Now, open the file and add this RWR_SCREEN = { x = 1000; y = 1245; width = 170; height = 170; } Change the X and Y values to position the RWR, and the width and height to change it's size. Save the file and boot DCS. Finally you need to go to options and change your resolution to the combined size of your screen. Say for instance your top display is 1920x1080, and your bottom screen is 1440x900, then your resolution entered would be 1920x1980. (You do not add the widths because 1920 is your widest screen, you do not need to go past that, only up and down.) The aspect ratio will adjust itself automatically. Finally select the monitor config file you created and named from the drop down box. Hopefully this will get you through it, I found the hardest part was the positioning and sizing of the RWR! Any more questions don't hesitate to ask.

Hey, check back a page, you missed my later post, negates the need to edit, link to file :)

I'd buy another one at the drop of a hat if it was necessary, best HOTAS I've ever used, bar none.

Use the ALR-69 File from here and replace the file in the location I mentioned (Scripts etc etc) Then you need to set up a new Monitor Config file, which is explained very well in the first post of that same thread. Sorry I'm posting from a work computer and there's customers everywhere so I'm rushing :P I'll go into more detail if you're still stuck later and none else has helped!

You need to modify the Indicator.init lua file in the (install location)/scripts/aircraft/A-10C/ALR169 folder. You will also need to modify the Monitor Setup file in the config folder. There is a thread regarding this in the tech support forum here. Sorry if this is little info, I'm in bed right now, about to get ready for work. If you still have trouble I'll help you out tonight when I'm home.

Firstly I'd like to say a huge well done to ED for giving such an awesome outline on what they hope to achieve with their future projects, it's awesome that a developer can provide such a great sense of community, and be so active within it. Secondly, some of the people here need to chill! If ED have decided to take on two aircraft projects, then it's because they are confident that they can deliver two aircraft projects. Who are you to tell them how to run their business? Yes we are the end user and the paying customer, and ED are fantastic community hosts being that they openly ask for feedback and criticism, but its a shame to see that some of the guys here will still spit their dummies out and throw a tantrum because ED aren't working exclusively on what they want! Step back and look, there are more customers out there than you, who are also willing to pay for what will be an undoubtedly amazing product. I for one am ecstatic to see that there are plans for more than one project to be under simultaneous development. To me this means that we will likely see better integration from the get go, more for us to read while we wait, and less time between releases! If they worked exclusively on DCS:Next Jet, then you'd likely be the same kids whinging that it was going to be another half a year/however long until DCS:Flying Legend, because they hadn't gotten anything done on it. You don't know what ED are capable of, so I think it's common courtesy to give them some space to breathe without having to get your blessing! Look at BS2. If you knew they were developing that then you'd have been complaining that they weren't working on 1.1.1.0, but you didn't know, and hey! We got TWO great products. Keep it up ED, you're doing incredible work, and I think it's safe to say you have positive support from 95% of the community here. Don't let the complaining 5% change your game plans, because you've got it pinned so far.

Does it come with the Mavs, Sidewinders and jammer? :P

A bit of wood for a shell and Helios for the rest of that empty looking screen, and you're onto a winner!

My modded viewport files (Scripts/Aircraft/A-10C/***/***.init) LUA files are all working great, except the digital clock. It is very large and totally off of where it should be, any ideas what may be causing this? I can post the lua file tomorrow but if anyone has figured this one already then speak up! :) Smoother FPS on the ground for me on an unrelated note!

I'm a little late, but technically it's still nighttime here in the UK :P Happy Birthday Matt, you deserve one after the incredible work you and your team have done. Looking forward to the next week, "busy" has historically resulted in treats for us, so I wish you a successful and "busy" year! :P

Great job, you and Speed. Still haven't gotten round to installing yet, making sure all my display outputs will work ok with MFD's, RWR etc, but it all looks like it's going to be OK, I'll report back when it's all done :)

Sweet! I'll install tomorrow morning! Very pleased, great job ED.

Have any Helios/Multi monitor users installed yet? A) Will Helios still patch and work correctly B) My custom LUA files in the monitor setup folder, with modified display ports; will they still work if I back up and replace the files in the new install? Any word on this would be appreciated!