yet another, this time a 109g




http://rapidshare.com/files/66487088/109g.zip.html

no psd with this and no indicators for functions not on a 109(chocks etc). elev trim and flaps are in the dual pressure gauge

enjoy

Frinkin Nice!! Thanks for your wonderfull work. Great addition. Cheers! Bolox00.

cheers ddpairborne59

had the idea in my head for a while now of taking Crash_Moses idea of going to 16 bit a stage further and go to 8 bit. to do this all bmp's were saved in 24 bit and converted using Bright
http://mission4today.com/index.php?name=Downloads&file=details&id=319

seems to run quicker to me- am running at a 50 ms timing for Udpspeed (its set to this in the d/l ) with no noticeable loss in visual quality.
i'd be very interested to hear how this runs on other rigs.

http://rapidshare.com/files/67574709/SP8BIT.zip.html



based on a pru spit- hence the petrol gauge- with a clock added as there is no waypoint indicator ; time to navigate old style
flaps in oil pressure gauge, rudder trim in brake pressure gauge, wep light in supercharger panel and a tail wheel lock beneath u/c indicator are the only 'deviations'

have fun

first off, a p47, which at least one person has been asking for .the background is 8 bit but a few needles are 16 bit after experiencing very thin black lines in some after converting to 8 bit
its quite heavy on dials so doesn't run as quickly as the spit.the dials are also quite small and single pixel 'jumps' of the needles is starting to become apparent.




http://rapidshare.com/files/69248934/p47.zip
an in action shot


its got nearly every indicator possible apart from chocks/dive brake. the dual fuel gauge is 'different'- the lh needle showing~ % and the rh needle fuel quantity from ~15%. there is also a low fuel light.

the next is a repaint of my last 109 fitted into a full cockpit shot. also converted to 8 bit background with some 16 bit needles.



http://rapidshare.com/files/69249578/109full.zip

ive included a readme which is mainly a cut and paste of readme's and some hopefully relevant posts from here on how to make your own, it really isn't rocket science

Where can you download the latest version of UDPSpeed.zip?

The links in the first post are bad.

which link is bad?
all my sets include a copy of udpspeed in them

quote:

Originally posted by bolox00:
which link is bad?
all my sets include a copy of udpspeed in them

All of the links on the first page of this thread don't work, at least for me. I just read the first few posts and didn't want to have to search through all 14 pages.

Since you just posted, I looked at about your last 4-5 posts in this thread and didn't see any links for udpspeed.

Hey, since you guys are into second monitors, have you seen This Post? It uses a Touchscreen, but you can give it a test on a regular monitor. It also runs locally, or networked to save resources.

the original udpspeed links haven't worked for a while and the prog has been updated since to include more functionality. all pits from the last year or so include a copy of the updated udpspeed.
d/l a copy of either of my last two pits and there is a copy of udpspeed included as well as a readme where i've copied stuff from this thread on how to setup udpspeed and some stuff on how to make your own should you so wish (hopefully its a precis of the last 14 pages )

been aware of your wonderful proggy touchbuddy for a while now- really nice
have thought about the possibilities of combining the two in my madder flights of fancy but was under the impression it wasn't possible

Thanks, I'll check that out.

"Combining the two"? What were you wanting to do exactly?

TouchBuddy had a feature that makes a specific tab transparent, so you can see behind it. so, you could have a TB profile with buttons and switches, and have one tab that is transparent so you could see this udpspeed behind it possibility. That is what some users do with this tool for Lockon. It'c called Lockon Virtual Panel (LOVP).

You guys seem to be having so much fun with this.
Is there an instruction manual for dummies anywhere??
It looks so complicated to us hi-tech impaired
dummies.

It was as easy as bolox00 said. Download one of their cockpit profiles, extract it to a folder, and just double click on the udpspeed.exe. If you right-click on the window it displays, you get a menu.

I set the DemoMode value from 0 to 1 to turn it on in the updspeed.ini file. Do, this and you will see the gauges moving around, and all of the right-click menu items.

Right-click to get the menu, then select the About menu item and read it. It explains how to set it up.

