Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
faq [2019/04/05 16:06]
profitview
faq [2021/11/30 11:50] (current)
profitview
Line 1: Line 1:
-<​page-header>​ 
 ==== Frequently Asked Questions ==== ==== Frequently Asked Questions ====
-</​page-header>​ 
  
 <​accordion>​ <​accordion>​
  
-<panel title="​1) - Once I have paid for PV, when do I receive ​my registration code?">​ +<panel title="​1) - Once I have paid for PV, when does my account get activated?">​ 
-Once you have received at least two confirmations on the blockchain, you will receive an email containing your registration ​code. (Please let us know if you haven'​t received a registration ​code within 24hr)+Once you have received at least two confirmations on the blockchain, you will receive an email containing your personal account ​code. (Please let us know if you haven'​t received a code within 24hr) 
 + 
 +From that time on your account status in the app itself will change and you are good to go!
 </​panel>​ </​panel>​
  
 <panel title="​2) - How do I request a trial for your indicators?">​ <panel title="​2) - How do I request a trial for your indicators?">​
-Trials were being abused and are thus no longer offered for indicators.+For a few days of trial access send us a [[https://​occ.profitview.app|message on TV]] or email to <​support@profitview.app>​!
  
 Please join our [[https://​discord.profitview.app/​|Discord]] Server and see the ''#​results-only''​ channel where you'll find numerous examples showing their effectiveness. Please join our [[https://​discord.profitview.app/​|Discord]] Server and see the ''#​results-only''​ channel where you'll find numerous examples showing their effectiveness.
Line 16: Line 16:
  
 <panel title="​3) - How do I request a trial for ProfitView?">​ <panel title="​3) - How do I request a trial for ProfitView?">​
-We don't offer a ProfitView trial however ​it's free to try out ''​BitMEX Testnet'',​ ''​Coinbase Pro Sandbox'',​ ''​Deribit Testnet'' ​and ''​Gemini Sandbox''​!+We don't offer a dedicated ​ProfitView trial – however ​**all testnets** can be used **without** a license or subscription on the regular version: ​''​Binance Futures Testnet'', ​''​BitMEX ​Testnet'',​ ''​Bybit ​Testnet'',​ ''​Coinbase Pro Sandbox'',​ ''​Deribit Testnet''​''​Gemini Sandbox'',​ ''​Kraken Futures Demo'',​ ''​KuCoin Sandbox'',​ ''​KuCoin Futures Sandbox'',​ ''​OANDA Sandbox'',​ ''​OKEX Demo'',​ ''​Phemex Testnet''​ and ''​SimpleFX Demo''​!
 </​panel>​ </​panel>​
  
-<panel title="​4) - How much do the OCC &amp; Multipass Indicators ​cost?">​ +<panel title="​4) - How much does the OCC Indicator ​cost?">​ 
-OCC & Multipass are each offered at an annual ​cost of 0.1 BTC per year.+OCC is offered at a subscription ​cost of ''​$499.99''​ for **[[https://​profitview.app/​buy/​occ/​|12 months]]** – or ''​$274.99''​ for **[[https://​profitview.app/​buy/​occ/​6m/​|6 months]]**. 
 + 
 +[[https://​shop.profitview.app/​|Visit our shop here!]]
 </​panel>​ </​panel>​
  
 <panel title="​5) - How much does ProfitView cost?">​ <panel title="​5) - How much does ProfitView cost?">​
-ProfitView 1.is offered as a lifetime subscription at a cost of 0.08 BTC.+ProfitView 1.is offered as a **[[https://​buy.profitview.app/​|lifetime ​license]]** at a cost of ''​$399.99''​ or a **[[https://​profitview.app/​buy/​monthly|monthly ​subscription]]** at a cost of ''​$36.99''​. 
 + 
 +[[https://​shop.profitview.app/|Visit our shop here!]]
 </​panel>​ </​panel>​
  
Line 35: Line 39:
 </​panel>​ </​panel>​
  
-<panel title="​7) - Does ProfitView only support OCC/MP or do OCC/MP only work with ProfitView?">​+<panel title="​7) - Does ProfitView only support OCC or does OCC only work with ProfitView?">​
 Short answer: **No!** Short answer: **No!**
 \\ \\
Line 43: Line 47:
 </​panel>​ </​panel>​
  
-<panel title="​8) - How can I backtest the OCC or MP Indicator?">​ +<panel title="​8) - How can I backtest the OCC Indicator?">​ 
-While TradingView backtesting is quite limited and not really useful for crypto trading, ​backtester ​versions of OCC and MP are still in the works.+While TradingView backtesting is quite limited and not really useful for crypto trading, ​newer versions of OCC have a complete **paper trading simulation** ​and **backtesting built in**!
 \\ \\
-Until then you have to manually backtest (count the signals) on the chart and use our Google Sheet to compare the profatibility of different setups: https://​profitview.app/​strateval 
 \\ \\
-(we are also working on a TradingView addon to quickly export/​save ​the signals from the active chart to make this much easier)+Additionally you can use our Google Sheet to compare ​the profitability of different standard settings: https://​profitview.app/​strateval
 </​panel>​ </​panel>​
  
Line 56: Line 59:
  
 <panel title="​10) - In TradingView alerts, what do I have to select?">​ <panel title="​10) - In TradingView alerts, what do I have to select?">​
-Under ''​Condition''​ you have to select your indicator with the settings that you are using on your chart or that you want to run, then in the **wide** dropdown **below** it you select the alert condition (Long/Short etc.).+Under ''​Condition''​ you have to select your indicator with the settings that you are using on your chart or that you want to run, then in the **wide** dropdown **below** it you select the alert condition (eg"​Entry"​).
 \\ \\
 The narrow dropdown right next to the indicator selection only contains the graphs of the indicator which don't influence the main trigger condition and can usually be ignored! The narrow dropdown right next to the indicator selection only contains the graphs of the indicator which don't influence the main trigger condition and can usually be ignored!
Line 129: Line 132:
 </​panel>​ </​panel>​
  
-<panel title="​15) - Sometimes I get error messages saying &​quot;​expires is in the past&​quot;​ or &quot;Your computer'​s ​clock is too far into the future&quot; etc., what can I do?">​ +<panel title="​15) - Sometimes I get error messages saying &​quot;​expires is in the past&​quot;​ or &quot;Timestamp for this request was ahead of the server'​s ​time&quot; etc., what can I do?">​ 
-Please make sure that your computers clock is synced and has the exact current ​time. You can check this by visiting ​the following site: https://time.is/+Since ProfitView 1.3 an internal exchange ​time sync was added and is regularly runHowever sometimes your OS time sync can interfere with this process. 
 +\\ 
 +Since ProfitView 1.3.3 the internal ​time sync is also triggered whenever this error is encountered from an exchange API.
  
-It is also highly recommended that you enable auto clock syncing ​by installing NetTime ​(http://​www.timesynctool.com/​for Windows.+The **two alternative solutions** to this problem are: 
 + 
 +**a)** Either lower the PV time sync interval ​by lowering the value of "​Exchange Time Sync Interval"​ under "​General Options" ​(then PV will run the time sync more often) 
 + 
 +**b)** Disable PVs internal time sync completely by setting "​Exchange Time Sync Interval"​ under "​General Options"​ to "​0"​ and then using an external time sync tool:
 \\ \\
-For OS-X follow the instructions under http://​www.macinstruct.com/​node/​92 to set up time syncing!+We recommend installing NetTime (http://​www.timesynctool.com/​) for Windows – for OS-X follow the instructions under http://​www.macinstruct.com/​node/​92 to set up time syncing! 
 + 
 +Please make sure that your computers clock is synced and has the exact current time. You can check this by visiting the following site: https://​time.is/​ 
 </​panel>​ </​panel>​
  
Line 144: Line 156:
 At the same time you should then specify LESS number or retries (3-4) for your main position order by adding ''​retries=<​number>''​ only to that line of your syntax. At the same time you should then specify LESS number or retries (3-4) for your main position order by adding ''​retries=<​number>''​ only to that line of your syntax.
  
-**Note:** According to the [[https://​www.bitmex.com/​api/​explorer/#​!/​Order/​Order_new|BitMEX API documentation]] position closing orders are considered "​reduce only" by default, so for ''​c=position''​ commands there is **no need** to specify ''​r=1''​ – with the added benefit of normal ​closing orders being exempt from load shedding while "​reduce only" orders can fail!+**Note:** According to the [[https://​www.bitmex.com/​api/​explorer/#​!/​Order/​Order_new|BitMEX API documentation]] and the [[https://​blog.bitmex.com/​api_announcement/​load-shedding-and-close-execinst/​|BitMEX Blog]] position closing orders are considered "​reduce only" by default, so for ''​c=position''​ commands there is **no need** to specify ''​r=1''​ – with the added benefit of closing orders ​without a quantity (PV will omit this automatically for q >= 100%) being completely ​exempt from load shedding while "​reduce only" orders can fail!
 </​panel>​ </​panel>​