You can always use the Build menu to build the solution, does it work then? If not, do you get any error messages?
V-Sync has no effect on image quality. Its only purpose is to make sure that your graphics card sends a new image to your screen exactly at the time when your screen is about to refresh. Without V-Sync you can get image tearing because the graphics card may send a new image to your screen before the screen is done drawing the previous image.
Refresh rate of DK2 is 75 Hz so you're not getting more than 75 FPS anyway no matter how fast the game may really run on your computer.
Refresh rate of DK2 is 75 Hz so you're not getting more than 75 FPS anyway no matter how fast the game may really run on your computer.
Not to mention that Fernando would probably hate to second to Lewis again. RB already has a duo of drivers with great potential. McLaren really remains the only reasonable option...
Display it in a button. If you set appropriate "Style" flag for the button it should look like a text.
Again, read the InSim.txt file in LFS/docs
You cannot create IS_NCN packet because it is an "Info" packet. LFS will send you IS_NCN when a new player connects to your server. You cannot send IS_NCN to LFS - there's no reason why you would want to do it anyway.When you receive IS_NCN, you can send IS_MTC to display the welcome message.
...
inSim.Bind<IS_NCN>(on_IS_NCN);
...
void on_IS_NCN(InSim inSim, IS_NCN ncn) {
IS_MTC message = new IS_MTC();
message.UCID = ncn.UCID;
message.PLID = 0;
message.Msg = "Hello " + ncn.PName;
inSim.Send(message);
}
I think both the track and the tyres contributed to a quite boring afternoon. If it wasn't for Nico once again proving how much of a douche he is, the race would've been entirely uneventful. The lack of tyre strategy was certainly a letdown but that wasn't the only problem. Except for Nico passing cars 2 secs slower than him and Magnussen X Verne fight at the beginning, what else has happened? IMHO not much...
What exactly about it you don't understand? You can send packets to LFS to make it do stuff (restart race, reorder grid, display buttons, ...) and LFS can send packets to you to tell you what's going on in the game (player pitted, race was restarted, ...).
All you need to know is the kinds of packets InSim uses and what they are for. This is all described perfectly in InSim.txt. It doesn't matter if you use InSim.NET, CInSim, LFS_External or your own tools to talk to LFS through InSim. You always have to know what packets to send or get and how to read the data in them. InSim.NET makes this extremely easy because it turns raw InSim packets into C# objects that you can use naturally from your program.
FWIW, here's how you can display buttons with InSim.NET
using System;
using InSimDotNet;
using InSimDotNet.Packets;
namespace ISN_Example
{
class MainClass
{
public static void Main (string[] args)
{
InSimSettings settings = new InSimSettings();
InSim inSim = new InSim();
/* Tell InSim.NET that we are interested in incoming IS_BTC packets */
inSim.Bind<IS_BTC>(ISButtonClicked);
/* Set up connection parameters */
settings.Host = "127.0.0.1";
settings.Port = 29999;
settings.Admin = String.Empty;
/* Try to connect */
try {
inSim.Initialize(settings);
} catch (InSimException e) {
Console.WriteLine("There was a problem when trying to connect to InSim:");
Console.WriteLine(e.Message);
return;
}
/* Create an object that resembles IS_BTN InSim packet */
IS_BTN button = new IS_BTN();
/* Set up first button */
button.ClickID = 1;
button.ReqI = 1;
button.T = 5;
button.L = 5;
button.W = 50;
button.H = 15;
button.BStyle = ButtonStyles.ISB_CLICK | ButtonStyles.ISB_C1;
button.Text = "Click Me";
/* Hand it over to InSim.NET and let it do the magic */
inSim.Send(button);
/* Adjust some values to create another button */
button.Text = "Another click me";
button.T = 25;
button.ClickID = 2;
inSim.Send(button);
/* Notice that I do not have to create two objects ("button1" and "button2") to display
* two buttons. I can just change some values in "button" and send it again. */
/* Wait for any key */
Console.ReadKey();
/* Hang up and exit */
inSim.Disconnect();
Console.WriteLine("Connection to InSim closed...");
}
/* InSim.NET will call this method when it gets IS_BTC packet from LFS */
public static void ISButtonClicked(InSim inSim, IS_BTC clicked)
{
Console.WriteLine("Button ID: " + clicked.ClickID + " clicked");
}
}
}
@DarkTimes:
It's pretty cool that InSim.NET builds and runs on Linux. At least the example above works flawlessly on my Fedora 20 box with Mono 3.10.
Maybe you should read the documentation for InSim itself then? It describes in detail the meaning of each packet. Creating or reading them with InSim.NET should be easy.
InSim.NET provides a few simple examples how to use it on its CodePlex homepage in "Documentation" section.
It's not about that. But we absolutely should not form any conclusions based on information of various quality we find somewhere on the Internet. There is a reason why it takes several years of professional training to become a doctor.
Note that the quoted text mentions only "severe" DAI but we have no idea what exactly does "severe" mean - at least I certainly don't. I'd imagine that the prognosis depends on lots of factors that cannot be explained to a layman in one web article.
Gary Hartstein about Diffuse Axonal Injury: http://formerf1doc.wordpress.com/2014/10/07/diffuse-axonal-injury/
From what I've gathered the prognosis depends a lot on how severe the damage is and nobody knows that well enough at this point. Let's hope for the best. Forza Jules!
From what I've gathered the prognosis depends a lot on how severe the damage is and nobody knows that well enough at this point. Let's hope for the best. Forza Jules!
I don't think that 11 years old technology qualifies as "the newest latest shit". There will be a new incompatible patch coming out soon anyway so a downgrade to 0.6F is only a temporary solution.
You can download the 0.6F installer from here for now: http://devoid-pointer.net/download_lfs06f.php
Don't use LFS_External. It's outdated and broken library. Use InSim.NET instead.
Front tyres can transfer only so much force on the road so as a general rule the more you brake the less you can turn. You might find braking to be much more challenging in LFS because the physics is not dumbed down in any way and there are very few driving aids. You might want to download a few hotlap replays from LFSWorld and compare them to your laps...
This sounds like something I could've figured out had I bothered to break out Firebug. It works at least in FF32.The old forum didn't have a special mobile style and as far as I was ever concerned it displayed quite well on all my mobile gadgets. The only rather annoying problem right now is the portion of the site being cut off in Gecko-based browsers, mobile or not if the display size is not wide enough for the content to fit in. You can see the left/right scrollbar missing on the attached screenshot.
I'm sorry to report that the update doesn't seem to fix the problem. The upper bar seems to behave a bit better when I zoom in but there is still no left/right scrollbar when the content doesn't fit into the window. Easiest way to reproduce this is to just zoom in - it breaks even in desktop Firefox.
The problem with the right part of the site running out of the browser is apparently not isolated to mobile browsers. I can get the same behavior in desktop Firefox 32 if the display resolution is low enough.
Misrendered 3D cars
Is anybody else experiencing this? The black region moves about as I rotate the car. It might just as easily be a drivers issue as I've only seen it with AMD FOSS Linux drivers so far...
Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde LE [Radeon HD 7730/8730]
OpenGL renderer string: Gallium 0.4 on AMD CAPE VERDE
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.1.5 (git-45bf29b)
OpenGL core profile shading language version string: 3.30
New site not displayed correctly in various mobile browsers
The new site doesn't display correctly for me in any of the mobile browsers I use.
Default Sailfish browser (based on Gecko/FF 26) won't display the rightmost part of the page.
Another problem is with Opera Mini (Android ver. 22) where the car change animation makes the right border jump around. When the animation stops, th border returns to its intended position.
The upper bar with links and login button doesn't move sideways with the rest of the site. If I zoom in, I cannot see the right side of the bar. I always have to zoom far out to see the login button. This is a problem common to all browsers I tried. (Sailfish default, Android Opera Mini, WebCat)
Default Sailfish browser (based on Gecko/FF 26) won't display the rightmost part of the page.
Another problem is with Opera Mini (Android ver. 22) where the car change animation makes the right border jump around. When the animation stops, th border returns to its intended position.
The upper bar with links and login button doesn't move sideways with the rest of the site. If I zoom in, I cannot see the right side of the bar. I always have to zoom far out to see the login button. This is a problem common to all browsers I tried. (Sailfish default, Android Opera Mini, WebCat)
Generic gamepads can still use DirectInput like they do now...
XInput is quite simple interface designed for XBox 360 gamepads only. Wheels and joysticks still need DirectInput to support force feedback, shifters, analog pedals etc...
It'll run just as well as it does on Windows when bootcamped, WINE's performance will be considerably worse.
You seem to have it pretty misconfigured. Make sure you're using the latest drivers; it might not help but it certainly won't hurt. I believe that you should set the "Wheel turn compensation" to zero if you want LFS to not mess with the input. Once you do that, uncheck the "Combined pedals" and assign correct axes for throttle, brake and clutch pedals in LFS. As a last thing turn off the "Calibration lock", click "Recalibrate axes" and turn your wheel all the way from lock to lock and depress all pedals. LFS will adjust the input for the reported axes ranges and your wheel should work correctly...
This is most likely related to the DX9 switch. Some native DX9 DLLs are needed to get the textures to load properly.
FGED GREDG RDFGDR GSFDG