That's as far as I got. Have not tried it with IL2 yet. But I can easily see how it works.

from a readme by **** Dastardly....

INTRODUCTION
============
UDPSpeed is a program written by Hruks and Alezz which allows you to display working cockpit gauges on a second screen. For best results, the screen should be that of a second PC networked to the PC you play IL2 on, but it is also possible to run the program on the same PC as the sim (by replacing both the IP addresses in the instructions below with "127.0.0.1"). BTW if you are using a second PC, then it doesn't have to be very powerful - I've run UDPSpeed in the past on an old 460Mhz laptop with 60MB of RAM.

In addition to UDPSpeed itself, this zip also contains a complete 1280x1024 set of my BF-109K instruments, along with a selection of generic warning lights and indicators. N.B. You do not have to be flying a 109 to use the instruments - they'll work with any plane, Allied or Axis. The gauges will also work when you're viewing an NTRK, so you can watch the track from an exterior view on your main screen whilst still keeping an eye on all the instruments on your second screen.

From top left, the set consists of: speedometer, artificial horizon with slip and turn indicators, VSI, tachometer, altimeter, compass with nav beacon indicator, clock, manifold pressure gauge, coolant temperature gauge, oil temperature gauge, landing gear indicator, prop pitch indicator, fuel gauge, war emergency power light, supercharger light, magnetos indicator, aileron and rudder trim indicator, tail wheel lock light, arresting hook light, elevator trim & G-force indicator, flaps position indicator, air brake light, and finally a low fuel warning light.



QUICK START GUIDE
=================
1. Set up a network connecting the PC you play IL2:FB/AEP/PF on (the host) to the PC you want to display the gauges on (the client).

2. Create a folder called UDPSpeed anywhere on your client PC and unzip the files into it. Your UDPSpeed folder should now contain sub folders for each gauge along with the UDPSpeed initialization file and executable.

3. Open the file "UDPSpeed.ini" in your UDPSpeed folder with notepad and check the IP address at the top. It should match that of your host PC. If it doesn't, then amend it. (You can check your IP address by clicking Start, Run, typing "cmd" followed by Enter, then typing "ipconfig" followed by Enter).

3. Open your conf.ini file (in the FB/PF folder on your host PC) and paste the following text at the end of it:

[DeviceLink]
port=21100
host=192.168.0.1

This tells IL2 itself the IP address of the host PC and must therefore match the address you used in the previous step. Obviously if your host PC uses a different address, then amend your conf.ini accordingly.


5. Double click the file "UDPSpeed.exe" in your UDPSpeed folder on your client PC. The gauges should appear.

6. Fire up IL2 on your host PC and load a mission. Once the mission has loaded and you're airborne, the gauges should be active. (If you use the autopilot during take-off, toggle it off and on again once you're off the ground).



LIMITATIONS
===========
1. 1C:Maddox have severely limited the variables which can be exported from a multiplayer game. Most of the main gauges will therefore only work when flying offline. If, like me, you'd like to see this restriction lifted then I suggest you contact 1C:Maddox and ask them to make the necessary changes to the sim (perhaps via a variable which a multiplayer server admin could edit e.g. AllowDevicelink=1).

2. The timing of the lights on the landing gear indicator is slightly wrong. This is because the current version of UDPSpeed doesn't have the ability to round up Devicelink key values.

3. FB/PF doesn't export a value for prop pitch for planes with automatic control (like the BF-109), so you won't see the needle move in this plane. When flying a plane with manual prop pitch control, however, you'll see the larger needle move (down for 100%, up for 0%).

4. FB/PF doesn't export a value for your radiator/cowl flap setting so it's not possible to make a gauge for that.

udpspeed doesn't handle twin engines

that should get you going. the only thing to watch for is the resolution the gauges were made for and your screen resolution.

there should be a full copy of this readme (or similar) in all of the downloads

Thanks for the replys guys.
I'll see what I can do with it.
Cheers.

due to a limitation/unknown syntax in udpspeed regarding multiple engines the #2 engine gauges are only clones of #1 engine but i hope it 'fakes' it reasonably.



http://rapidshare.com/files/77858841/110.zip

