Gruss Forum • View topic

by **Jencis** » Sun Apr 17, 2011 3:25 pm

Hi

Can someon tell me what to do in situations like this:

I ticked the stop loss with chase on 25 ticks. No OFFSET...

When i got solid green i pushed "close all positions" ... this acction wasn't accepted because odds started to go down again. So then i waited for stop loss but there wasn't ho more Red button so no stop loss triggered.

Question:

How to make stop loss going when "close all positions" doesn't matches?

Thank you

by **GaryRussell** » Sun Apr 17, 2011 5:56 pm

I'm afraid that's not how it's designed to work. Once you clicked "Close all positions" you cancelled the stop loss. The only option to you then was to cancel the green up bet and click close all positions again and repeat until you had greened up.

by **BERTRAND** » Mon Apr 18, 2011 6:17 am

I have just loaded latest beta version.
I set keep inplay unmatched (default). I then used a custom column to laybet, but the unmatched offset cancelled inplay.
I then again used a custom column, only I ticked IP against the unmatched offset. Unfortunately for me this seemed to have cancelled the stoploss and I lost the whole liability.
I tried one more time with IP ticked and again the stoploss cancelled without me realising in time.
Yesterday using the non beta version the stop loss worked perfectly with the same settings except that i was betting inplay.
So either 1. setting default to "keep unmatched inplay" or
2. Ticking IP against the unmatched offset--before the off
is causing the stoploss to cancel.

by **GaryRussell** » Mon Apr 18, 2011 7:22 am

I have just uploaded version 1.1.0.66x56. It should auto update next time you open the program. Please let me know if you still have the same problem with this version.

by **BERTRAND** » Mon Apr 18, 2011 8:16 am

Thanks Gary,I will let you know.
A couple of points meantime
Yesterday I was using an initial lay (stake=liability) stake of £100, with an actual bank of £200. The offset was 10%(ticks=%) with a stoploss of 30%(ticks=%). Surely there should have been sufficient funds for the offset/stoploss. Would there be any indication of insufficient funds?
Does the "close all positions" "red up" as well as "green up"?
Thanks in advance.

by **GaryRussell** » Mon Apr 18, 2011 8:31 am

What did you see that made you think the problem was funds? If there is a problem with funds when it tries to place a bet you should see evidence of this in the transaction log in the API response column.

Yes close all positions "reds up" as well. It shows you what your position will be before you click and if you see it's red you can still click the button and if it gets matched that is what your position will be.

by **GaryRussell** » Mon Apr 18, 2011 8:35 am

Sorry, I didn't explain. Ticking the IP column definitely did prevent the stop loss from working. This was a bug. The bug only existed in the Beta version. It's only just been discovered because you were the first person to report a problem when ticking the IP column.

by **BERTRAND** » Mon Apr 18, 2011 9:45 am

What did you see that made you think the problem was funds?
I didn't see anything, it's just that I'm new to the software and thought that I was probably doing something wrong!

I am still wondering about the default setting for unmatched bets going inplay. That did not work yesterday. I will leave that unchecked for today.
I guess I don't really need to use a custom column for what i'm doing. In fact I can use the chase unmatched function without the said column.
Many thanks for the incredibly rapid responses.
I hope I'm not going to make a nuisance of myself!
Bert

by **GaryRussell** » Mon Apr 18, 2011 9:53 am

I checked the default in play option and couldn't find anything wrong. I would be grateful if you could try it again with this ticked before you click the custom column and let me know if the bets do not appear in the bets manager with IP already ticked. If they are not ticked when you do this then that is not how it is supposed to work and I will investigate further.

by **BERTRAND** » Mon Apr 18, 2011 2:48 pm

I think I can tell you what you need to know Gary.
If I back to lay (using custom column and default stake unmatched requests inplay) then IP column is ticked and stop loss works.
However if I lay to back with stake=liability stake then IP is not ticked and I can't be sure, but I think stop loss is cancelled also.

by **GaryRussell** » Mon Apr 18, 2011 3:12 pm

Very strange. I just tried the same and the IP column was ticked and the stop loss was still active so I must be missing something. Could you possibly send a screenshot of your custom column settings to admin@gruss-software.co.uk so I can be sure I am testing the same scenario.

by **BERTRAND** » Mon Apr 18, 2011 3:30 pm

Yes I have sent

by **GaryRussell** » Mon Apr 18, 2011 3:32 pm

Just looking through the code again and it makes no logical sense that it should not use the keep in play option when stake=liability. Did you definitely place this bet on a market that goes in play? Which market was it?

by **GaryRussell** » Mon Apr 18, 2011 3:41 pm

Also when IP was not ticked had you definitely placed the bet before the market went in play? When the market is already in play it does not need to have this column ticked.

by **BERTRAND** » Mon Apr 18, 2011 3:44 pm

The market in the screenshot afew minutes ago---I used those settings for that race. Iwill send you a screenshot of BA just before the off. Soon as I can

Problem with Stop Loss!!!

Problem with Stop Loss!!!

Who is online

Sports betting software from Gruss Software