starting to get rather gauge heavy with ~40 'dials' so there is a layout jpeg in the zip

Holy wah! Never thought to use 'bright' to clean up the pics. Doh!

Beautiful work gents...now I just need to find a nice clean photo of an SBD-3 cockpit.

S!

continuing the twin engine theme



http://rapidshare.com/files/78858012/b25beta.zip

had to crop the full pit to keep dial size reasonable so have had to take a few liberties with functions- see layout jpeg for details.

i've found some hires pics of us planes recently and in among them was the original hires p47 pic so i redid that



http://rapidshare.com/files/78858121/47d.zip

basically the same layout as before with a few changes to hopefully better represent r/l function.

both are 1024*768 8 bit single background

http://www.nationalmuseum.af.mil/photos/media_search.as...it&btnG.x=0&btnG.y=0
might give some ideas for someone to play with?

Hello and Thank you to everyone who are placing so much labor into this.

This is program is amazing. I was up till 5am this morning playing around with it. Watching tracks with cockpit view on, and just lowering my eyes to watch the panel during combat to see there inputs, also not having to lower my head with Trackir and zoom in/out/away from viewing the target to reading the gauges.

More games should use a secondary screen to offset information from the game window.

If I may pose a few questions ?

1. Can I obtain any of these new or lower resolution samples besides signing up for rapidshare service ?
2. In testing, the elevation/slip gauge in the stock install uses between 15-20% cpu, while the others I have tested only use 0-3% each, This normal ?
3. Playing around with the program I found that I could see my desktop background. So would it be possible to set the background picture as the cockpit and then place the individual gauges correctly over the desktop picture ? or is that what you are doing ?
4. Anyone have any personal performance setting for running this on the machine ? I got it to micro second hickups when all the 1280x1024 gauges are on. Just not perfect yet.
5. Any experience if this program should this be run on the same hard drive as IL-2 or a separate drive ?
I will also do testing if you need someone who is running it on one PC.

glad you are having fun with this stuff.

to answer your questions:
1) you don't need to sign up for rapidshare, just click the free button and wait for d/l ~ 1 min, select server and enter code in box.

2)sounds about right, sliding seems to be more processor heavy than rotation.

3)which set(s) are you using? DD's original sets are 800*600 resolution, his later stuff is 1280 res. CM's and mine are 1024*768 and use a single background for all gauges, moving stuff around isn't possible but the seems to be a major speed increase. there is a further speed increase in these sets by using 8/16 bit images as opposed to 24bit.

4)DD's sets tend to run at a refresh of 1 sec, the later single background sets in 50ms-150ms range and are thus alot smoother. this can be adjusted in the udpspeed ini file, this bit
[Main]
TimerMS=150
playing with this may help, but all my experience is with running on a separate pc via lan. this is how most people are running it i believe. the problem i think you will see is cpu usage as it draws in 2d not 3d and can't 'offload' to gpu. if you have dual core you might try experimenting with assigning udpspeed to a separate core?

5) not sure

looks like you may have just nominated yourself as single pc tester

Thank for the answers Bolox00.
Here is what I found so far.

Test of DD's file name UDPSpeed_BF109K_1280x1024_v1 on a single system comprised of this hardware.
E6300@3.08ghz
Gigabyte 965p-ds3
2gig ram at 4-4-4-12
Raptor 150gig with IL-2, Raptor 36gig with UDPSpeed.
Audigy2 platinum
XFX 8800gt 512mb 640/1650/950
Acer 20inch main, Benq 19inch secondary.


Game runs 1680x1050, 8xAA w/supersampling, 16xAF, vsync, triple buffering, all settings maxed except ground is excellent(perfect causes some weird lag when look at the ground). UDPSpeed monitor runs off the single 8800gt at 1280x1024 as well.

Some settings:
UDPSpeed=0
IL-2=1
IL-2 Priority=high(going above normal helped, did not try realtime)
TrackIR=0
Saitek profiler=0
Everything else was left as is.
UDPSpeed timer at 500ms.

Activation:
Started UDPSpeed, and unchecked all gauges(labeled=Pribor) under additional menu. I then only opened one at a time with the game playing Intro2 track to see how much cpu it took and how it affected my game play and the gauge in real time. Also had to fly certain planes to use some gauges/lite switches.

Results:
Pribor(gauge) number/ cpu use/ game lag/ gauge lag
no gauges just label bar set to vertical= 2-6%, no, no
1= 3-8%, no, no
2= 17-28%, no, yes(slow slip ball, off from ingame sometime)
3= 3-8%, no, no
4= 3-8%, no, no
5= 11-16%, no, no(but if you move it, medium lag)
6= 16-25%, no, same as #5
7= 3-8%, no, no
8= 3-8%, no, no
9= 6-13%, no, no(but if you move it, slight lag)
10= 6-11% no, no(but if you move it, slight lag)
11= 2-6%, no, no
12= 3-6%, no, no
13= 5-7%, no, no
14= 5-7%, no, no
15= 3-6%, no, no
16= 3-6%, no, no
17= 3-6%, no, no
18= 2-6%, no, no
19= 2-6%, no, no
20= 5-11%, no, no
21= 4-10%, no, no
22= 2-6%, no, no
23= 2-6%, no, no
24= 2-6%, no, no
25= 2-6%, no, no

Thoughts:
-With each one running alone you can see how much resource they take.
-You cannot add them up for a total.
-Some like #24 and #25 are boarder items that both use 2-6% with no increase to the base labels, but when both were on together I got low of 5% and a high of 8%, so then #24 and #25 added 0.5% on a low and 1% on the high each.
-Others gauges, maybe because the plane did not have any inputs or small input variables, the gauge did not use any extra cpu power when used with others or the base labels.(mostly the light button type)
-This section will need to be broken down for further testing to see what combinations of well used gauges cost to in terms of performance.

Notes and questions:
-So far I see that the polling is easy for this PC to run. You can display one label or all of them and there is no diference in cpu use.
-Does this mean it is asking for all the info regardless of the label being shown or not?(no gauges)

-The graphic gauge part is going to take some time to sort out. It takes a lot of resources to display these 1280x1024.
-For some reason one gauge over another is taking up more resources.
-Could it be the size and shape of its components? The calculations to do the needles sweep or maybe the redrawning of the needle?
-Seems weird that IL-2 on one core does not even hit 50% use, yet as little as three gauges can use that in 2d. 3ghz single core cannot run this yet some old system can show them all with no lag?

Next test will be setting IL-2 to the affinity=0 and the others to 1 with priority high. So far the numbers are better. I am doing this part to get the program running the best it can under a one set profile then will be able see what can be done to the graphics portion.

Any comments are greatly welcomed.

nice tests you seem to have a good handle on things.

the artificial horizon is i think the biggest resource hog particularly as it slides aswell and is a large image to be drawn each time ~200*200 which is alot of pixels to compute/draw compared with a needle of say 100*10 pixels.

as the slide feature was a late addition to udpspeed i'm guessing that the coding is optimized for rotation and has to do alot more calculating to do a slide movement.
slipball i've always found one of the most awkward to get to work right (also vsi)- at least matching ingame without putting in multiple intermediate positions which takes more calculation and can lead to 'stepping' as it reaches these intermediate values. ingame seems to have a smoothing function applied if not non linear movement aswell. have you delved into playing with the background ini files to modify behaviour yet? might be worth trying to set these to zero? there may be a reduction in cpu useage? i suspect not as i think it still has to calculate zero movement, but maybe worth investigating?
AFAIK udpspeed does read all values called even when not displaying
one thing to rember about udpspeed is that it's free, having been written by Alezz and Hruks , and initially was for use on a separate pc showing maybe 10 gauges in 800*600 with no sliding needles- like il2 itself it is now being pushed to do alot more than it was designed for
i'd also take a look at the single background sets(ok i'm biased here ) , there is a noticeable increase in speed and hence smoothness.
there is also a p51 set a few pages back that uses a completely different way of using devicelink data to draw in 3d, maybe worth a look?

nice rig and overclock btw, tho i'm suprised at you having probs with perfect mode- maybe a new thread with dxdiag and conf.ini settings might get a response from nvidia gurus?